01
Connect the repo
Install the GitHub App and point doxa at your docs.json. The repo stays the source of truth.
NewSelf-updating docs, powered by agents→
Documentation that keeps up with your code
doxa turns a GitHub repo into a living docs site — generated, published, and maintained by an AI agent that reads your code and opens pull requests.
Mintlify-compatible docs.jsonllms.txt + MCP built inPublish on every push
Getting started
Quickstart
Ship your first docs site in minutes — point doxa at a repo and publish.
Chapter 01 — The drift
Every sprint ships new endpoints, new flags, new behavior. Your documentation doesn't notice. It drifts, quietly, until readers stop trusting a word of it.
0
0
402d417feat: rotate API keys without downtime8119bfffeat(auth): device authorization flowd510582refactor: split billing service27b5b90feat: usage-based quotas61eccb2feat: new /v2/exports endpointChapter 02 — The fixPlug doxa in.
Plug doxa in.
The story changes.
02
Publish on every push
Each push ships a fast, themeable site — versions, tabs, OpenAPI playground, ⌘K search.
03
Let the agent maintain it
On merges and schedules, the agent edits docs in an isolated sandbox and opens a pull request you review.
Chapter 03 — In the product
From push to pull request
Dashboard — deployments
Push to publish
Merge to main and doxa fetches the repo, validates docs.json, imports every page, and reindexes the assistant — live in seconds.
18:42:09Deploy started — acme/api@main18:42:10Resolved commit 402d417.18:42:10docs.json is valid.18:42:14Imported 101 page(s), pruned 0.18:42:15Indexing pages for the assistant…18:42:21✓ Deployed — 101 pages liveDashboard — workflows
An agent on the docs team
Workflows watch merges and schedules. The agent clones your repo into a sandbox, reads the real source, edits the docs — and opens a PR you review. Never silent overwrites.
✦
✦
✦
⇡
PR #128 docs: update for #341 +3 files
Docs site — assistant
Answers with receipts
Every site ships an AI assistant that understands the whole corpus and cites the exact page — plus llms.txt and an MCP server, so the models your users already ask stay current too.
How do I rotate an API key without downtime?
Create a second key, deploy it, then revoke the old one — keys overlap so requests never fail mid-rotation.↳ guides/authentication.mdx
Ask anything about your docs…↑
Built for humans — and the models they ask
Bring your docs to life
Start free, connect a repo, and watch your documentation maintain itself.