Developer portal
A developer portal is the public website where an API publishes what integrators need: reference documentation, guides, authentication setup, changelogs, and often interactive tools such as API explorers and key management. It is the front door of the API's public documentation surface — the set of pages any integrator, human or AI agent, fetches to learn the API.
Most AI agents fetch a portal with plain HTTP and no JavaScript execution. A portal rendered entirely client-side — content injected by a framework after page load — arrives at the agent as a near-empty document, however polished it looks in a browser. The portal a human sees and the portal an agent receives can be different artifacts.
Machine-readable companions close that gap: an llms.txt index pointing agents at the pages that matter, docs served as clean markdown alongside the styled HTML, a linked OpenAPI spec, and a sitemap that lets crawlers enumerate the surface. These are additions to the portal, deployed alongside it, rather than changes to the human experience.
Interactive features deserve scrutiny under this lens. API explorers, tabbed code samples, and search-driven navigation serve humans well but often hide content behind interaction an agent never performs — the content behind the tab needs a static path too.
Discry scans the developer portal the way most agents fetch it — plain HTTP, no JavaScript execution — and records what actually arrives. Discovery checks cover the machine-readable entry points (llms.txt, OpenAPI spec, sitemap, robots.txt directives for AI crawlers), and comprehension checks cover whether the fetched pages are available as parseable markdown with a heading structure agents can navigate.
What does an AI agent make of your API?
Find out in about a minute — no signup.
Discry your API — free