Generate from the spec
OpenAPI 3.x becomes endpoint pages with synthesized examples and three-language samples.
Solutions
Documentation your API can be judged by.
OpenAPI in, living reference out: examples, code samples, a safe playground, and AI agent surfaces that respect your permissions.
What API teams do with GraphStaff
Ship the reference with the API.
Let developers try it
A host-allowlisted proxy playground runs real calls without exposing keys.
Version what you ship
Docs versions with version-scoped search and assistant answers.
Serve the AI agents too
MCP, llms.txt, and Markdown twins publish beside the human site.
Scoped by reader
Partner endpoints stay partner-only.
Reader groups scope the reference like any other page, and the scoping follows into search, Ask AI, and MCP.
More solutions
Questions, answered
Frequently asked questions.
The short version of what teams usually want to know before they see GraphStaff in action.
Which formats are supported?
OpenAPI 3.x, including multi-file specs with external references. AsyncAPI and Swagger 2.0 are not supported today.
Do you detect breaking changes?
No. GraphStaff versions and publishes docs. It does not diff specs or generate changelogs today.
Can each developer see their own keys and request logs?
No. GraphStaff governs content and answers. It does not ingest API telemetry or manage developer keys.
How do docs deploy?
Push to git. CI validates, pull requests get preview URLs, and merge ships to production.
See it with your knowledge
A reference that keeps its promises.
Send a spec, even a messy one. We will return a live reference you can judge.