llms.txt and markdown routes
Read FounderHQ documentation in agent-friendly formats.
Every page on this site has a Markdown twin. Nothing to install, nothing to configure.
Read one page as Markdown
Add .md to any docs URL.
https://www.getfounderhq.com/docs/analytics/protocol-reference/envelope.mdYou get the page as plain Markdown, with the title and canonical URL on the first line. Paste it into any chat.
Every page also has a copy button and a "view as Markdown" menu at the
top, and an agent link at the bottom. You never need to type the .md
by hand.
Ask for Markdown with a header
If your client cannot change the URL, ask for Markdown in the
Accept header instead.
curl -H "Accept: text/markdown" \
https://www.getfounderhq.com/docs/analytics/protocol-reference/envelopeThe same URL returns HTML in a browser and Markdown to your agent. The
response carries Vary: Accept, so caches keep the two apart.
text/plain and text/x-markdown work too. FounderHQ serves Markdown
when you rank it at or above text/html.
Give an agent the whole site
Two files cover the site.
| File | What it holds | Use it when |
|---|---|---|
/docs/llms.txt | A map: every page title, description, and absolute URL | The agent should pick what to read. Small enough to paste into a system prompt. |
/docs/llms-full.txt | Every page, in full | The agent has a large context window and you want one paste. |
curl https://www.getfounderhq.com/docs/llms.txtThe API reference is not in llms-full.txt
/docs/llms-full.txt leaves out the generated API reference pages, because
the endpoint schemas would crowd out the guides. Read those pages
individually with .md, or let the
MCP server fetch them on demand.
Which one to reach for
- Working in an editor with an agent: use the MCP server. It searches, so the agent reads only what it needs.
- Pasting into a chat window: use
.mdon the page you care about. - Scripting or building your own tool: use
/docs/llms.txtto discover pages, then fetch each one with.md.