Docusaurus

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Use an official CLI G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Build against official SDKs G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Point an agent at llms.txt or agent-oriented docs G

Agent access

Rely on versioned APIs with a documented deprecation policy G

Api quality

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Issue scoped/least-privilege API credentials for an agent G

Agent access

Operate the product with natural-language commands G

Agentic features

Set up automations that run autonomously in the background G

Agentic features

Subscribe to events via webhooks G

Agent access

Test against a sandbox environment without touching production data G

Api quality

I publish versioned documentation per product or API version, and readers switch versions from the site C

Versioning

Self-host the core product G

Export all of my data in open formats and leave G

My docs live in my own git repository — branches, pull requests, and merges drive what gets published C

Git workflow

I author pages in Markdown/MDX with rich components — tabs, callouts, code groups, steps — without writing custom HTML C

Authoring

Readers get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the box C

Search

Every published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTML C

Agent output

My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes C

Spec driven

My published docs site automatically serves llms.txt (and a full-content variant) so agents can index it C

Agent output

My published docs site exposes its own MCP server that my users' agents can query for search and page content C

Agent access

Define rules that trigger actions automatically on events G

Prevent my data from being used to train AI models G

Export my entire docs site as a static bundle and host it anywhere, so my content is never locked in C

Portability

I customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brand C

Theming

Read the product's source under an open license G

I serve docs on my own custom domain or as a /docs subpath of my main site C

Domains

Choose where my data is stored (region/residency) G

Do everything through the API that I can do in the UI G

Every docs pull request gets a shareable preview deployment before it merges C

Git workflow

Perform bulk operations across many items at once G

Readers can try real API calls from an interactive playground embedded in the reference docs C

Playground

A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests C

Writer agent

An embedded AI assistant on my docs site answers reader questions with citations into my content C

Assistant

Automated checks lint my content against a style guide and flag issues before they publish C

Quality

CI validation catches broken links and invalid configuration before the site publishes C

Quality gates

Control data retention and deletion G

I see page views, search terms, and reader feedback so I know which docs work and which fail C

Analytics

My docs analytics distinguish AI-agent traffic from human traffic so I can see who — or what — is actually reading C

Analytics

Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth C

Authoring

Opt out of telemetry and usage tracking G

Schedule recurring jobs or workflows G

Teammates propose changes that go through review — comments, approvals, and a merge step — before they publish C

Review

I publish my docs in multiple languages with translated navigation and content C

Localization

Reusable snippets and variables keep repeated content in sync across pages C

Content reuse

I gate some or all docs behind authentication — password, JWT, or SSO — for customers-only content G

Access control

Version, review, and roll back my automations G