Reranker

Usage depends on the selected model and the query–document inputs. Review the response usage and current pricing before estimating a large workload.

v3.5 and v3 compare documents listwise; m0 supports visual candidates; v2 and earlier models offer other size, language, and architecture trade-offs.

Open the model card for its published license. API access and permission to run downloaded weights commercially are separate arrangements.

Multilingual rerankers support cross-language relevance matching. Test the language pairs and document styles important to your application.

Limits vary by model. The v3 family also exposes a document-length setting; reduce long candidates or segment them before reranking.

Use the published API limits and account for the total context of a listwise request. Reducing the candidate set also helps latency.

Measure representative queries with the model, candidate count, and document lengths used in production. A fixed document count alone is not enough.

Available weights and cloud marketplace listings provide deployment paths. Review the model license and the environment’s memory and runtime requirements.

This playground runs published rerankers. Training or adapting the underlying reranker requires a separate training workflow and licensed model assets.

Choose m0 for image candidates and provide readable source images. Very small text or heavily compressed pages can lose information before ranking.

A listwise model sees the query and candidate documents together, allowing the score to reflect relationships among the candidates.

The serving system balances total request size, throughput, and latency. Follow the API schema rather than assuming the model’s theoretical maximum.

Both request frequency and input volume can matter. Queue bursts, limit concurrency, and retry transient rate errors with backoff.

For text, evaluate v3.5 first. For visual documents, evaluate m0. Use a smaller or older model when its license, runtime, or latency better fits the task.

Some hosted models may need to load or initialize before serving a request. Latency also depends on the input size and current service load. Keep a timeout suited to the workload and inspect errors before retrying.

A key can access the services assigned to its scopes. Review the key in the dashboard before sharing it with an application.

Open the key manager to inspect recorded requests, status, latency, and available usage data for the selected key.

Sign in to manage your keys. If a key may be exposed, revoke it and update the applications that use it.

Access follows the expiry and status configured for the key. A key that is revoked or expired cannot be used for new requests.

Use only the transfer options available in your account. Do not assume that provider balances and Chatsax balances are interchangeable.

Use the key manager. Revocation stops future access, so update any dependent applications before retiring a key.

Check the platform privacy terms and the selected provider’s policy. Avoid sending material your organization has not approved for that service.

Use the status and retry information returned by the API. Add backoff and control concurrency instead of continuously retrying the same request.

The batch workflow supports submitting a job, checking its status, and downloading its output when the selected provider completes it.

Chatsax is independently operated. The current model APIs are provided by Jina, whose papers and model cards are linked for reference.

Each service has its own metering rules. Reading, search, embedding, and generation can count different units; review the active pricing before use.

Open the dashboard to receive a visitor key automatically. Sign in when you need account management or token purchases. The account screen shows your available balance and access.

The provider may have processed work before the connection ended. Review the recorded usage and billing status rather than inferring them from a closed browser tab.

The checkout screen displays payment methods available for your region, currency, and account.

Use the billing portal linked from your account, and retain the payment confirmation associated with the purchase.

No. API credit pays for hosted usage. Downloading and commercially running model weights follows the model’s separate license.

Use the contact page to describe the services, traffic, latency, and deployment requirements you need.

Check the selected account and key, the payment status, and the latest usage records. Keep the payment reference when contacting support.

Use the billing controls provided in the account or payment portal. Check the confirmation after changing an automatic payment setting.