Built for OpenAPI
Your spec is the source of truth. Docs update automatically.
Agent-friendly
Serve /llms.txt and structured context so agents can use your API out of the box.
Docs as Code
Write docs in Markdown, review in GitHub, and deploy with your CI pipeline.
SEO & Performance Optimized
High-performing docs for search engines.
People don't read docs the same way anymore, just like we don't write code the same way. We needed to optimize for agents, and Fern's llms.txt and markdown serving let us do that. All our documentation is written agentically with minimal human intervention and lots of automation.
Shashank GoyalFounding Engineer
Edit docs the way your team works. We ship a CLI, Fern Writer, and GitHub Actions so writers, engineers, and agents all contribute to the same repo.
Docs and MCP servers all derive from the same spec. Change one thing upstream and the entire surface regenerates. Nothing drifts, nothing falls out of sync.
Plus, add SDKs in 7 supported languages at any time.
Edit, measure, and improve your docs from a single dashboard. See what developers search for, where they get stuck, and ship updates to resolve them.
Spot 404s, drop-offs, and popular paths, then redirect or rewrite to keep developers moving.
See what developers search, ask the AI chat, and flag as feedback in one place. Then quickly ship updates to the answers they need.
Your docs are readable by every coding agent and easy to maintain by every human.
Your docs are served as clean Markdown, with an auto-generated llms.txt. Coding assistants, agents, and LLMs get accurate context about your API without any extra work from you.
Get your Agent-readiness score →Fern SDKs handle pagination automatically — list endpoints return an async iterator you can loop over directly.
Built-in AI chat lets users ask questions and get answers grounded in your docs, with no hallucinations or generic responses.
Every Fern docs site ships with a built-in MCP server. AI agents and coding assistants can query your API reference directly, no manual setup.
@Fern Writer Write a quick start guide for my Fern generated TypeScript SDK
PR created: github.com/your-company/docs/pull/3929
Tag Fern Writer to draft updates, open GitHub PRs, and keep your documentation in sync with what your team ships.
Beautiful out of the box, easy to maintain, and built to convert users.
MDX Guides
Write flexible, structured guides using MDX with support for custom components and layouts.
Generate API References
Automatically generate API reference docs from your spec, always up to date and consistent.
Changelog
Share updates to your API and docs with a built-in changelog that keeps users informed.
Git sync
Sync docs with your Git repo to version, review, and ship changes through pull requests.
API key injection
Automatically populate API keys so users can instantly make API calls and see realistic responses.
Access control (RBAC)
Assign role-based permissions and configure what content a user can access.
Federated authentication
Secure your documentation behind auth. Fern supports SSO, OAuth, and username + password.
Code editor
Edit your docs in a powerful code editor with syntax highlighting and live preview.
Writing agent
Generate and update docs from prompts or Slack threads using an AI-powered writing agent.
Web editor
Edit docs directly in the browser with a rich visual editor. No local setup required.
Preview links
Share a unique URL for every pull request so reviewers can see docs changes before they ship.
Versioning
Document and manage multiple versions of your product or API to support users across different releases.
Tabs
Organize content into tabs to separate audiences, products, or workflows cleanly.
Product switcher
Group multiple products under one docs site so users can switch between them without losing context.
Multiple repos
Aggregate content from multiple repos into a single unified docs site.
Security, deployment, and partnership that scale with your API.
SSO, visitor auth, and RBAC. Connect any SAML or OIDC provider and control access across docs and admin features.
Aggregate content from multiple repos into one site, with product and version switching that scales across teams without breaking IA.
Run on our managed cloud, or self-host to meet stricter security, networking, and compliance requirements.
First-class translated content. Ship docs in multiple languages as part of the rollout, not as a bolt-on.
SOC 2 Type II and annual pentests. Reports and supporting security documentation available for procurement.
Uptime SLA, escalation paths, and a dedicated Slack or Teams channel, with 24/7 coverage for critical incidents.
