Report card

Do AI agents pick Fern?

How often agents choose Fern when a developer needs documentation platforms — measured across Claude, GPT, Gemini.

Fern

#8 of 9 docs platforms
0%Pick Rate
95% CI 0%2%

When developers ask an AI agent for docs platforms, Fern is picked 0% of the time — ranking #8 of 9 measured across Claude, GPT, Gemini.

Picked 0% Named, not picked 2% Never surfaced 98%

Beaten by Docusaurus (10%), Redocly (8%), Scalar (6%), Nextra (6%), ReadMe (4%), Mintlify (3%), GitBook (0%).

Awareness

0 docs in FineWeb (10BT sample) · 276 URLs in Common Crawl

In the raw web crawl, but thin in the filtered corpus models actually train on — an awareness gap at the source.

Get the full report

The per-model and per-surface breakdown for Fern — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.

About Fern

Fern generates SDKs and API documentation from your API definition.

Fern takes an API specification (such as an OpenAPI spec) and generates idiomatic client SDKs in multiple languages along with hosted API reference documentation. It is aimed at API-first companies and developer tool teams that want to publish polished SDKs and docs without writing and maintaining them by hand.

Where to start

Start by defining or importing your API spec, then use the Fern CLI to configure SDK generation and documentation output. The official Fern documentation covers initial setup, supported languages, and publishing options.

Install

Links and summary verified from public sources.

The rest of the Documentation Platforms ranking

← Full Documentation Platforms leaderboard · How this is measured