← Back to leaderboard
Stripe

Stripe API

https://stripe.com · v2026-05-27.dahlia · 587 operations · 1422 schemas
37
F

Stripe's OpenAPI spec scores 37, an F. That is 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 AI agents need most. Examples and error documentation, the two pieces of context LLMs rely on hardest at the moment of constructing a call, are entirely absent.

Category breakdown

Examples0
Semantics78
Intent67
Error Handling0
Parameters70
Pagination69

Key findings

  • All 587 operations lack request and response examples
  • All 1,422 schemas lack examples
  • All 587 operations omit error response documentation
  • 1,149 of 1,422 schemas have no description
  • No RFC 9457 Problem Detail format detected in error responses

What Stripe should fix

  1. Add at least one request and response example per operation. Stripe's docs already contain these. The spec should mirror them.
  2. Document error responses (4xx, 5xx) on every operation. Adopting RFC 9457 Problem Detail format would be a major win.
  3. Add descriptions to the 1,149 schemas currently missing them. Agents use schema descriptions to disambiguate field semantics.
  4. Define global tags with descriptions so agents can navigate the API by domain (Payments, Subscriptions, Connect) rather than guessing.

Scored on 2026-05-25 from Stripe's public OpenAPI spec. View source spec · How scoring works

How does your API score?

Run AgenticScore on your own OpenAPI spec — find issues before LLMs do.

npx agenticscore score ./openapi.yaml
Install the CLI →