# Jina — API Agent Score

> Score: 72/100 (Grade: B) | Domain: jina.ai | Rubric: 1.0.0 | Checked: July 24, 2026

Jina scored 72/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/jina)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 72/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 90/100 (A+)
- Developer Experience: 48/100 (F)
- Agent Discovery: 78/100 (B)
- Agent Understanding: 70/100 (B)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://docs.jina.ai/authentication. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 486/697 (70%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 78%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="2026.07.23.0144" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [warn] Description completeness — 318/343 operations carry a description. Investigated: sdk 93%, spec 0%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://docs.jina.ai/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (jina-ai/reader, 120 snippets). Investigated: docs 100%, sdk 67%, cli 50%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 63%.
- [warn] llms.txt present, valid & comprehensive — llms.txt exists but contains no parseable links. Investigated: docs 60%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 10 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%, sdk 0%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Operation purpose clarity — 63% of operations are agent-inferable (target 90%+). Investigated: spec 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 2% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 3 list endpoint(s). Investigated: docs 100%, spec 75%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Jina's API contract is a genuine strength — the machine-readable spec and schema quality give partners and agents a solid foundation to build on. The two areas that need urgent attention are Developer Experience and Agent Understanding: partners have no self-service portal, no changelog, and no inline code samples, making onboarding slow and opaque; and agents lack the structured context files, runnable examples, and rate-limit signals they need to integrate reliably without human intervention. Fixing the onboarding and agent-context gaps in parallel will unblock both human partners and the AI agents they rely on.