# Rev — API Agent Score

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

Rev scored 77/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 76/100 (B)
- Agent Discovery: 86/100 (A)
- Agent Understanding: 80/100 (A)
- Agent Usability: 57/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 6/6 enums are named types (not bare strings). Investigated: sdk 100%, spec 58%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 88%, docs 75%.
- [warn] Auth declared & discoverable — Authentication applied on 16/53 operations (partial coverage). Investigated: spec 88%, docs 88%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 79% example coverage (target 80%+). Investigated: spec 100%, docs 100%, sdk 100%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://docs.rev.ai/get-started has a runnable sample in the .md variant (https://docs.rev.ai/get-started.md). Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 3/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 38% description completeness. Investigated: spec 100%, sdk 0%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.rev.ai/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [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%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (clash-verge-rev/clash-verge-rev, 60 snippets). Investigated: docs 100%, sdk 58%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Content negotiation partially supported: 25 correct type, 0 wrong type, 16 HTML only. Investigated: docs 88%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 79%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 9 of 41 pages have substantive content differences between markdown and HTML (avg 11% missing). Investigated: docs 80%.
- [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 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 50%.
- [warn] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: docs 67%, spec 50%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [warn] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 13%, docs 13%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Rev's API design and discoverability foundations are strong, and crawlability is already working in its favor. The two areas holding back partner and agent success are agent understanding — AI agents lack the structured context files and metadata they need to correctly interpret and act on Rev's APIs — and agent usability, where missing rate-limit signals put partner integrations at risk of silent failures. Prioritize giving agents a clear, parseable context layer first, then close the operational reliability gap so partners can run production workflows with confidence.