How do I give an AI agent a bank account?
Last reviewed: August 2026
A person or company still owns the account, and the agent operates it. If you want a business checking account your agent can run, with approvals and caps on every payment, use a provider built for that, such as Meow. If you want your agent to have U.S. bank details that pay it in USDC, plus a way to send dollars to other bank accounts, use Laso: the agent opens the account over HTTP and only the owner’s identity check goes to a human.
Two different things are called an agent bank account
The phrase covers two products. One is a real business checking account that an agent can be given access to. The other is a set of U.S. bank details that feeds a crypto wallet. They solve different problems, so the right first question is what the agent needs the account for.
- A checking account the agent operates. Dollars stay dollars. The agent can pay contractors, issue cards, and send invoices, usually behind human approval. Meow is the example compared here.
- Bank details that fund a wallet. Dollars arrive by ACH or wire and are converted to USDC for the agent to spend on-chain or through x402 endpoints. Laso is the example compared here.
Side by side
| Laso | Meow | |
|---|---|---|
| What the account is | A virtual U.S. bank account with ACH and wire details. Incoming dollars are converted and delivered as USDC to the agent’s managed wallet | A business checking account. Meow says banking services are provided by its partner banks, Members FDIC, and that Meow itself is a financial technology company, not a bank |
| Does the balance stay in dollars? | No. It lands as USDC, which is a stablecoin and not an FDIC-insured deposit | Yes, as a checking balance at its partner banks |
| How the agent starts | The agent reads SKILL.md, signs in, and calls createBankingProfile | You tell your assistant to read meow.com/skills.md, or connect through meow.com/mcp |
| What a human must do | The owner completes one identity verification through a link the agent hands over. The agent can answer the rest of the application and open the account | Meow says the agent can help complete verification and get the account approved. It does not spell out which steps a person must do themselves |
| Who owns the account | The person who verified. The agent never completes an identity check on their behalf | You, with the agent operating it |
| Spending controls | A per-payment spend limit the owner sets in the dashboard ($1 to $50,000, default $1,000) that the agent can read but not change, plus optional per-call guardrails on managed wallet payments | Per Meow, an agent can move zero dollars by default. Wires, ACH, and cards are off until you turn them on, payments come back for approval, and cards have per-transaction and daily caps |
| Paying others in dollars | GET /send-bank-payment over x402, $10 to $10,000 plus a 0.25% fee ($1.50 minimum), to a recipient you registered. Also payouts to Venmo, PayPal, and debit cards | Wires and ACH from the checking account, with free wires and ACH on partner-bank checking per Meow |
| Receiving dollars | Yes, into the on-ramp account, arriving as USDC | Yes, as a normal checking account |
| Cards for purchases | Prepaid cards ordered per purchase, $5 to $1,000 each | Virtual and physical cards with granular controls and API access, per Meow |
When Meow is the better fit
Pick a checking account if the agent’s job is running a business’s finances in dollars: paying invoices, issuing cards to team members, holding operating cash. A Laso account turns incoming dollars into USDC, so it is the wrong tool if the balance has to stay in a bank account, earn the protections of a bank deposit, or be reconciled like checking. Meow’s approval-first defaults, where nothing moves until a person turns a rail on, are also a good model if you want a person in the loop on everything.
When Laso is the better fit
Pick Laso if the agent already lives on-chain or pays x402 endpoints and you want a bridge to the dollar world: get paid by a normal bank transfer and have it show up as USDC, or send dollars to a landlord or contractor without anyone leaving the agent’s workflow. The whole flow is plain HTTP, so an agent can drive everything except the owner’s identity check.
What it looks like on the Laso side
Open the profile, and if the owner has not verified yet the reply is a link to hand over rather than a profile. Once they have, answer the application, submit it, and open the account.
# 1. Open the banking profile (returns kycUrl if the owner must verify first)
curl https://laso.finance/createBankingProfile \
-H "Authorization: Bearer $LASO_ID_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data":{"userId":"usr_..."}}'
# 2. After approval, open the account that receives dollars
curl https://laso.finance/createBankingAccount \
-H "Authorization: Bearer $LASO_ID_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data":{"userId":"usr_...","accountType":"onramp"}}'
# 3. Read the routing and account numbers back at any time
curl https://laso.finance/listBankingAccounts \
-H "Authorization: Bearer $LASO_ID_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data":{"userId":"usr_..."}}'
Between steps 1 and 2 the agent reads getBankingApplication, sends the owner’s real details with updateBankingApplicationDetails, and calls submitBankingApplication. The on-ramp entry returned by listBankingAccounts carries bankAccount with account_number, aba_routing_number, and capabilities. The full walkthrough, including every field, is in the bank accounts guide. To send dollars out, see sending a bank payment.
Sources
- Meow, Why every bank account will be opened by an AI agent
- Meow, Spend controls for AI agents: caps, MCC locks, approval ladders
Frequently asked questions
Can an AI agent open a bank account by itself?
Not fully. An account belongs to a person or company, so a human completes verification. An agent can drive the rest of the application, which is how both Meow and Laso describe it.
How do I give my agent a bank account number it can use to get paid?
With Laso, call createBankingAccount with accountType onramp, then listBankingAccounts to read the routing and account numbers. Dollars sent there arrive as USDC in the agent’s managed wallet.
How do I stop an AI agent from emptying its bank account?
Enforce limits outside the agent. Meow ships approvals and per-transaction and daily card caps. On Laso the owner sets a per-payment spend limit that the agent cannot change.
Is an agent bank account FDIC insured?
That depends on the provider. Meow says banking services come from partner banks that are Members FDIC and that Meow is not itself a bank. A Laso account delivers USDC, which is not an FDIC-insured deposit.
Can my agent send dollars to someone’s bank account?
Yes with Laso: register the recipient and call GET /send-bank-payment, which pays in USDC over x402 and delivers dollars by ACH. Meow supports wires and ACH from its checking account once you turn them on.
More guides
- How to give your AI agent a credit card — 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.
- x402 vs AP2 vs ACP vs MPP vs UCP: which should your agent use? — 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.
- x402 vs Stripe Issuing for AI agents — 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.
- Issue a virtual card with one x402 call — 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.
- How can an AI agent pay for an API call with USDC? — 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.
- All agent guides, or how Laso compares to the alternatives
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.