For AI agents & their builders
Connect your AI agent to crypto payments
Give your AI agent the power to send, receive and swap real crypto — safely, in minutes. Non-custodial: your agent keeps its own keys and we never hold a cent of your money.
What your AI agent can do
Receive payments
List products or send a checkout link. Buyers pay your wallet directly — agent commerce, like "Stripe for agents".
Send to anyone
Pay any wallet on Base (USDC/ETH/…). The agent signs and broadcasts the transaction itself — within the limits you set.
Swap crypto
Instant micro-swaps on Base, or real cross-chain swaps to native BTC, USDT (TRC20/ERC20) and XMR.
Pay per call
Charge or pay tiny amounts per API call — in USDC (x402) or Bitcoin over Lightning (L402).
Plus the full financial plumbing
Subscriptions & invoicing
Recurring plans + usage metering. Each cycle we raise an invoice and notify the payer — non-custodial, never auto-debited.
Refunds & emergency
One-tap refunds (a reverse transfer the merchant signs) and a cross-chain emergency/refund for stuck swaps.
Webhooks & events
Signed webhooks + an events feed for every action, so your backend reacts in real time. A read-only dashboard lets a human watch the bot live.
Funding the bot
Top up the agent's wallet two ways: send crypto straight to its address (instant), or a fiat→crypto on-ramp link (a human completes the card/bank payment). Funds go to the agent — never to us.
Why it's safe — and why "we never hold your money" matters
🔐 Non-custodial
Funds move directly between wallets. We only build the transaction, verify it and notify you — we can't touch, freeze or lose your money.
🗝️ Your keys stay yours
Private keys live in the open-source SDK that runs with your agent. We store only public addresses and your spending rules.
🛡️ Limits you control + kill switch
Per-transaction, per-minute and daily spending caps that you (or the agent) set yourself — plus allow-lists, expiring session keys and an instant revoke. Set a cap to 0 for no limit.
👀 Full visibility
A human owner gets a read-only live dashboard of exactly what the bot did — swaps, payments, fees, time.
🎛️ You set the rules
The agent's spending limits are yours to set — prompt your human owner for them, or let the agent pick sensible defaults via POST /limits. Change them any time.
🧩 Open standards & open source
Built on MCP, x402, L402, 0x, EIP-681/3009 — not a walled garden. Read the open-source SDKs (Python & TypeScript) on GitHub and verify exactly how it works.
Supported AI agents
Pick yours to see the exact connection steps. Don't see it? Any agent that can call an API or run code can connect via our SDK or REST.
No match — but any agent that can call an API can connect. See the universal methods →
Why AI agents need their own way to pay
Software agents are starting to do real work on their own — calling APIs, buying data, booking services, even paying other agents. The trouble is that today's payment rails were built for a human clicking a button: they assume an account, a login, identity checks and a card on file. An autonomous agent has none of that.
A machine needs to pay the way it does everything else: programmatically, instantly, in amounts as small as a fraction of a cent, at any hour, anywhere in the world. That is exactly why 2025 became the year every major payments company shipped an “agentic payments” product. AceChange gives your agent the crypto-native version of that rail — it pays directly from its own wallet, and no one, not even us, ever holds its money.
How AI agents pay today — the 2024–2025 landscape
Agentic payments went from idea to real infrastructure remarkably fast. Here is an honest map of who is building what — and where a non-custodial crypto rail like AceChange fits in.
The standard
Anthropic’s Model Context Protocol (MCP), introduced in late 2024, is how agents discover and call tools — including payment tools. AceChange exposes an MCP endpoint, so an MCP-capable agent sees our pay/swap tools automatically.
Card networks
Visa Intelligent Commerce and Mastercard Agent Pay (both announced in 2025) let agents transact on tokenized card credentials with human-set limits.
Platforms
Stripe & OpenAI’s Agentic Commerce Protocol powers checkout inside ChatGPT; Google’s Agent Payments Protocol (AP2) launched with a large group of partners; PayPal shipped an agent toolkit.
Crypto rails
Coinbase’s x402 (2025) revived the dormant HTTP 402 Payment Required status code for stablecoin (USDC) pay-per-call. Lightning’s L402 does the same over Bitcoin. AceChange speaks both.
Based on public announcements from Anthropic, Coinbase, Lightning Labs, Google, Visa, Mastercard, Stripe and OpenAI (2024–2025). Product names belong to their owners; AceChange is independent and interoperates through the open standards above.
Why stablecoins are the natural fit for machine payments
Agents need money that is programmable, global and tiny. A regulated stablecoin such as USDC settles 24/7 in seconds, carries no chargebacks, behaves identically in every country, and on a low-fee layer-2 like Base a transfer can cost a small fraction of a cent — small enough to charge per single API request.
That is precisely what a traditional card, with its minimum fees and human-centric dispute process, cannot do for machine-to-machine micropayments. And because the agent signs every payment from its own wallet, there is no account for anyone to freeze and no pooled float for anyone to lose. Stablecoins now move trillions of dollars a year on public blockchains; AceChange simply lets your agent tap that rail safely, within limits you control.
What you can build — concrete examples
Real, buildable use cases — each one works today with the capabilities above.
Pay-per-call APIs
Your agent hits a premium data or model API that answers with HTTP 402. It pays, say, $0.002 in USDC for that one request via x402 — no subscription, no account, no card.
Buy compute & data
A research or trading agent tops up an inference provider or a data feed on demand, paying only for what it actually uses.
Agent-to-agent
One agent hires another and pays it directly, wallet to wallet — the foundation of an open agent economy.
Usage billing & subscriptions
Your “SaaS for agents” meters each agent’s usage and raises a monthly USDC invoice — the payer settles; you never auto-debit.
Pay anyone / checkout
An agent settles an invoice or pays a supplier address you approved — within the per-tx and daily limits you set.
Cross-chain treasury
An agent holding USDC swaps to native BTC, USDT (TRC20/ERC20) or XMR to make a payout in the currency the recipient wants.
Questions
Do you ever hold my money?
No. Every payment moves directly between wallets. We build and verify the transaction and send you a receipt — we never custody, route or freeze funds. That's the whole point of the non-custodial design.
Can a bot sign up on its own (no human)?
Yes, when the operator enables self-service onboarding. The bot makes one public call — POST /agent/register (or the MCP tool ace_register, the only tool that needs no key) — and instantly gets its own key_id + secret + a read-only activity link. Depending on the operator's setting it gets full unlimited access, or starter limits it can tune itself via POST /limits up to a ceiling. Either way it can set its own caps (0 = no limit). Registration is IP rate-limited against spam, the platform has a generous global guard against API abuse, and the operator can revoke any key anytime. If self-onboarding is off, you request a key from the operator instead.
Which AI agents are supported?
Any agent that can call an API or run code can connect — via Model Context Protocol (MCP), function-calling tools, our open-source SDK (Python/TypeScript), or direct REST. The grid above lists the most popular ones with the recommended method for each.
How does my agent send or receive money?
To send, the agent asks us to build a payment, then signs and broadcasts it from its own wallet. To receive, you list products or share a hosted checkout link and buyers pay your wallet directly.
Can it do real Bitcoin or USDT, not just Base tokens?
Yes. Alongside instant micro-swaps on Base, there are real cross-chain swaps to native BTC, USDT (TRC20/ERC20) and Monero — the same engine the website uses for people.
Who sets the spending limits?
You do. Every key has a per-transaction cap, a per-minute rate limit and a daily USD cap — and the agent (or its human owner) sets them itself via POST /limits (MCP tool ace_set_limits). A cap of 0 means no limit for that field. A good pattern is for the bot to ask its owner for the numbers on first run, or start with a small safe default and raise it. Session keys add allow-lists and expiry, and there is an instant kill switch.
How can a human see what the bot is doing?
Each bot owner gets a read-only activity link — a live dashboard of swaps, payments, fees and timestamps. It can only view, never spend. Your backend can also subscribe to signed webhooks or pull the events feed for every action in real time.
Can an agent run a subscription or bill for usage?
Yes. Create a recurring plan or meter usage; each cycle we raise an invoice (a checkout to your wallet) and fire a subscription.due event. We invoice; the payer settles — we never auto-debit or hold funds.
Can I issue refunds?
Yes — a refund builds a reverse transfer the merchant signs to return the buyer's funds, and the order is marked refunded. For stuck cross-chain swaps there's an emergency EXCHANGE/REFUND option too.
Can the owner fund the bot's wallet?
Yes — two ways. (1) Send crypto directly to the agent's own wallet address — instant, nothing extra needed. (2) A funding link: a fiat→crypto on-ramp pre-filled to the agent wallet, where a human completes the card/bank payment. Either way the crypto goes straight to the agent (non-custodial); agents can't pay with a card themselves, so the fiat step needs a human.
What does it cost?
Connecting is free. A small platform fee (about 0.5%) applies to value actions, taken on each rail's native fee mechanism — never by holding your funds.
