--- title: "Jina Reader and anonymous utility APIs free inference" description: "A recurring no-cost API allowance covering 2 cataloged models." canonical_url: "https://freeinferencing.com/provider/jina_ai_reader/" md_url: "https://freeinferencing.com/provider/jina_ai_reader.md" last_updated: "2026-09-19" --- # Jina Reader and anonymous utility APIs > A recurring no-cost API allowance covering 2 cataloged models. ## Classification - **Directory:** Current - **Free access:** Always-free quota - **Status:** Available now - **Confidence:** High - **Payment card:** No - **Account:** Not required - **Equivalent paid value:** Up to $438.30/mo - **API endpoint:** `https://r.jina.ai` ## Models mentioned - `ReaderLM-v2` - `jina-vlm` ## Limits and terms ```yaml 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? **Partially private.** Jina excludes model training, but anonymous Reader retention and non-training content handling remain unclear. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: partial 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. agreements: 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 ```yaml account_required: false payment_method_required: false ``` ## API compatibility and modalities - **Compatibility:** Jina Rest - **Modalities:** Webpage To Markdown, Pdf Extraction, Image Captioning, Tokenization, Segmentation, Image / vision ## Before you build with Jina Reader and anonymous utility APIs ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “Always-free quota” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 2 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is No, and account access is not required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Partially private** because Jina excludes model training, but anonymous Reader retention and non-training content handling remain unclear. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 7 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [Reader API and current limits](https://jina.ai/reader/): Official Product - [Legal information](https://jina.ai/legal/): Official Terms - [Elastic Privacy Statement](https://www.elastic.co/legal/privacy-statement): Official Privacy - [Elastic Customer Data Processing Addendum](https://www.elastic.co/legal/customer-dpa): Official Dpa - [Jina model catalog with current per-token USD rates](https://api.jina.ai/v1/models): Live Catalog - [jina-ai/reader, the official Reader API repository](https://github.com/jina-ai/reader): Official Repository - [ReaderLM-v2 first-party model card on Hugging Face](https://huggingface.co/jinaai/ReaderLM-v2): Official Repository ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.