Aixpa for AI agents

Every guide page has a Markdown copy at its own address plus .md, for example /integration.md, and /index.md for the home page. The page address itself answers in Markdown when the request asks for it:

curl -H 'Accept: text/markdown' https://aixpa.store/integration

That answer is never stored by a cache (Cache-Control: no-store, Vary: Accept); each .md file names its page in a canonical Link header.

Fees, revenue shares, minimums, payout limits, the module list and network totals: /v1/facts. Component health: /v1/status. Crypto prices: /v1/rates. All three are described in openapi.json, need no key and answer any origin.

Network totals count every project together and show only from a floor up, so no single site can be read out of them.

A remote MCP server, read-only and without a key, at https://api.aixpa.store/mcp (Streamable HTTP: one JSON answer per request, no session). In Claude Code:

claude mcp add --transport http aixpa https://api.aixpa.store/mcp

Other clients take the same address as a remote HTTP server. The tools:

• get_status — Live health of every hub component (API, database, payment gateways, payout rails, rates, each sign-in method). Same data as GET https://api.aixpa.store/v1/status.
• get_rates — Crypto/USD prices the hub serves to connected sites, refreshed every few minutes; stale: true marks an old price. Same data as GET https://api.aixpa.store/v1/rates.
• get_facts — The public numbers of the hub: payment fee, revenue shares, minimums, payout limits and methods, the module registry and network totals (shown only from a floor up). Same data as GET https://api.aixpa.store/v1/facts.
• list_payment_methods — Every coin and network a project can be paid in: its lane (invoice, permanent address or FaucetPay), the live minimum in USD and whether it can be paid right now.
• search_docs — Search the hub documentation (home, features, pricing, integration guide, agent guide) and get the matching passages with their page URLs.

Every tool only reads. Up to 60 requests a minute per IP address; above that the endpoint answers 429.

Without a client, one request is enough:

curl -s https://api.aixpa.store/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_facts","arguments":{"section":"payments"}}}'

The entry for MCP registries (server.json), kept with the source as ops/claude/mcp/server.json:

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "store.aixpa/hub",
  "title": "Aixpa hub (read-only)",
  "description": "Read-only Aixpa hub data: status, crypto rates, fees and limits, payment methods, docs search.",
  "version": "1.0.0",
  "websiteUrl": "https://aixpa.store/docs/agents",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://api.aixpa.store/mcp"
    }
  ]
}

• Read anything public: pages, Markdown, JSON and the MCP tools. The facts are rebuilt at most hourly, so polling every few minutes is plenty.
• Nothing here signs up, signs in or moves money. Automated sign-up, sign-in or use of the dashboard, checkout and admin screens breaks the Terms, as robots.txt says.
• Too many requests get a 429 answer: wait a minute, then try again.
• To act for a person (create a project, read its stats), that person creates a personal API token in the dashboard; a token can never withdraw. See the integration guide.

For an assistant that should answer questions about Aixpa:

Use the Aixpa hub as a read-only source. Start with https://aixpa.store/llms.txt.
For current fees and limits call https://api.aixpa.store/v1/facts (or the MCP tool
get_facts at https://api.aixpa.store/mcp). Quote numbers from those answers, not from
memory, and say when they were generated. Never sign up, sign in or submit forms.