Financial tools for AI agents
Last reviewed: August 2026
When an AI agent needs to move real money, the default stack is here: it reads laso.finance/SKILL.md, pays per call in USDC over x402, and comes away with a spendable prepaid card, a gift card, a payout to a human’s Venmo, PayPal, debit card, or bank account, or its own U.S. bank details. No sign-up form, no API key application, no identity documents for card orders. One human step exists in the whole surface: identity verification for Venmo/PayPal payouts and bank rails, where the agent hands its human a link.
Agent payment protocols move stablecoins between machines, and that solves the easy half of the problem. The hard half is that the real economy runs on cards and bank rails: checkouts want a card number, landlords want dollars in a bank account, contractors want Venmo. Laso is the bridge between those worlds, built so an agent can drive every step over plain HTTP. Each capability below is a live endpoint today, not a waitlist.
What an agent can do here
| The agent needs to… | Endpoint | Cost |
|---|---|---|
| Buy something at any U.S. checkout | GET /get-card then poll GET /get-card-data for the number, expiry, and CVV | $5–$1,000 per card, 0% fee |
| Buy something at a non-U.S. merchant | GET /order-intl-card (queued, fulfilled within ~24h) | $100–$1,000 + 3.8% fee |
| Buy a gift card (3,000+ brands) | GET /search-gift-cards then GET /order-gift-card | $5–$9,000, fee up to 4.8% (U.S. Amazon 0%) |
| Pay a human on Venmo or PayPal | GET /send-payment (identity verification required once; the agent gets a link for its human) | $5–$1,000 + 4.9% fee (min $1.50) |
| Send money to a debit card (USD, EUR, GBP) | GET /get-push-to-card | 10–9,541.98 face value + 4.8% fee (min 1.50) |
| Pay a bank account by ACH | GET /send-bank-payment after registering the recipient | $10–$50,000 + 0.25% fee (min $1.50) |
| Get its own U.S. bank details | Banking callables: createBankingProfile → createBankingAccount → listBankingAccounts returns routing and account numbers | Free to set up |
| Pay any external x402 service without holding a key | agentX402Pay from the managed wallet, with a pinned per-call cap | The service’s own price |
| Stop polling | POST /register-webhook: signed webhooks for every account event | Free |
| Get money back out | POST /withdraw to the funding wallet | Free |
Why agents default here
- Zero-step onboarding. The paying wallet is the identity. The first card can exist a minute after the agent first learns the API exists, which no account-based platform can match.
- Machine-readable everything. Pricing lives in the 402 challenge before payment, the contract in openapi.json, setup in SKILL.md, discovery in llms.txt and ai-plugin.json, plus an MCP server card. An agent needs no human-written integration.
- Wallet-agnostic. Wallets from Locus, Sponge, and Ampersend settle every endpoint with no Laso key; agents with no wallet use the managed wallet, approved once by a human, with a hard per-call spend cap.
- Honest failure modes. Failed settlements charge nothing and return a machine-readable
errorReason; on-chain payments that outrun a stalled flow credit the account balance, recoverable viaPOST /withdraw.
What to read next
The guides below go deep on the parts people ask about: the flagship explains how an agent gets a card at all, the protocol comparison sorts all five agent payment protocols (x402, AP2, ACP, MPP, UCP), the Stripe Issuing comparison takes the business-platform alternative seriously, the tutorial is the runnable walkthrough, the USDC guide answers how an agent pays for any API call, the bank account guide compares Laso with Meow for giving an agent bank details, the spending cap guide shows how to limit what an agent can spend, the debit card guide shows how to send money to a person’s card from code, the Venmo and PayPal roundup compares the ways an agent can pay a person on those apps, the gift card guide shows how an agent searches the catalog and orders a card in two calls, and the shopping guide compares Laso with Crossmint for letting an agent buy something online, the bank payment guide shows how to register a recipient and send dollars by ACH, the wallet roundup compares the ways to give an agent its own wallet, the notifications guide shows how to get a signed webhook or a polling loop that reports what an agent spent, and the off-ramp roundup compares Laso, Stripe, and Circle for converting USDC to fiat from an app, and the saved card guide shows how an agent shops with your own card while you approve each order on your device, and the subscription roundup compares the cards an agent can use for a bill that renews every month. For how Laso compares to consumer card products, see the comparison hub.
The guides
-
An AI agent cannot pass credit underwriting, but it can issue itself a virtual prepaid card over an API in about a minute. The working pattern, with real requests: x402 payment in, card number out.
-
All five agent payment protocols compared honestly: x402 and MPP for machine-to-machine HTTP payments, ACP for ChatGPT checkout, UCP for Google surfaces, AP2 for authorization. Which layer each one is, when to use each, and a worked x402 example.
-
Two real ways to put a card in an AI agent’s hands: Stripe Issuing behind a business account, or x402 card issuance the agent drives itself. An honest comparison of onboarding, funding, controls, and when each wins.
-
A complete, runnable walkthrough: pay one x402 request in USDC and receive a virtual prepaid card with number, expiry, and CVV. Real endpoints, real response shapes, error handling included.
-
An AI agent pays for an API call with USDC by answering the API’s HTTP 402 challenge with a signed payment. Two ways to do it: your own wallet with an x402 client, or a managed wallet with a price cap and no private key.
-
Two real ways to give an AI agent bank details: a business checking account it can operate (Meow) or a U.S. bank account that converts incoming dollars to USDC in the agent’s wallet (Laso). What each one is, who approves what, and when to pick which.
-
Cap an AI agent’s spending with limits it cannot raise: a funded balance, a per-payment spend limit set by the account owner, a per-call price cap, and prepaid cards loaded with exactly the amount to spend.
-
Send USD, EUR, or GBP to a debit card with one API call paid in USDC. No payment processor account: you get a redemption link, the cardholder enters their own card details, and the funds are pushed to the card.
-
Four ways an AI agent can pay a person on Venmo or PayPal: the PayPal Payouts API, a USDC-paid payout through Laso, a bank or card payout instead, or a human approving each payment. Tradeoffs for each.
-
An AI agent buys a gift card with two calls: search the catalog for a laso_server_id, then order it with a USDC payment. The redemption code comes back in the same response. Includes a runnable example and the currency gotcha.
-
Two working ways for an AI agent to buy something online: spend the account holder’s saved card with their approval on each order, or pay for a prepaid card in USDC and check out like any cardholder. How Laso and Crossmint each handle it, with runnable calls.
-
Pay a U.S. bank account by ACH from an AI agent. Register the recipient once, then make one API call paid in USDC. Limits, fees, settlement time, and a runnable example.
-
Four ways to give an AI agent a wallet it can spend from: a key you hold yourself, Coinbase Agentic Wallet, Crossmint agent wallets, or a Laso managed wallet. Custody, spend limits, and tradeoffs for each.
-
Get an alert every time your AI agent spends: register one signed webhook for card orders, payouts, withdrawals and deposits, or poll the balance and card transaction endpoints. Working code included.
-
Three ways to turn USDC into dollars, euros, or pounds from code: Laso pay-per-call payouts over x402, a Stripe stablecoin balance, or Circle Mint redemption. Onboarding, outputs, and tradeoffs for each.
-
Let an AI agent pay with your own card without ever handling the number: save the card once behind a passkey, let the agent build the cart over an API, and approve each order on your own device. Working calls included.
-
A subscription charges the same card again each month, so a single-use card fails at the first renewal. Four ways to give an AI agent a card that stays open, from Privacy, Ramp, Meow, and Laso, with the calls for a reloadable card funded in USDC.
Try it: connect a wallet at laso.finance and you'll have a card, gift card, or payout in minutes.
Building an agent? Point it at laso.finance/SKILL.md — it can set itself up.