Reader

The active request limit depends on your key and the upstream service. Check the rate-limit page for the limit assigned to your key, and use the retry information returned by a rate-limited response.

Reader normally counts tokens in the returned content. Options such as ReaderLM or web search can use a different rate; review the active pricing and recorded usage.

The service loads the supplied URL, extracts the relevant page content, and returns Markdown, text, HTML, or a screenshot according to your request.

Jina publishes its Reader implementation. The source link explains the extraction pipeline; Chatsax adds its own access and gateway layer.

Latency depends on the target site, cache state, browser engine, and readiness settings. A simple cached page and an interactive application have very different loading costs.

Clean document text reduces navigation, scripts, and markup in the context you send to a model. Raw HTML remains available when structure is useful.

Reader preserves the language of the source. Browser locale controls can help request the localized version a website serves.

A URL does not grant access to restricted content. Use authorized access, and supply supported cookies or proxy settings only when you have permission.

Use a public PDF URL or upload a local PDF in the playground. Scanned and image-heavy pages may need visual extraction; inspect the response before indexing it.

Images can remain as Markdown references, be removed, or receive generated captions. Choose the output that suits the model consuming the document.

Upload the file and provide a reference URL so that relative resources and links have a meaningful base.

Set cache tolerance to accept recent content, or bypass the cache when freshness matters. Requests with custom authentication may not be cacheable.

Reader supports forwarding cookies for authorized sessions. Some applications still require interactions that a single extraction request cannot reproduce.

Yes. Supply the PDF URL rather than an abstract page when you need the paper itself. Rate limits on the source website can still affect access.

Enable generated alt text to add a visual description to image references. Captions are model output and should be checked for important details.

Use a managed key, inspect errors and latency, control concurrency, and choose cache settings according to how quickly your sources change.

It is useful when document structure makes rule-based HTML conversion difficult. Enable ReaderLM in the playground and compare the resulting content and usage.

Use ReaderLM with an extraction instruction and JSON schema, then validate the returned fields in your application.

No access result is guaranteed. Target websites may reject automated traffic regardless of the available browser settings or account tier.

A higher service tier changes service limits; it does not confer authorization on third-party websites.

The public Reader repository is a useful starting point. Review its license, dependencies, browser requirements, and the parts you need to operate yourself.

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.