Mintlify

See which AI agents read your Mintlify docs

Documentation is where agent traffic concentrates. It's what an agent actually reads when deciding whether to recommend your tool over a competitor — and it's usually the part of your site you can't instrument.

Why you can't see them today

Mintlify's built-in analytics is client-side, so it counts humans reading your docs and nothing else. Every AI agent that pulls a page to answer a question about your product is invisible in it. For a developer tool, that's the traffic that decides whether you get recommended.

The reason there's no script tag to paste. AI agents don't execute JavaScript. Every analytics tool you already run is a browser tag, so it never fires for an agent — which is why your dashboards show none of this traffic. The only way to see it is server-side, at the edge, or in your logs.

See yours before you install anything

Paste a chunk of your access log and we'll pull out the AI agents that crawled you, what they read, and the files they asked for and couldn't find. No account, nothing stored.

Check my log free →

Install: Cloudflare Worker

No code required. Captures response status, so you also see the pages agents asked for and didn't get.

Put your docs domain behind Cloudflare. Add the domain to Cloudflare and set the CNAME for your docs subdomain to cname.mintlify.builders, proxied (orange cloud).
Fix the two Cloudflare settings Mintlify needs. SSL/TLS encryption mode must be Full (strict), and Edge Certificates → Always Use HTTPS must be off. Cloudflare's HTTPS redirect blocks Let's Encrypt from validating the domain, and certificate provisioning fails with no useful error.

Deploy the Worker and route it. Deploy the Pickrate Worker and point a route at your docs hostname.

git clone https://github.com/pickrate-io/cloudflare-worker
cd cloudflare-worker && npm install
npx wrangler secret put PICKRATE_KEY
npx wrangler deploy

Gotchas worth knowing first

Mintlify's pre-validation doesn't work through a Cloudflare proxy

The domain verification flow will not complete for proxied domains. Set the CNAME to cname.mintlify.builders and continue without waiting for the TXT records to show as verified — they won't.

Always Use HTTPS breaks certificate issuance

This is the one that costs people an afternoon. With it on, Let's Encrypt can't validate the domain, so the certificate never issues and the docs site stays broken. Turn it off in Edge Certificates.

Watch for 404s on your agent surfaces

Because the Worker sees responses, you'll find out if agents are asking for /llms.txt or /llms-full.txt on your docs domain and getting a 404. That's a fixable gap you'd otherwise never learn about, and it's common on docs subdomains.

Questions

Why does agent traffic to docs matter more than to my marketing site?

Because docs are what an agent reads to answer a question about your product. When someone asks Claude or ChatGPT to pick a library, the model's impression of your tool comes substantially from documentation it has read or retrieved. Your marketing homepage is not what gets read at decision time.

Does this work for GitBook, ReadMe, or Docusaurus?

Yes, and they're simpler — no platform-specific certificate settings. Point the custom domain at your docs host through Cloudflare, proxied, then route the Worker at it.

Do I have to change anything in Mintlify?

No. The Worker sits in front and forwards every request unchanged. Mintlify doesn't know it's there.

Other setups

Track AI agent traffic with a Cloudflare Worker — Goes in front of any origin. The only option when you don't control the codebase.
See which AI agents crawl your Vercel site — Zero code. Covers every framework on Vercel at once, and captures response status.
All install options — the full chooser, including pasting a log with no install at all.
Developer reference — every method in one place.

Agent-readable version: https://pickrate.io/install/mintlify.md