1. Per-page export (fastest)
Every page in these docs has a contextual menu in the top-right. Click it and you can:Copy page as markdown
Copies the current page’s markdown source to your clipboard. Paste into any LLM.
View as markdown
Opens the raw
.md source in a new tab. Also available at <page-url>.md (e.g. /api-reference/inventory.md).Open in ChatGPT / Claude / Perplexity
One click, opens the chat tool of your choice with the page’s content pre-loaded.
Open in Cursor / VS Code
Opens your IDE with the MCP server pre-configured so the AI can query the docs live.
2. Full docs as a single file
Want to hand the entire Phygitals Partner API reference to your LLM, your PM, or a new hire? There are two prebuilt artifacts served directly by this site:llms-full.txt
The full docs in one markdown file. Every page, concatenated and structured for LLM ingestion. Paste directly into Claude, ChatGPT, Gemini, or any context window.
llms.txt
Index of every page with URLs and descriptions. Point an agent at this if you want it to crawl selectively instead of dumping everything.
Quick fetch
3. Live MCP server (most powerful)
For Claude Code, Cursor, VS Code, and other MCP-aware clients, we host an MCP server that lets the AI query these docs on demand. The AI can search, read pages, and pull up endpoint details during a conversation without you pasting anything.- Claude Code
- Cursor
- VS Code
- Other clients
Run once:Then in any Claude Code session, the model can search these docs and read any page directly.
What the MCP server exposes
Semantic search across every page in these docs. The AI calls this when it needs to find relevant sections for a user’s question.
Shell-style commands (
rg, cat, head, tree) over the docs as a read-only virtual filesystem. The AI uses this to read full pages or scan for exact keyword matches.Which should you use?
Quick question
Per-page export. One click, one page, done.
Onboarding a new dev
llms-full.txt. Ship them one file with everything.Building with AI
MCP server. Docs stay live and queryable throughout the build.