Jina Reader and anonymous utility APIs
A recurring no-cost API allowance covering 2 cataloged models.
https://r.jina.aiModels mentioned
ReaderLM-v2jina-vlmEquivalent paid value
How this was valued: Modeled request envelope for the anonymous Reader tier: the documented keyless limit of 20 requests/minute per IP (28,800/day) is multiplied by a modeled 10,000 tokens per request and priced at Jina's current $0.05 per 1M token API rate, the rate the live first-party catalog lists for ReaderLM-v2 and all standard models and the rate keyed Reader calls pay when Jina counts the tokens of the output response. The per-request size is modeled, not documented: r.jina.ai publishes no per-request or per-minute token cap at any tier, so the assumption borrows Jina's only published per-request token quantity for web-content retrieval, the adjacent s.jina.ai charge of "a fixed number of tokens, starting from 10000 tokens" per request; individual Reader responses can be larger or smaller. Assumes uninterrupted single-IP saturation with no latency or availability loss. The anonymous Segmenter charges zero tokens even when keyed, so it adds no paid-equivalent value at Jina's own rates, and s.jina.ai is blocked without a key; the separate 10M-token keyed signup balance is valued in the jina_ai_search_foundation record and is not double counted here.
Limits and terms
- Reader Anonymous Requests Per Minute Per Ip
- 20
- Segmenter Anonymous Requests Per Minute Per Ip
- 20
- Segmenter Tokens Charged
- 0
- Reader With Free Key Requests Per Minute
- 500
- Caveat
- Supplying a key to Reader charges its token balance; anonymous basic Reader calls remain free.
What happens to your prompts?
Jina excludes model training, but anonymous Reader retention and non-training content handling remain unclear.
- Plan Scope
- Jina Reader and anonymous utility endpoints after Elastic's October 2025 acquisition; legacy Jina statements and current Elastic processing terms both matter.
- Prompt Retention
- URLs, fetched pages, prompts, and transformed content are request data; the public legal documents do not state a Reader-specific retention period or whether anonymous requests receive different storage.
- Response Retention
- not documented
- Ordinary Logging
- Operational, diagnostic, usage, IP, and security metadata may be retained and used in aggregated and anonymized form.
- Model Training
- Jina's terms say customer request data, inputs, prompts, and uploaded content are not used to train its models.
- Product Improvement
- Aggregated anonymized metadata can improve services; request-content use outside model training is not described with Reader-specific precision.
- Human Or Operator Access
- Content can be accessed as necessary for service delivery, security, support, and legal compliance under Elastic/Jina controls; no operator-blind promise is published.
- Subprocessors And Routing
- Reader fetches third-party URLs and operates under Elastic's current DPA and subprocessor framework, creating both destination-site and service-side data flows.
- Deletion Controls
- No anonymous per-request deletion mechanism or content TTL was found; contractual deletion at termination does not directly help anonymous users.
- Caveat
- Anonymous access should not be mistaken for anonymous processing. IP and usage logs plus an undocumented content TTL make Reader unsuitable for confidential URLs or query material.
Governing documents
- Terms And Conditions
- https://jina.ai/legal/
- Privacy Policy
- https://www.elastic.co/legal/privacy-statement
- Data Processing Agreement
- https://www.elastic.co/legal/customer-dpa
Eligibility
- Account Required
- No
- Payment Method Required
- No