For the complete documentation index, see llms.txt. Append
.mdto any page URL for its markdown version.
This documentation is built to be read by agents as well as by people. Everything below is read-only, and needs no credentials. It provides the information for your agent to help you build your integration faster.
An agent working from a web search may hallucinate and invent endpoints. Pointing it at these documentations means it reads the actual parameter names, the actual error codes, and the actual auth scheme.
These docs run a Model Context Protocol server. An agent connected to it searches and reads the documentation directly rather than scraping rendered HTML.
https://docs.banxa.com/mcpIt exposes six read-only tools:
| Tool | What it returns |
|---|---|
search | Passages matching a query, across all three products |
list-apis | The documented APIs and what each is for |
get-endpoints | Every endpoint of one API, with method and path |
get-endpoint-info | One endpoint in full (parameters, schemas, security, examples) |
get-security-schemes | How to authenticate against one API |
get-full-api-description | The complete OpenAPI description |
The transport is streamable HTTP. Clients must send Accept: application/json, text/event-stream; a request advertising only application/json is rejected with 406 Not Acceptable.
claude mcp add --transport http banxa-docs https://docs.banxa.com/mcpOnce connected, ask the agent questions:
- which Banxa product should I use if I already run my own KYC,
- what does
POST /eapi/v0/rampsaccept, - what does error
40003mean
A machine-readable description of the server, including the tool list, is available at https://docs.banxa.com/.well-known/mcp/server-card.json.
Two skills are published for coding agents. Each is a self-contained instruction document an agent can fetch and follow, rather than a page it has to interpret.
| Skill | Use it when |
|---|---|
choose-banxa-integration | Deciding between Native API, Hosted Checkout, or other future integration patterns |
banxa-api-authentication | Signing requests, and debugging 401s or nonce collisions |
The index is at /.well-known/agent-skills/index.json, with a SHA-256 digest per skill so a client can verify it fetched the document the index describes.
Append .md to any documentation URL to get the markdown source instead of rendered HTML.
curl https://docs.banxa.com/products/native-api/docs/getting-started/authentication.mdBanxa provides llms.txt for LLMs to consume our documentation on their own.
A condensed version of the documentation is available at /llms.txt.
The full corpus is available at /llms-full.txt.
https://docs.banxa.com/.well-known/ai-catalog.json) is an RFC 9727 catalog listing every Banxa API with its reference documentation and status endpoint, so a client can enumerate what exists before fetching anything.
While it is still stabilising in Chrome, please treat this feature as experimental
Pages on this site register WebMCP tools, so a browser-resident agent can search these docs and look up endpoints without leaving the page.
/robots.txt names the AI crawlers explicitly and declares how Banxa prefers this documentation to be used. Answer-engine crawlers are welcome. A sitemap lists every canonical page.