Use this page when wiring Dollr documentation into ChatGPT, Claude, Cursor, VS Code, or your own RAG pipeline.
The Dollr payment API (https://api.heydollr.app) is separate from the documentation MCP (https://docs.heydollr.app/mcp). MCP only helps AI tools read these docs — it does not execute payments.
Quick links
| Resource | URL | Use case |
|---|
| llms.txt | docs.heydollr.app/llms.txt | Compact site index + flows for agent context |
| llms-full.txt | docs.heydollr.app/llms-full.txt | Every doc path with descriptions |
| OpenAPI | api.heydollr.app/openapi.json | Schemas, codegen, Postman import |
| Docs MCP | https://docs.heydollr.app/mcp | Read/search published docs from an MCP client |
Copy page Markdown
On any doc page, open the contextual menu (top of page) → Copy page. Paste into your AI chat for questions about that specific guide or API concept.
For whole-site context, prefer llms.txt or llms-full.txt over copying many pages manually.
Documentation MCP (read-only)
Mintlify hosts a documentation MCP endpoint for this site. It lets compatible clients search and retrieve Dollr doc content.
Endpoint: https://docs.heydollr.app/mcp
Use the MCP endpoint URL above in your client config.
Manual setup (Cursor)
Add to your user or project mcp.json:
{
"mcpServers": {
"dollr-docs": {
"url": "https://docs.heydollr.app/mcp"
}
}
}
Manual setup (Claude Desktop)
Add a custom connector or MCP server pointing at https://docs.heydollr.app/mcp per Anthropic’s current MCP documentation.
Manual setup (other clients)
Any MCP client that supports HTTP/SSE remote servers can use the same URL. Refer to your client’s docs for the exact config shape.
Do not put Dollr Client ID or Client Secret into MCP config. API secrets belong only in your backend when calling https://api.heydollr.app.
Mintlify Assistant (built-in)
The docs site includes Mintlify’s Assistant panel on the right (header sparkle icon, Ask AI anchor, or Assistant in the contextual menu). It answers from published Dollr documentation.
One-time setup (Mintlify Dashboard)
- Open Mintlify Dashboard → Assistant for the dollr_api_docs project.
- Enable the assistant.
- Add up to three starter questions (site-wide). Suggested copy — paste into the dashboard:
| # | Starter question |
|---|
| 1 | How do I collect a mobile money payment in Liberia with the Dollr API? |
| 2 | What is the difference between Dollr invoices and orders, and when should I use each? |
| 3 | How do I authenticate and avoid duplicate charges when a payment is PROCESSING? |
- Optional: set a deflection email (e.g.
dev@heydollr.app) when the assistant cannot answer.
- Optional: add search domains only if you want the assistant to pull public context outside the docs.
Custom behavior instructions for the assistant live in .mintlify/Assistant.md in the repo (synced on deploy).
On-site behavior (already in repo)
- Open on load:
?assistant=open plus assets/javascripts/assistant-default-open.js opens the panel by default; readers can close or expand it. Closing once keeps it closed for that browser session.
- Keyboard shortcut: ⌘I (macOS) / Ctrl+I (Windows).
- Contextual menu: includes Assistant, Copy page, View, Claude, and ChatGPT.
Ask about the current page
The contextual menu also includes Open in Claude and Open in ChatGPT — they start a conversation with the current page as context. Use those for one-off questions; use llms.txt + MCP for building integrations.
Agent guardrails (summary)
When implementing Dollr for production:
- Auth — OAuth client credentials;
expires_in is in minutes; refresh before expiry.
- Idempotency — Generate UUID v4
reference_id before POST /v1/executions/*; poll status before retrying.
- MoMo —
PROCESSING can last minutes; do not re-execute with a new reference_id during that window.
- Secrets — Server-side only; never in mobile apps or browser bundles.
- Support payload — Include
reference_id, HTTP status, redacted request/response, method, provider, market.
Full checklist: Support · Errors: Knowledge Base
