For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Getting started
    • Overview
    • How it works
    • Quickstart
    • Project structure
    • Customer showcase
    • Changelog
  • Configuration
    • Overview
    • Site-level settings
    • Page-level settings
  • Writing content
    • Markdown basics
    • Rich media in Markdown
    • Fern Editor
    • Reusable snippets
  • AI features
    • Overview
    • Fern Writer
    • AI-generated examples
    • Markdown access
      • Overview
      • Customize LLM output
      • Agent directives
      • Analytics and integration
    • MCP server
    • API catalog discovery
      • Overview
        • Customize API Reference layout
        • Audiences
        • Write Markdown in API Reference
  • Public API
    • GETJWT from Fern API key
    • GETAlgolia search credentials
    • GETCurrent user information
  • Fern Writer API
    • GETGet Fern Writer Install Link
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • Instance audiences
API ReferencesCustomization

Audiences

Use audiences to filter the endpoints, schemas, and properties that are displayed in your API Reference.
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Customize API Reference layout

Next

Write Markdown content in your API Reference

Team and Enterprise feature

This feature is available only for the Team and Enterprise plans. To get started, reach out to support@buildwithfern.com.

Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include public and beta. You can configure audiences in the OpenAPI Specification.

Once you’ve added audiences to your API Specification, you can filter to that audience by adding the audience property to the api object in your docs.yml navigation.

docs.yml
1navigation:
2 - api: API Reference
3 audiences:
4 - public

Here’s an example from Schematic in production.

Instance audiences

API Reference audiences work alongside instance audiences, which control which products and versions appear in each documentation instance. You can use both features together:

  • API Reference audiences - Control which endpoints and schemas appear within API References
  • Instance audiences - Control which products and versions appear in each instance

For example, you might have a public API Reference that shows only public endpoints. To ensure this API Reference only appears on your public documentation site, tag the containing product or version with the public audience.