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 (2,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–$10,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, and the tutorial is the runnable walkthrough. 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.
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.