For engineering teams
Docs that keep pace with your shipping velocity.
Your reference goes stale the moment the code moves, and a new engineer pays for it on day one. Gravity reads your source and gateway, generates the reference for you, and catches drift in CI before it ships, so the docs are never the thing holding a release back.
Runs in the pipeline you already have. No new tools for your team to babysit.
A commit lands
A commit lands and CI runs, exactly as it does today.
Drift, caught in CI
Your build knows the docs are wrong before your users do
A check runs on every pull request and diffs your gateway against the published reference. When the code outpaces the docs, Gravity opens the fix as a proposal — so the reference is corrected in the same review, not weeks after a customer hits the gap.
- Runs as one step in the pipeline you already have
- Notices new, changed and removed endpoints and types
- Proposes the exact edit, bound to the code that changed it
- Fails loudly or stays advisory — your call, per repo
Your reviewed docs become dev-memory your agents can read
Expose your published, reviewed reference over MCP and every coding agent on your team can query it directly. The assistant answering “how does the billing service work?” pulls from your real documentation — the same source of truth your engineers read, so it stops inventing endpoints that never shipped.
- One connection, available to every agent and tool
- Always the reviewed, current version — never a snapshot
- Scoped to what each agent is allowed to see
Built for engineers
From the commit to the contract
The reference is generated from the things you already maintain — your source and your gateway — and stays bound to them. Precise where it counts, out of your way everywhere else.
API reference from the gateway
OpenAPI derived from your gateway, routes and types, bound block-by-block to the artifact it came from. We generate the spec where you do not already have one.
Drift caught in CI
When the code changes, the affected pages are flagged and the exact edit is proposed in the same pull request — reviewed and merged like any other change.
MCP dev-memory
Your reviewed reference is available to your coding agents over MCP, so humans and machines read one source of truth instead of guessing.
A map of the whole system
Services, packages and module boundaries laid out automatically, so a new engineer can navigate the codebase on day one instead of week three.
Fits the pipeline you have
A single check in CI, no new platform to run. Advisory or blocking per repo, so you adopt it without slowing a release down.
Published on your own domain
The generated reference ships as branded docs on your domain, current with main, ready for the engineers and partners who depend on your API.
Onboarding without the archaeology
A reference your team trusts on sight
The reference Gravity produces from your gateway and source — every endpoint, parameter and type, organised by service — is the map a new engineer needs, and it is current by construction.
- Navigable on day one
- Services, endpoints and module boundaries laid out automatically, so a new hire reads the system instead of pinging the channel that knows it.
- Always in step with main
- Because it is generated from the code, the reference a new engineer reads is the code that is actually running — not a snapshot from a release ago.
- Fewer interruptions for the team
- The questions that used to cost a senior engineer an afternoon are answered by the reference, and by the assistant that reads it.
- 0
- endpoints documented from source automatically
- 0
- drift fixes proposed in CI last quarter
- 0
- reference pages edited by hand to keep them current
- 0%
- of generated facts bound to a source
Go deeper
Explore the engine room
The engineering workflow rides on two parts of the platform. Both work as one governed system, from the commit to the customer.
How the reference is generated
See how Gravity reads your source and gateway, binds every fact to the code it came from, and keeps the reference true as the code moves.
Answers and dev-memory
Cited answers for your readers, and your reviewed docs exposed to every coding agent over MCP — one source of truth for humans and machines.
Point it at your repo.
Generate your reference from your source and gateway, and catch the first drift in CI today.