Swagger Petstore - OpenAPI 3.0 spec score
Octri scored the public spec at https://petstore3.swagger.io/api/v3/openapi.json for what a code generator can do with it. This is a reading of the document, not a grade of the API.
19 operations · 6 models · 3 tags · OpenAPI 3.0.4
Scored 26 October 2026 · fingerprint aa8f3e20c4f7… · spec version 1.0.28
Document last changed 26 October 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 | 0.8 lost | 5 of 19 operations | DELETE /user/{username}PUT /user/{username}DELETE /pet/{petId}and 2 more |
| Shared models live in components and are $ref'dshared-schemas-referenced | 2.0 | Clean | 19 operations clean | Nothing found |
| Generated public names do not collideoperation-id-unique | 2.0 | Clean | 19 operations clean | Nothing found |
| Every path placeholder has a parameterpath-parameters-declared | 1.5 | Clean | 19 operations clean | Nothing found |
| Every operation declares an operationIdoperation-id-present | 1.0 | Clean | 19 operations clean | Nothing found |
| operationIds read as method namesoperation-id-naming | 1.0 | Clean | 19 operations clean | Nothing found |
| Operations carry a summary or descriptionoperation-documented | 1.0 | Clean | 19 operations clean | Nothing found |
| Request bodies are documentedrequest-body-documented | 1.0 | 0.3 lost | 3 of 19 operations | POST /user/createWithListPOST /pet/{petId}/uploadImagePOST /store/order |
| Failure responses are declarederror-responses | 1.0 | Clean | 19 operations clean | Nothing found |
| Operations are taggedoperation-tagged | 1.0 | Clean | 19 operations clean | Nothing found |
| No duplicate or equivalent pathsduplicate-paths | 1.0 | Clean | 13 paths clean | Nothing found |
| Authentication is describedsecurity-declared | 1.0 | Clean | Declared | Nothing found |
| Parameters explain their purposeparameters-documented | 0.75 | 0.18 lost | 1 of 19 operations | DELETE /pet/{petId}#header:api_key |
| A server URL is declaredserver-url | 0.5 | Clean | Declared | Nothing found |
What 8.7 means for an SDK
A strong reading, and the three rules that decide most of it.
A generator has what it needs here: typed methods, named models and doc comments that say something. What is left is polish, and it can wait until after the first release.
Three rules carry six of the 10 points between them. On this document they took 0.82.
−0.8
Successful responses declare a schema
5 of 19 operations
Clean
Shared models live in components and are $ref'd
19 operations clean
Clean
Generated public names do not collide
19 operations clean
What to change first
Every rule that deducted, in the order they cost.
0.8 lost
Successful responses declare a schema
Give the success response a schema, or a $ref to one in components. A 204 needs nothing.
Inside Octri this one has a one-click fix.
0.3 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.
0.18 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 petstore3.swagger.io 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 Swagger Petstore - OpenAPI 3.0.