Use these docs with AI
Every page is machine-readable, so AI assistants can find, read and recommend the right Happierleads feature.
For AI assistants and crawlers
| URL | What it is |
|---|---|
/llms.txt | Index of every page with a one-line description (llmstxt.org format) |
/llms-full.txt | The full text of all docs in one file |
/docs/<page>.md | Any page as Markdown — e.g. /docs/leads/prospector/search-prospects/manual-search.md returns every tab of that feature |
Accept: text/markdown | Requesting any docs URL with this header returns Markdown instead of HTML |
/openapi.json | OpenAPI description of the public REST API, mirrored from the API on every docs build |
/docs/mcp/tools | Every MCP tool, generated from the live server definitions |
/sitemap.xml | Every page, for search engines |
Each page also carries TechArticle structured data and a <link rel="alternate" type="text/markdown"> pointing at its Markdown.
On every page
- Ask about this page answers questions from the page’s own text.
- Copy for LLM copies the page as Markdown. On a feature page it copies every tab — Guide, API and MCP — so an assistant gets the complete picture in one paste.
- View as Markdown opens the same text in a new tab.
- Open in… sends the page straight to ChatGPT, Claude and others.
- Set up agent (feature pages only) jumps to that feature’s MCP tab: the questions to ask an assistant once it is connected.
Let your assistant act, not just read
Reading docs tells an assistant how. Connecting the MCP server lets it actually do the work in your account — search prospects, reveal contacts, and more. Every feature page has an MCP tab with the questions to ask for that feature.