# RevenueCat — API Agent Score

> Score: 83/100 (Grade: A) | Domain: revenuecat.com | Rubric: 1.0.0 | Checked: September 28, 2026

RevenueCat scored 83/100 (A), classified "ai-ready".

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

## Summary

- Overall: 83/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 88/100 (A)
- Developer Experience: 72/100 (B)
- Agent Discovery: 97/100 (A+)
- Agent Understanding: 88/100 (A)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "2.0.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 6 of 46 public signatures use loose types (anyTypeRatio=0.130). Investigated: sdk 64%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://app.revenuecat.com/signup, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.revenuecat.com/docs/getting-started/quickstart includes a runnable first-call code sample. Investigated: docs 100%.
- [fail] Description completeness — 18/18 operations lack a description. Investigated: sdk 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms.txt found at 2 locations; using https://www.revenuecat.com/docs/llms.txt as canonical. Investigated: docs 100%, sdk 0%.
- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/revenuecat, 6330 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 2 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — error codes is documented on the docs site at https://www.revenuecat.com/docs/test-and-launch/errors, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, sdk 0%.
- [warn] Agent-navigable, token-efficient docs — 1 of 50 pages between 50K–100K chars (max 54K). Investigated: docs 100%.
- [warn] Operation purpose clarity — Read/write classification is mostly ambiguous: only 8/18 operations classified. Investigated: sdk 72%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

RevenueCat's API program shows strong structural foundations — contract shape, schema typing, and agent discoverability are all in good standing. The two areas most likely to slow down partners are documentation quality and operational transparency: every single API operation is shipped without a description, and there is no changelog or rate-limit signaling anywhere in the spec or docs. Partners and their agents cannot self-serve through integration without understanding what each endpoint does or how to handle throttling and breaking changes. Prioritize adding operation descriptions and a changelog immediately, then close the rate-limit gap to make production integrations reliable.