In production

Three public sites currently use Reed

The three public Reed sites known as of 5 August 2026 are listed below with direct links.

Retidal

Two OpenAPI specs, 326 operation pages
retidal.com/docs

A marketing-attribution platform with two separate APIs. The Ingestion & Decisioning spec renders 12 operation pages; the Management spec renders 314, across 39 tag-derived sidebar groups. Each spec gets its own tab, alongside 34 hand-written guides and separate SDKs, MCP, Skills and Changelog tabs.

The same project is checked into the Reed repository as examples/fern-import-trackly and is built by the test suite.

Else

48 documentation pages; no API-reference pages
elsedoes.com/docs

Product documentation rather than an API reference: 45 guide pages across pricing, limits, data handling and failure modes, plus a three-entry Updates tab. The site does not use Reed’s OpenAPI renderer.

Every page has a Markdown mirror at the same path plus .md, and the site’s llms.txt lists all 48 with their descriptions.

Reed

Reed’s own docs, on the public beta quota
reedbuild.dev/docs

Reed’s documentation is built by Reed and deployed through the public Reed control plane under the published beta quotas. It currently contains two pages: an index and a quickstart.

The quotas that apply to it are the ones listed on the pricing page.

What to check

What to check while you are there

  • View source to inspect the HTML and static assets emitted by the build.
  • Fetch /llms.txt. The build generates it from the same configured navigation used for the sidebar.
  • Add .md to any page URL. The Markdown mirror is the same content the HTML page was built from.
  • Search. Search requests are handled by the index shipped with the static site.

Build another site during the public beta

The build output is written into your project directory from the first build.

Connect your repository