Segmenter

Yes. One API key is valid for all Jina AI search foundation products, including the Reader, Embeddings, Reranker, Classifier, and Segmenter APIs, with tokens shared across all of them.

Yes, token usage can be monitored in the 'API Key & Billing' tab by entering your API key, allowing you to view the recent usage history and remaining tokens. If you have logged in to the API dashboard, these details can also be viewed in the 'Manage API Key' tab.

If you have misplaced a topped-up key and wish to retrieve it, please contact support AT jina.ai with your registered email for assistance. It's recommended to log in to keep your API key securely stored and easily accessible.

No, our API keys do not have an expiration date. If a key is compromised, revoke it yourself in the API Key Management dashboard, which takes effect immediately; issue a replacement key first if you want to avoid downtime. Any remaining token balance stays on your account rather than on the revoked key. If you cannot access the dashboard, or believe the account itself is compromised, raise it with Elastic Support.

Yes, you can transfer tokens from a premium key to another. After logging into your account on the API Key Management dashboard, use the settings of the key you want to transfer out to move all remaining paid tokens.

Yes, you can revoke your API key if you believe it has been compromised. Revoking a key will immediately disable it for all users who have stored it, and all remaining balance and associated properties will be permanently unusable. If the key is a premium key, you have the option to transfer the remaining paid balance to another key before revocation. Notice that this action cannot be undone. To revoke a key, go to the key settings in the API Key Management dashboard.

This is because our serverless architecture offloads certain models during periods of low usage. The initial request activates or 'warms up' the model, which may take a few seconds. After this initial activation, subsequent requests process much more quickly.

No. We never use your API requests, inputs, or outputs to train our embedding, reranker, or any other models. Your data remains yours.

Rate limits apply per API key:

Free: 100 RPM, 100K TPM
Paid: 500 RPM, 2M TPM
Premium: 5,000 RPM, 50M TPM

There is also an IP-based limit of 10,000 requests per 60 seconds. Limits vary by endpoint; see the rate limit table above for per-endpoint figures.

There is no batch size limit for either the Embeddings or Reranker APIs. You can send as many items or documents as needed per request. Both APIs batch inputs internally by token count for optimal GPU utilization.

No, they are three separate paths. The Jina APIs on this site are self-serve and pay-as-you-go with a Jina API key. The Elastic Inference Service (EIS) runs Jina models inside Elastic Cloud, billed through your Elastic subscription, with no infrastructure for you to manage. Jina On-Prem is a commercial license, sold by Elastic as its own SKU since August 10, 2026, for running the models in your own self-managed, on-premises, or air-gapped infrastructure. For the EIS and On-Prem paths, contact Elastic Sales.

Our pricing model is based on the total number of tokens processed, allowing users the flexibility to allocate these tokens across any number of sentences, offering a cost-effective solution for diverse text analysis requirements.

Yes. New users get an auto-generated API key with free tokens usable across any of our models. Once the free tokens are consumed, you can purchase additional tokens for the key in the 'Buy tokens' tab.

No, tokens are not deducted for failed requests.

Payments are processed through Stripe, supporting a variety of payment methods including credit cards, Google Pay, and PayPal for your convenience.

For self-serve token purchases, Stripe issues an invoice to the email address associated with your Stripe account at the time of purchase. If you need a formal purchase order, a negotiated contract, procurement paperwork, or consolidated billing, that runs through Elastic rather than Stripe: contact Elastic Sales.

Token purchases on this site cover use of the hosted Jina APIs. They do not license you to run the model weights in your own infrastructure. For that, Elastic has sold a commercial license as its own SKU since August 10, 2026, priced annually rather than per token. Contact Elastic Sales for a quote.

Self-serve token purchases are processed through Stripe and invoiced automatically to your Stripe account email. For purchase orders, procurement processes, or volumes above what self-serve top-up supports, contact Elastic Sales.

Balance and rate limits belong to an API key, not to the account, so the first thing to check is the key itself rather than the account page: enter it in the API Key & Billing tab and confirm the balance and tier there. If the account holds more than one key, the tokens are on the key that was topped up, which may not be the key your application is sending. A new tier can also take a short time to propagate after payment. If the key shows the balance but is still limited at the previous tier after that, contact support.

Self-serve billing is managed from the customer portal reachable via the API Key & Billing tab, where auto top-up can be switched off and saved payment methods removed. Turning off auto top-up stops future charges but leaves any balance already purchased usable. If you also want the account and its data removed, or a refund considered, send that request to support; account deletion is handled manually and takes a few business days, and you will get written confirmation once it is done.