Spec drift is the gap that grows between what your OpenAPI spec documents and what your API actually returns. It's the single biggest source of integration bugs — and almost nobody checks for it.
string → integer) and only the consumers notice.Most drift tooling — including the popular oasdiff — compares two spec files. They explicitly cannot tell you whether your live API matches your spec, because they never touch a running endpoint. That's the gap DriftWire fills.
# probe live endpoints and validate every response against the spec
driftwire check openapi.yaml --url https://api.example.com
# reports type mismatches, undocumented fields, missing required,
# and enum violations — exit 1 when drift is foundRun it locally during development, or as a CI step that gates deploys the same way unit tests do. No uploads, no telemetry, no account — responses never leave your machine.
Paste two specs into the live demo and watch the diff engine flag breaking changes instantly:
▶ Open the live demo View source (MIT)