OpenAPI Petstore
80/100
Excellent
confidence: high
Complexity 2/10 (Simple) —
RCS=5, adj=-1, ECS=4
· Doc coverage: high
· OpenAPI 3.1.0 · 20 endpoints · 6 schemas
Signals
| Signal | Value | Bucket | Pts | Source |
|---|---|---|---|---|
| auth_required securitySchemes: petstore_auth, api_key |
optional | optional | 1 | spec |
| total_endpoints | 20 | 6-20 | 1 | spec |
| schema_depth | 2 | shallow | 0 | spec |
| avg_response_size_kb 3 documented example(s) sampled |
0.12 | <=5 | 0 | examples |
| error_surface documented responses: 400, 404, 405 |
3 | low | 0 | spec |
| error_codes_count documented responses: 400, 404, 405 |
3 | 0-3 | 0 | spec |
| pagination_supported | false | no | 0 | spec |
| pagination_pattern | none | none | 0 | spec |
| parameter_complexity | medium | medium | 1 | spec |
| rate_limiting documented header 'x-ratelimit-limit' · documented header 'x-ratelimit-remaining' · documented header 'x-ratelimit-reset' |
3 | complex | 2 | spec |
Recommendations
- Rate limiting is documented — ensure quota tiers are stated and agents are told to honor `Retry-After` / `X-RateLimit-Reset` when backing off.
- Authentication is declared — make sure credential acquisition is also documented (where to obtain keys/tokens, scopes needed) so an agent operator can set up access.
- Large surface area: scope the AI agent to a focused subset of endpoints, or split the spec into smaller domains.
- Reduce parameter count, simplify nested object parameters, or document each parameter's role; AI selects parameters from descriptions.