Changelog

HTTP API access for AI agents

AI agents can now access authenticated documentation directly via HTTP API. This enables custom integrations and AI tools to retrieve protected content programmatically.

Agents obtain a JWT via the /api/fern-docs/get-jwt endpoint with a Fern API key, then use it to access protected documentation:

$
curl https://docs.example.com/platform/overview \
>
  -H 'Accept: text/plain' \
>
  -H 'x-fern-host: docs.example.com' \
>
  -H 'FERN_TOKEN: your-jwt-here'

Content is served as clean Markdown for token-efficient processing.

Learn more in the MCP server documentation.

Folder-based navigation

Auto-generate navigation from a folder of markdown files using the new folder configuration. Instead of manually listing each page in docs.yml, point to a folder. Fern discovers all .md and .mdx files and adds them to the navigation.

1
navigation:
2
  - section: Getting started
3
    contents:
4
      - page: Introduction
5
        path: ./pages/intro.mdx
6
      - folder: ./pages/guides
7
        title: Guides # Display name for folder section
8
        icon: fa-regular fa-book
9
        collapsed: true
10
        availability: beta # Optional badge to display in navigation

Subfolders become nested sections. Supported options: title, slug, icon, collapsed, hidden, skip-slug, availability.

Learn more about navigation configuration.