FastAPI gives you OpenAPI for free — but the prose docs, guides, and examples around it still rot. docs-keeper parses your routers and Pydantic schemas and drafts the narrative documentation that the auto-generated spec can’t.
Endpoint docs that never drift
docs-keeper reads your FastAPI routers and Pydantic models and keeps the human-readable docs in lockstep.
What docs-keeper keeps in sync
Endpoint guides
Path operations documented with real request/response models and dependencies.
Pydantic schemas
Model fields and validation explained from the schema definitions.
Auth & dependencies
Security dependencies and middleware described as they change.
Quickstarts
Runnable examples updated when signatures change — and sandbox-validated where enabled.
Docs it writes for FastAPI
README.mdAPI guideSchema referenceCHANGELOG.mdTutorial
Frequently asked
I already have /docs from OpenAPI — why this?
The OpenAPI UI documents the contract; it doesn’t write your quickstart, tutorials, or conceptual guides. docs-keeper drafts that prose and keeps it grounded in your code.
Are code examples checked?
Where snippet validation is enabled, examples are compiled in an isolated sandbox before a PR is opened.
Does it understand async routes?
Yes — async def path operations are parsed the same as sync ones.
Try docs-keeper on your FastAPI repo
One public repo, 20 doc PRs per month, no credit card. See if drafts read like your team before committing to a paid plan.