Docs developers and LLMs both love
Publier turns your OpenAPI spec and MDX source into a developer-first, AI-native doc site — with try-it playgrounds, SDK tabs, and a first-class MCP endpoint.
Real APIs, not just prose
Point Publier at your OpenAPI 3.1 spec and get a complete reference — request/response schemas, endpoint pages, and a try-it playground rendered from the same source of truth your code generates.
- OpenAPI 3.1 and AsyncAPI 3.0 both supported out of the box
- Copy-as-curl, fetch, Python, Go, Java, and C# — one click
- SDK tabs auto-wired to each operation
curl https://api.publier.net/v1/messages \
-H "Authorization: Bearer <token>" \
-d '{"model":"opus-4-7","messages":[...]}'
LLMs, not just search boxes
Agents that answer your developers' questions need structured context. Publier ships an MCP server at every tier plus canonical markdown feeds and llms.txt — LLMs crawl your reference as reliably as GitHub Copilot crawls your repo.
- MCP server auto-generated from every page, no config
- /llms.txt and /llms-full.txt built at ship time
- Per-endpoint agent analytics — see who is retrieving what
Docs live where code lives
Every page is MDX in your repo. Pull-request previews, review comments, and revert are the same workflow your engineers already know — no third-party CMS, no content staging UI, no drift.
- MDX + YAML config — lint, grep, diff like any code
- Pull-request previews per branch, built in CI
- Astro content collections give you typed frontmatter
Ship developer docs this week
One command scaffolds a working OpenAPI-powered doc site. No vendor lock-in, no per-seat tax.