Guides
One guide per framework. Each says where that framework’s OpenAPI document comes from, how to run apidrifter against the live app, how to read a real finding and decide which side to fix, and how to make the check automatic with an instructions file, the Claude Code hook and a CI job. Every guide has a runnable example in the repository with a deliberate mismatch, so the findings shown are real output.
Verify your FastAPI app against its OpenAPI spec
The document comes from the type hints at /openapi.json; the drift hides where handlers bypass response_model.
Verify your Express app against its OpenAPI spec
A hand-written openapi.yaml beside server.js; the drift is a field the server grew and the document never got.
Verify your Hono app against its OpenAPI spec
Zod schemas generate the document; the drift is a value in the store that the enum never learned about.
Verify your Fastify app against its OpenAPI spec
Route schemas generate the document and serialize responses; the drift is a status code the schema never listed.
Verify your NestJS app against its OpenAPI spec
Decorators generate the document; the drift is a DTO property that is required on paper and optional in the service.
Other frameworks
The loop is the same for anything that speaks HTTP and has an OpenAPI 3 document: start the app, run npx apidrifter run <spec> --base-url http://localhost:<port>, read the two fixes on each finding, pick a side. Theagents page has the instructions paragraph and MCP setup that work for any codebase; the CLI reference has every flag. The examples live at examples/ in the repository.
Last reviewed 2026-11-03