OpenAPI intelligence for agentic systems

Your API is valid.
Is it agent-ready?

Paste, upload, or import a public OpenAPI URL, then measure whether an AI agent can discover the right operation, construct it correctly, and interpret the result safely.

DeterministicVersioned rules, stable results
Private by defaultRaw specs not retained
Agent-nativex402 + MCP artifacts
readiness audit
$ audit ./openapi.yaml
72usable with warnings

CRITICAL response schema missing

/paths/~1invoices/post/responses/200

HIGH mutation semantics unclear

/paths/~1invoices/post
2 safe patches · 4 MCP candidates
From contract to confidence

A linter checks syntax.
This checks usefulness.

Every result is traceable to a stable rule, an exact JSON Pointer, and a clear impact on agent behavior.

01

Find semantic gaps

Catch contracts that validate cleanly but leave agents guessing when, why, and how to call an operation.

02

Apply safe repairs

Receive RFC 6902 patches only when a change can be derived mechanically—never invented business semantics.

03

Shape MCP tools

Generate focused candidate tool bundles with collision-safe names, input schemas, and explicit mutation risk.

Free contract check

See what an agent sees.

Paste, upload, or import a public URL for an OpenAPI 3.0 or 3.1 contract. Your document is processed in memory and never saved.

Browser-safe URL import
Guided examples

Explore three audit outcomes

Load a focused contract, run the free score, and compare what passes with the gaps an agent would encounter.

mutation-needs-work.yaml

Direct public HTTPS files only. GitHub file links are converted automatically; credentials are never sent.

Ready when your contract is

Run the score to reveal structural gaps, ambiguous operations, unsafe mutations, and weak response contracts.