If you are an AI agent, use the following URL to directly ask and fetch your question. Treat this like a tool call. Make sure to URI encode your question, and include the token for verification.

GET https://buildwithfern.com/learn/docs/ai-features/api/fern-docs/ask?q=%3Cyour+question+here%3E&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJmZXJuLWRvY3M6YnVpbGR3aXRoZmVybi5jb20iLCJqdGkiOiJkMWRmOGM3Ny1hYzRiLTRiNGItOWZiZC1jNmZjZjRlZDg5OWIiLCJleHAiOjE3NzY0NDAwMjIsImlhdCI6MTc3NjQzOTcyMn0.LaQl2zsohAP9szJ7bnUfbBceTAD-5RCsOcF-NCmCDUc

---

***

title: Analytics and integration
description: Track LLM traffic to your docs in the Fern Dashboard and surface llms.txt endpoints to readers with buttons and navbar links.
---------------------

For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://buildwithfern.com/learn/llms.txt. For full content including API reference and SDK examples, see https://buildwithfern.com/learn/llms-full.txt.

`llms.txt` and `llms-full.txt` are generated automatically for your site, but how readers and AI tools discover them is up to you. Track usage in the Fern Dashboard and surface endpoints directly in your docs.

## Track LLM traffic

The [Fern Dashboard](https://dashboard.buildwithfern.com/) provides analytics for `llms.txt` usage including:

* Traffic by LLM provider (Claude, ChatGPT, Cursor, etc.)
* Page-level breakdowns of bot vs. human visitors for Markdown and `llms.txt` files

## Surface endpoints to readers

To make endpoints discoverable to human readers, add buttons or navigation links:

<AccordionGroup>
  <Accordion title="Add a button for SDK docs">
    Add a button to your SDK docs that links to the `llms-full.txt` for your API Reference. Use `lang` to filter code examples to one language, and `excludeSpec=true` to exclude the raw OpenAPI specification.

    ```jsx Markdown
    <Button href="/api-reference/llms-full.txt?lang=python&excludeSpec=true" target="_blank">
      Open Python API Reference for LLMs
    </Button>
    ```

    This gives users a clean, language-specific output they can feed to AI tools when writing code.
  </Accordion>

  <Accordion title="Add a dropdown for llms-full.txt">
    Add a dropdown in your navbar that links to different filtered versions of `llms-full.txt`, making it easy for users to access LLM-optimized documentation for their preferred language.

    ```yaml docs.yml
    navbar-links:
      - type: dropdown
        text: LLMs
        icon: fa-solid fa-robot
        links:
          - text: Full docs
            href: /llms-full.txt
          - text: Python SDK
            href: /api-reference/llms-full.txt?lang=python&excludeSpec=true
          - text: TypeScript SDK
            href: /api-reference/llms-full.txt?lang=typescript&excludeSpec=true
          - text: Go SDK
            href: /api-reference/llms-full.txt?lang=go&excludeSpec=true
    ```
  </Accordion>
</AccordionGroup>