# Fern API catalog before agent scrape guesswork

> Expose a standards-based API catalog before expecting agents or API crawlers to reverse-engineer your docs from HTML and navigation chrome.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/fern-api-catalog-before-agent-scrape-guesswork/
- Source: [buildwithfern.com](https://buildwithfern.com/learn/docs/ai-features/api-catalog)
- GrowthDex source hub: [Fern Docs: API catalog discovery](/sources/fern-docs-api-catalog-discovery-buildwithfern-com/)
- Last checked: 2026-06-08T10:06:43.000Z
- Rarity: rare
- Budget: low
- Channels: API docs, AI visibility, Developer Tools
- Stages: api discovery, agent retrieval, machine-readable docs, developer seo, api catalog


## Why this can grow

A docs site can look clear to a person while still being awkward for machines to parse. Fern's API catalog feature fixes that by publishing a machine-readable map of visible APIs with both the human reference URL and the underlying spec link. That matters because the discovery job shifts from scraping to retrieval. Instead of hoping an agent stumbles into the right endpoint page, you give it a clean front door.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where fern api catalog before agent scrape guesswork can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the API docs and AI visibility channel.
3. Use the evidence from buildwithfern.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Fern documents an RFC 9727 `/.well-known/api-catalog` endpoint that is generated from visible API Reference navigation and advertised via a `Link` response header.

## Adjacent tactics in the same lane

- [Fern search scope by product before cross-doc noise](/growth-ideas/fern-search-scope-by-product-before-cross-doc-noise/) - 2 shared channels
- [Fern API key injection before auth copy-paste](/growth-ideas/fern-api-key-injection-before-auth-copy-paste/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The docs path should stay readable to bots and buyers](/blog/the-docs-path-should-stay-readable-to-bots-and-buyers/) - documentation, API docs, AI visibility

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.