Skip to main content
Two Model Context Protocol servers sit in front of the HTTP Agent API. Docs MCP includes get_agent_use_cases — Visa prepaid, travel eSIM, ~20k gift cards, and paid KYT, with the spend-tool names for each job. Docs MCP is Streamable HTTP, not an HTML article. A browser GET with Accept: text/html redirects to HowTo. MCP clients stay on the protocol.

​
Spend credentials

Spend identity is client_id + Ed25519 private key (stdio env or headers X-IMBA-Agent-Client-Id / X-IMBA-Agent-Private-Key). HTTP headers cannot contain raw PEM newlines: send one line with the two-character sequence \n, or PKCS#8 / 32-byte seed as base64url. A Wallet JWT or a stolen access token is not a spend credential. The public host does not hold a shared wallet. Spend MCP never calls convert, withdraw, or C2C (the agent is not a payer). A human may still C2C to this client_id in Wallet. HTTP convert at tier 1 remains a separate request, not an MCP tool.

​
OpenAI / ChatGPT

Docs listing and the discovery stub only. Do not wire ChatGPT Actions to openapi/agent.json or to spend. Money/crypto plugins are forbidden in that store. npm: @imba_wallet/agent-mcp-docs (docs), @imba_wallet/agent-mcp (spend). Org is @imba_wallet (underscore). There is no @imbawallet scope.