Your OpenAPI spec is lying
Most OpenAPI files describe the API somebody intended to build. The server has been changing since....
Tag archive
Most OpenAPI files describe the API somebody intended to build. The server has been changing since....
A successful scan rebuilds the contract from code, but it does not prove conformance or correctness; verify runtime behavior with tests and scenarios.
AI fills bounded per-handler slices for specific gap codes, but it cannot invent a route, method, or path; deterministic extraction proves the structure.
The gate classifies every parameter and response as proven, proven-empty, or gap, so a route is never emitted as a bare URL with empty contracts.
The x-a2a extension holds version, binding, endpoint, method, card URL, contracts, and examples. It is a vendor extension, not a standard OpenAPI keyword.
Scan a local backend to reverse-engineer an OpenAPI 3.2 document through deterministic framework tracing and AST analysis, with AI filling only gaps.
Deterministic extraction proves routes through framework tracing and AST analysis, so lookalikes are not mistaken for routes, unlike name-based guessing.
The four layers are Observed live tables, Modeled status and diffs, Proposed additive migration with blockedBy, and Inferred link tables.
A scanned OpenAPI gives real routes and contracts to build ordered scenarios from, chaining requests and asserting at each step.
A router that exists but is never mounted leaves its routes unreachable. The scan reports them instead of treating defined paths as live endpoints.
Before adopting a scanned spec, confirm each route is mounted and reachable, check its gate status, and trace gaps and unmounted routers.
Incremental rescans use a discovery sidecar to update only what changed, preserving your edits to the generated document instead of rebuilding it.