◎ Discry Score
stripe.com
payments · API
B
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 94 (A)
Discry your API →
PAYMENTS · RANK #6 OF 25

Stripe is Good to agents.

Discry independently scored how well an AI agent can discover and understand the Stripe API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 71/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass
llms.txtAn llms.txt index that points agents to the docs that matter.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Partial
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 96/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Pass
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • Stripe's documentation quality remains best-in-class — task-oriented descriptions, realistic examples in 10+ languages, comprehensive error handling guides with recovery steps
  • The llms.txt at 93KB exceeds the ideal 50KB threshold but is well-structured and API-focused
  • Stripe explicitly signals AI welcome via Content-Signal: ai-train=yes, ai-input=yes in robots.txt
  • Official MCP server at mcp.stripe.com with OAuth support — listed on PulseMCP and Glama with remote server capabilities
  • OpenAPI spec is publicly maintained at github.com/stripe/openapi with both JSON and YAML formats covering v1 and v2 APIs

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add .well-known/mcp.json at docs.stripe.com or stripe.com pointing to mcp.stripe.com
  2. 02Create a focused llms.txt under 50KB covering core payment flows, or split into llms.txt (concise) + llms-full.txt (comprehensive)
  3. 03Add AGENTS.md to stripe/stripe-node or stripe/openapi GitHub repos with context for coding agents
  4. 04Add llms-full.txt with the complete API documentation in markdown

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

api_keyoauth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✓ Idempotency documented

Comprehensive execution documentation. Bearer token API key auth. Versioned API with date-based versions. JSON error responses with type, code, message, and param fields. Rate limits documented (100 read/s, 100 write/s). Cursor-based pagination. Idempotency-Key header supported with 24hr retention.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free