Axiom Wallet

Use this skill when the user wants to interact with their Axiom Wallet through MCP.

Axiom Wallet can be used to:

check available balance
review recent transactions
retrieve single-use payment details for a user-requested purchase
attach receipt details after a successful purchase

The Axiom MCP endpoint is:

https://mcp.useaxiom.ai/mcp

When to use this skill

Use Axiom Wallet when the user asks you to:

buy or pay for something with Axiom
check their Axiom balance or account info
inspect recent Axiom transactions
retrieve payment details for a specific checkout

Do not use this skill for unrelated browsing, account settings changes outside the available MCP tools, or speculative purchases the user has not clearly requested.

Authentication

Axiom uses OAuth 2.0 with PKCE. Your MCP client handles the OAuth flow automatically.

To connect, add Axiom as a remote MCP server:

{
  "mcpServers": {
    "axiom": {
      "url": "https://mcp.useaxiom.ai/mcp"
    }
  }
}

Or in Claude Desktop: Settings > Connectors > Add and enter https://mcp.useaxiom.ai/mcp.

When you first use an Axiom tool, your client will open a browser window to sign in. Log in with your Axiom account and approve the requested permissions. The connection completes automatically after approval.

If authentication fails or expires, your client will prompt you to sign in again.

Available tools

Use the MCP tools exposed by the server when available:

whoami — returns user profile (name, email, shipping address, phone)
get_balance — returns current balance and available funds
list_transactions — lists recent transactions (optional cardId filter, limit)
get_payment_details — issues a single-use virtual card for a purchase. Requires itemName, itemAmount (dollars), merchant (merchantName, merchantWebsite), and reasonForPurchase (userCommand, aiReasoning). May fail if blocked by spending rules or if approval is required.
create_receipt — attaches receipt details to a completed transaction

Purchase workflow

When the user asks you to buy something, use this order:

Confirm the purchase details.
- Use the exact item, merchant, quantity, and price the user asked for.
- Do not invent purchase-critical facts.
Complete all checkout steps that do not require payment.
- Fill in name, email, shipping address, and any other required fields first.
- Advance through the checkout until the final step where payment details are needed to proceed.
- The goal is to reach the final total (including shipping, tax, and fees) before requesting a card.
Check available funds.
- Call get_balance to confirm sufficient funds for the final total.
Request payment details.
- Call get_payment_details with:
  - itemName — name of the item being purchased
  - itemAmount — the final total in dollars
  - merchant — { merchantName, merchantWebsite }
  - reasonForPurchase — { userCommand: "the user's original request", aiReasoning: "why this purchase fulfills it" }
- Treat the returned card as single-use and intended for one authorization only.
- Do not request payment details until you have the complete total — the card is created at this point.
Complete checkout.
- Enter the returned card number, expiry, CVV, and billing address to finalize payment.
- Always use the billing address returned by get_payment_details — not the user's shipping address. These are different. Verify the billing fields match before submitting.
- Do not store or reuse card details outside the active checkout flow.
Record the receipt.
- After a successful purchase, call create_receipt with the transaction ID and accurate purchase facts.
- Do not include hidden chain-of-thought, internal reasoning, secrets, tokens, or unrelated context.
Items: For each item include:
- imageUrl — product image URL (see references/enrichment.md for how to find these reliably)
- url — link to the product page
- description — short variant info (size, color, etc.)
Order confirmation: Include orderConfirmationUrl with the merchant's order confirmation page URL and orderNumber with the confirmation number.

Audit trail: Provide categorized steps. Each step has a category, an action (short title), and optional detail (extra context).

Categories:
- request_initiated — what the user asked for, product identification
- purchase_in_progress — checkout steps (shipping, tax, etc.)
- approval_required — if user approval was needed via Axiom
- purchase_complete — payment and order confirmation
- receipt_created — final receipt attachment
Example steps for a typical purchase:
```
{ category: "request_initiated", action: "User requested item", detail: "I want this in size medium https://shop.example.com/product" }
{ category: "request_initiated", action: "Product identified", detail: "Heavyweight Tee - Jet Black at $25.00 (flash sale, regular $35)" }
{ category: "purchase_in_progress", action: "Size confirmed in stock" }
{ category: "purchase_in_progress", action: "Shipping address entered", detail: "123 Main St, McLean VA 22101" }
{ category: "purchase_in_progress", action: "Shipping method selected", detail: "Standard Shipping (2-4 Business Days) at $6.57" }
{ category: "purchase_in_progress", action: "Tax calculated", detail: "VA Tax $1.51" }
{ category: "purchase_in_progress", action: "Final total", detail: "$33.08" }
{ category: "purchase_complete", action: "Payment completed", detail: "Axiom virtual card" }
{ category: "purchase_complete", action: "Order confirmed", detail: "Order #7XC9R4NGX" }
{ category: "receipt_created", action: "Receipt attached" }
```

Safety and behavior rules

Always check balance before requesting payment details.
Never claim a purchase succeeded unless checkout actually completed.
If spending rules, approval requirements, or policy checks block the purchase, stop and tell the user what happened.
Never bypass approval flows.
Never expose OAuth tokens, session details, cookies, or browser state.
Never include internal reasoning in receipts or any external system.
Never fabricate merchant, amount, tax, shipping, or transaction details.

Troubleshooting

Auth expired or failed

Your MCP client will prompt you to re-authenticate. Sign in again when prompted.

Insufficient funds

Tell the user the balance is insufficient and stop.

Spending rules blocked the transaction

Tell the user Axiom's rules prevented the purchase and do not retry blindly.