← Back to leaderboard
Stripe API
46
D
Stripe's OpenAPI spec scores a D — surprisingly low for one of the most respected developer APIs in the industry. The disconnect is striking: Stripe's human-facing documentation is widely considered exceptional, but the spec itself omits the structured signals that AI agents need most. Examples and error documentation — the two pieces of context LLMs lean on hardest — are entirely absent.
Category breakdown
Examples0
Semantics79
Intent71
Error Handling0
Parameters70
Pagination69
Key findings
- All 587 operations lack request/response examples
- All 1,385 schemas lack examples
- All 587 operations omit error response documentation
- 1,118 of 1,385 schemas have no description
- No global tags with descriptions defined
What Stripe should fix
- Add at least one request and response example per operation. Stripe's docs already contain these; the spec should mirror them.
- Document error responses (4xx, 5xx) on every operation. Adopting RFC 9457 Problem Detail format would be a major win.
- Add descriptions to the 1,118 schemas currently missing them. Agents use schema descriptions to disambiguate field semantics.
- Define global tags with descriptions so agents can navigate the API by domain (Payments, Subscriptions, Connect, etc.) rather than guessing.
How does your API score?
Run AgenticScore on your own OpenAPI spec — find issues before LLMs do.
npx agenticscore score ./openapi.yaml
Get API Key →