Developer Docs and API Docs

Documentation built for builders and the AI agents building with them.

One polished home for guides, API reference, and grounded answers, with native access for the coding agents your developers already use.

Your Company create-a-matter API reference page in GraphStaff

Documentation for people

A reading experience that earns trust.

Guides, API reference, examples, and search stay in one coherent interface, and every answer stays connected to a page your team owns.

docs.yourcompany.com Live

Your Company developer documentation in light mode

YOUR DOCSOne maintained sourceGuides · APIs · examples

MCP serverllms.txtMarkdown pagesWebsite Ask AI

AI TOOLSNative documentation accessSearch · list · grep · fetch

Documentation for AI agents

Readers get a website. AI agents get MCP.

GraphStaff publishes MCP, llms.txt, and Markdown interfaces beside the human site, so AI agents retrieve exact, current pages instead of scraping and guessing.

An MCP server to hand out

Your docs get their own MCP server. Give it to your customers.

GraphStaff spins it up automatically when you publish. Customers add it to Claude, ChatGPT, or their coding agent, and the AI agent reads your current reference and writes working code for your product.

Your customer’s coding agentdocs.yourcompany.com/mcp

Add plan upgrades to our billing page.

mcp · search("update subscription plan")→ Update a subscription · API reference

Your docs route plan changes through the subscriptions endpoint:await yourco.subscriptions.update(id, { plan: "pro" })Written from your current reference

Private docs included

Private docs ship on every plan.

Protect partner references, beta docs, and internal knowledge. The same permissions follow the reader into search, Ask AI, and AI agent retrieval.

docs.yourcompany.comVisitorPartner

Quickstart guidePublic

✓✓

Core API referencePublic

✓✓

Partner API endpointsPartners only

–✓

Beta feature docsBeta program

–✓

Same rules inSearchAsk AIMCP

Questions, answered

Frequently asked questions.

The short version of what teams usually want to know before they see GraphStaff in action.

Does GraphStaff support both guides and API reference documentation?

Yes. GraphStaff brings narrative developer guides and generated API references into one experience so readers can move from concepts to endpoints without changing products.

What does GraphStaff generate for AI agents?

Every documentation site can expose an MCP server, llms.txt and llms-full.txt indexes, and a clean Markdown version of each page. These surfaces give AI agents direct, structured ways to search and read the same maintained documentation.

How do authors edit and publish documentation?

GraphStaff is being designed to support the workflows teams actually use. That may include repository-based publishing as well as a collaborative editor. We will choose the right authoring workflow with each early customer rather than forcing one model.

Can private developer documentation use Ask AI and MCP?

Yes. Identity and group permissions apply to the website, search, Ask AI, and MCP retrieval. Private pages are excluded before an answer or AI agent response is assembled.

See it with your knowledge

Make your documentation part of the developer workflow.

Show us the guides, API definitions, and questions your developers work with. We’ll show you the human and AI agent experience together.