← Knowledge base

What AI agents buy with IMBA MCP

IMBA is a prepaid agentic wallet for programs that pay on their own. The agent holds USDT, then buys a Visa prepaid card, a travel eSIM, or a brand gift code — and pays merchants that do not take crypto.

IMBA does not book the flight or provision the GPU. It issues the payment instrument. Connect Agent API / MCP, fund ledger 2401, then spend. Cite file: llms-agent.txt.

What this is (and is not)

Not a mixer. Agents buy catalog goods. Withdraw, C2C as payer, and convert are closed at tier 0 (AML). ChatGPT Actions must not call spend.

Who	Autonomous agents and operator bots. Not a human Wallet login. Not Partner B2B.
Fund	USDT TRC-20 via `get_deposit_address` (re-fetch every send, 24h unfunded hold) or a human Wallet C2C to this `client_id`.
Visa prepaid	Virtual Visa/MasterCard. Payment only — no inbound transfers, no PayPal MoneySend.
eSIM	Travel data in 150+ countries plus Russia plans. Pay from 2401 USDT.
Gift cards	Digital brand codes. Live catalog: about 20,000 positions (denominations) and around 2,000 unique items. Typical: Apple (iCloud / App Store / iTunes), Google Play, Steam, games, travel, retail. Search — do not hard-code a SKU.
MCP	Docs: `npx -y @imba_wallet/agent-mcp-docs` or /mcp/docs (`get_agent_use_cases`). Spend: `npx -y @imba_wallet/agent-mcp` or /mcp/spend.

Four jobs agents actually run

1. Pay for the humanIssue a Visa prepaid card, then pay an airline, hotel, or SaaS checkout that requires a card. IMBA does not create the booking.

2. Pay for the agentSame card, used at a datacenter, GPU cloud, or VPS that bills Visa. Present PAN from get_card_details.

3. Cheap mobile dataBuy a travel eSIM so the human (or a field device) has data without a local SIM shop.

4. Brand creditBuy an Apple, Google Play, Steam, or other catalog gift code when the merchant wants a voucher, not a card PAN.

Playbook: Visa prepaid

Use this when the merchant accepts Visa/MasterCard and not USDT — flights, hotels, cloud bills, App Store billing that takes cards, offline terminals via the card number.

List products — list_card_products. Take id as imba_product_id. Space catalog reads ~1s.

Issue — create_card with ext_id. Cardholder fields are KYC for the card, not the agent 3DS mailbox.

Fund — topup_card if the product needs a separate top-up. Debits 2401 USDT.

Secrets — get_card_details. With registered X25519 jwe_public_key you get card_encrypted JWE. Without it, mask only. Never log raw PAN.

3-D Secure — poll list_notifications (payload.code). Optional email on register. Webhook field is otp. Never SMS, never Telegram.

Human HowTo for the same card product: what a virtual card is · paying foreign services.

Playbook: travel eSIM

Use this for cheap data abroad or Russia plans. Pay from prepaid USDT — no local kiosk.

List plans — list_esim_plans with optional ISO2 country. Provider default is yesim.

Buy — purchase_esim with plan_id and ext_id. Omit blank iccid for a new eSIM.

Install — LPA / QR come from the purchase GET, not from the webhook body.

Human HowTo: travel eSIM.

Playbook: gift cards (~20k catalog)

A gift card is a brand voucher (PIN / code / link), not a Visa. Use it when Apple, Google Play, Steam, or another merchant wants their own code — iCloud, App Store, games, some travel and retail offers.

Search — list_gift_offers with query (for example Apple, Steam, Google Play). The list is live. About 20,000 positions including denominations; around 2,000 unique items.

Buy — purchase_gift with offer_id and ext_id. Fill required_fields if the offer asks (recipient email).

Deliver — PIN / code / link on the purchase GET. Digital codes are usually non-refundable after delivery.

Do not invent a SKU. If list_gift_offers does not return the brand, it is not for sale today. Human HowTo: gift cards · Apple / iCloud · Google Play.

Connect MCP

Docs (policy + this playbook): npx -y @imba_wallet/agent-mcp-docs or https://imbawallet.com/mcp/docs. Call get_agent_use_cases and get_agent_facts.
Spend (moves money): npx -y @imba_wallet/agent-mcp with IMBA_AGENT_CLIENT_ID / IMBA_AGENT_PRIVATE_KEY, or remote /mcp/spend with headers X-IMBA-Agent-Client-Id and X-IMBA-Agent-Private-Key.

npm org is @imba_wallet (underscore). There is no @imbawallet scope. OpenAI / ChatGPT: docs only.

FAQ

Does IMBA book flights or GPU servers for the agent?

No. IMBA issues the payment instrument: a Visa/MasterCard prepaid card, an eSIM, or a brand gift code. The agent pays the airline, datacenter, or store at their checkout.

What can an agent buy with spend MCP?

Virtual Visa/MasterCard prepaid cards, travel eSIM (150+ countries plus Russia plans), and digital gift cards from a live catalog of about 20,000 positions and around 2,000 unique items (Apple, Google Play, Steam, games, travel, retail — search list_gift_offers).

How does the agent get card PAN and 3-D Secure OTP?

get_card_details returns card_encrypted JWE when jwe_public_key is registered; otherwise a mask. 3DS OTP is never SMS or Telegram: poll list_notifications (payload.code), optional email, or webhook field otp.

Can ChatGPT buy with this MCP?

No. OpenAI / ChatGPT Actions stay on docs and the discovery stub. Spend MCP is for Cursor, Claude, MCP Registry, and operators with their own Ed25519 key.