Open criteria. Private analysis.
Your spec never leaves your browser.
AI agents and MCP servers call your API through its OpenAPI spec. When the spec is vague, the agent guesses, and guesses become wrong calls. AptessaAPI checks a spec against an open framework of 37 rules in 10 dimensions. Try 8 of them now.
Free check
Paste a spec instead
OpenAPI 3.0 or 3.1, YAML or JSON, up to 5 MB. The file is read on this device and not uploaded anywhere.
What the full framework checks
Ten dimensions of what an agent needs from a spec. The criteria are open; your analysis stays private.
- Descriptions an LLM can use. Operations, parameters and enum values explain themselves.
- Operation naming. Readable operationIds, one job per operation, predictable REST, safe retries.
- Auth agents can handle. Standard schemes, scopes in the spec, no interactive steps or deprecated grants.
- Machine-readable errors. One structured format that says what can be retried.
- Strict schemas. Typed responses, explicit required and nullable fields, enums.
- Consistent pagination. One scheme, with its metadata in the response.
- Lifecycle hygiene. Deprecations with sunset dates, explicit versions, stable operationIds.
- Discoverability. Inline examples, documented rate limits, a spec and llms.txt at known places.
- ISO data formats. Currencies, countries, languages and dates in their standard codes.
- Security posture. Auth on writes, no secrets in the spec or the URL, https everywhere, typed sensitive fields.
Get the full report
The full check covers all 37 rules. Join the waitlist and you'll hear when it opens. You'll get a confirmation email first.