The Relayer documentation ships with first-class AI integration. You don’t need to copy/paste pages into a chat anymore — your AI assistant can query the docs directly as a tool.Documentation Index
Fetch the complete documentation index at: https://docs.relayer.fi/llms.txt
Use this file to discover all available pages before exploring further.
Built into Mintlify: an MCP server, contextual menus, and
llms.txt — all already live for this site.Why connect via MCP
The Model Context Protocol lets AI clients (Claude Code, Cursor, ChatGPT, Windsurf, Devin, VS Code) search and read this documentation as a tool call during a conversation. Concretely:- Your AI assistant has up-to-date answers about every endpoint, every parameter, every flow — not outdated training data
- The assistant decides when to consult the docs; you don’t have to attach pages manually
- Auth, search, and full-page retrieval all work out of the box
The MCP server URL
- search — finds relevant snippets across all docs, returns titles + links
- query docs filesystem — retrieves full page content with shell-style commands
Connect to Claude Code
Run this in your terminal:Connect to Cursor
Add this to your~/.cursor/mcp.json (or the project’s .cursor/mcp.json for per-repo scope):
Connect to VS Code
VS Code’s MCP integration is configured via the samemcp.json format inside your workspace:
Connect to ChatGPT / Claude / Perplexity / Grok
These web-based assistants don’t use MCP directly. Instead, the documentation gives them context per page through the contextual menu:Click the contextual button (top right)
You’ll see options for Copy as Markdown, View as Markdown, and direct deeplinks to ChatGPT / Claude / Perplexity / Grok / Google AI Studio.
Use llms.txt
Every Mintlify-hosted docs site exposes a curated index of LLM-friendly Markdown at:
<page-url>.md:
What the assistant can answer well
Once connected, your AI tool can answer questions like:- “How do I create an agent with a $500 monthly USDC budget?” — it queries
/agent/flow-guideandPOST /v1/agents/{id}/budget - “What headers does the agent SDK send?” — it pulls
get-started/authentication - “Generate a Node.js snippet to prepare and confirm a Solana transaction” — it combines the signing flow guide with the endpoint params
- “Which endpoints in Payout are public vs dashboard-only?” — it consults the API Reference tags and the architecture page
What it can’t answer (yet)
The MCP server returns what’s in the docs. It doesn’t have access to:- Your workspace’s specific API keys, agents, or wallet IDs (use the dashboard for those)
- Live data from your account (balances, orders, etc.) — for that, the assistant would need to call the API itself with your credentials
- Information not published in this site (internal roadmap, pricing for enterprise tiers, etc.)
Get help
- MCP issues: try
claude mcp remove relayer-docsand re-add. If problems persist, open a support email. - AI assistants giving wrong answers: this likely means the docs themselves are unclear or stale — please report at dev@relayer.fi and we’ll fix the page.
Next Steps
Quickstart
Make your first API call in under 5 minutes.
API Reference
Browse the full endpoint surface with an interactive playground.