THE API CHANGE WORKBENCH / 01
See what your next API release stops accepting.Trace the change. Test a counterexample. Plan the migration.
OpenAPI 3.0.x · JSON or YAML · local refs only · 1 MiB per spec
A focused check, not a compatibility certificate. Unsupported constraints are routed to manual review.
No account. No API keys. No server upload. Specs are held in this tab's memory and are not saved after reload. Export only what you choose.
Contract Lens compares a deliberate subset of OpenAPI 3.0 schemas. No findings does not mean an API release is safe.
Existing path+method removal; new required parameters and bodies; request media removal; JSON-shaped schema type, enum, required properties, extra-property rules, nested objects, array items, numeric bounds and length/item bounds. Response schemas run in the reverse direction. Local $refs are traced into each affected operation.
Composition (oneOf/allOf/anyOf), pattern/format, recursive or external refs, readOnly/writeOnly projections, security, response headers, serialization changes and unrecognized schema keywords. Exact path matching only, no renamed-path inference. Status/media handling is heuristic. Removed statuses and some body/header changes are not exhaustively checked. Runtime behavior and business semantics are outside scope.
A bounded candidate search checks the source schema accepts a payload and the target rejects it. Verified means within this supported validator, not against a live server. Structural findings without a witness remain potential risks. Sampling limits can miss payloads.
All analysis is local. No analytics or external API calls. No YAML aliases, unsafe prototype keys, remote refs or spec over 1 MiB. Structural depth/node limits apply. This is a prototype, not a hardened parser for hostile inputs. Do not paste secrets into specs, reports or public issue trackers.