Stripe API OpenAPI spec score
Octri scored the public spec at https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json for what a code generator can do with it. This is a reading of the document, not a grade of the API.
612 operations · 1538 models · 0 tags · OpenAPI 3.0.0
Scored 30 September 2026 · fingerprint 7cff4cc46d06… · spec version 2026-09-30.endive · server api.stripe.com
Document last changed 30 September 2026.
Where the points went
Every rule, heaviest first, with what it cost this document, how much of the surface it touched, and where. The rule id links to what that rule checks.
| Rule | Weight | Result | Surface | Locations |
|---|---|---|---|---|
| Successful responses declare a schemaresponse-schema | 2.0 | Clean | 612 operations clean | Nothing found |
| Shared models live in components and are $ref'dshared-schemas-referenced | 2.0 | 0.5 lost | 20 of 612 operations | data, has_more, object, urlbank_account, default_for_currency, expand, external_accountaccount_holder_name, account_holder_type, account_type, address_cityand 17 more |
| Generated public names do not collideoperation-id-unique | 2.0 | Clean | 612 operations clean | Nothing found |
| Every path placeholder has a parameterpath-parameters-declared | 1.5 | Clean | 612 operations clean | Nothing found |
| Every operation declares an operationIdoperation-id-present | 1.0 | Clean | 612 operations clean | Nothing found |
| operationIds read as method namesoperation-id-naming | 1.0 | 0.6 lost | 309 of 612 operations | POST /v1/account_linksPOST /v1/account_sessionsPOST /v1/accountsand 306 more |
| Operations carry a summary or descriptionoperation-documented | 1.0 | 0.2 lost | 5 of 612 operations | POST /v1/application_fees/{id}/refundPOST /v1/charges/{charge}/disputePOST /v1/charges/{charge}/dispute/closeand 2 more |
| Request bodies are documentedrequest-body-documented | 1.0 | 0.6 lost | 298 of 612 operations | GET /v1/accountGET /v1/accountsDELETE /v1/accounts/{account}and 295 more |
| Failure responses are declarederror-responses | 1.0 | Clean | 612 operations clean | Nothing found |
| Operations are taggedoperation-tagged | 1.0 | 1.0 lost | 612 of 612 operations | GET /v1/accountPOST /v1/account_linksPOST /v1/account_sessionsand 609 more |
| No duplicate or equivalent pathsduplicate-paths | 1.0 | Clean | 431 paths clean | Nothing found |
| Authentication is describedsecurity-declared | 1.0 | Clean | Declared | Nothing found |
| Parameters explain their purposeparameters-documented | 0.75 | 0.56 lost | 422 of 612 operations | DELETE /v1/accounts/{account}#path:accountGET /v1/accounts/{account}#path:accountPOST /v1/accounts/{account}#path:accountand 419 more |
| A server URL is declaredserver-url | 0.5 | Clean | Declared | Nothing found |
Packaging, outside the score
This generates one package with 612 operations and 1538 models. Frontend consumers download all of it to call any of it, and low-spec machines pay for it in IDE and build time. The largest groups are `v1` (612), and each is a candidate for its own project.
What 6.6 means for an SDK
A mixed reading, and the three rules that decide most of it.
The client compiles and works. Callers will feel the soft spots: a few methods that return an untyped value, arguments with no hint on them, a namespace or two named after a path segment rather than a resource.
Three rules carry six of the 10 points between them. On this document they took 0.45.
Clean
Successful responses declare a schema
612 operations clean
−0.5
Shared models live in components and are $ref'd
20 of 612 operations
Clean
Generated public names do not collide
612 operations clean
What to change first
Every rule that deducted, in the order they cost.
0.5 lost
Shared models live in components and are $ref'd
Move the shape into components.schemas once and $ref it from each operation that returns or accepts it.
0.6 lost
operationIds read as method names
Name the id for the action, not the route. The audit suggests one per operation and can apply it.
Inside Octri this one has a one-click fix.
0.2 lost
Operations carry a summary or description
Write one sentence of summary. It lands on the reference page and in the SDK's doc comment.
Inside Octri this one has a one-click fix.
0.6 lost
Request bodies are documented
Describe the body, or the fields inside it. Field-level prose is the one that reaches the SDK's arguments.
Inside Octri this one has a one-click fix.
1.0 lost
Operations are tagged
Tag every operation. Tags are what decide whether a caller writes `client.invoices.list()` or `client.misc.list()`.
Inside Octri this one has a one-click fix.
0.56 lost
Parameters explain their purpose
Describe what the parameter does and what a valid value looks like. One line each.
Inside Octri this one has a one-click fix.
Where to go next
- Score your own spec The same fourteen rules, on any public URL. No account, and the spec is not kept.
- OpenAPI to a TypeScript SDK Published to npm, with the type definitions generated from your spec.
- OpenAPI to an MCP server The same endpoints, as tools an agent can call.
- How SDK Studio shapes a client Naming, hooks and packaging, decided before ten runtimes are built.
The spec at raw.githubusercontent.com is public. Octri keeps the `info` block, the score, and up to five sample finding locations per rule. The document itself is not stored and is not served from here. The audit predicts what an SDK generator can do with the description; it is not a security review, an uptime measurement or a critique of the API’s design. This page is not affiliated with Stripe API or Stripe Dev Platform Team.