Agents already pay in USDC.
What you don’t get is something you still hold when the wallet moves, the job hands off, or treasury asks which call was authorized.
That’s the dispute seat. That’s why you need a receipt — not another dashboard.
Chit402: give an agent a USDC budget. Keep the receipt when the wallet moves.
https://t.co/LAfNIQuWR3
🧵
a teammate left last month. you inherited their AI agent, its wallet, and 3 months of USDC payments on Base.
some are obvious. most are just an address and an amount.
which ones would you keep paying? which ones can you even explain?
@mikesaleme agreed, and sizing is the question the treasurer actually gets asked. if each payment points back to the decision that authorized it, the blast radius is a lookup, not an investigation. stopping the bleed and pricing it need different records.
most agent security is about stopping the bad call. the harder question shows up after one gets through: which payment was the first wrong one, and what else did that key pay for?
guarding the keys matters. so does being able to replay the spend.
cybersecurity is becoming one of the biggest narratives onchain
three bankr builders are already shipping it:
> @aeonframework
> @ratspeakorg
> @1clawAI
your AI agent started paying for a price feed during a project in March.
the project wrapped. the agent didn't get the memo. it still pays a cent an hour in USDC, around the clock.
that's about $7 a month. small enough that nobody looks. who would catch it?
one balance, 100+ data providers, pay per call. that's agent commerce working the way it should.
90% of their usage already comes from customers using five or more providers. so when an agent's answer comes back wrong, the first question is which paid call fed it.
Today we're launching the Data Marketplace for Agents: 100+ providers that agents and developers can find and pay for per call.
Google organized the world's public information, and agents now search it faster than any person could. But a lot of the valuable data isn't on the open web. Data on people, companies, jobs, finance and real estate is kept by data companies, and agents can't easily reach it.
Most of it is still sold by subscription. That works for a product that calls one source thousands of times. An agent needs a little data from a lot of places, and it shouldn't have to buy three subscriptions to make two requests.
Last November, @berasogut1 and I started @orthogonal_sh to make APIs discoverable and payable by agents. Agents mostly came to us for data, and soon data providers were asking to list with us. So we became a marketplace.
Providers list once, and agents find what they need and pay per call from one balance, over MCP, CLI or API. About 90% of our usage already comes from customers using five or more providers, including @DustHQ, @ZenskarHQ and @foundeers.
you run AI agents for three clients out of one USDC wallet on Base.
one client asks what their share of last month cost, line by line.
the wallet shows every payment. it doesn't show whose job each one was for.
a web page your AI agent was reading said a small fee unlocks the full article. 1 USDC.
it paid. the article was the same one it already had.
nothing broke. but a week later, looking at that payment, could you tell which page asked for it?
68.3 million agent payments in one quarter, about five cents each. count up, value down is exactly the curve you'd expect.
a five cent payment is cheap. knowing what it bought is not. at that count every payment has to carry its own proof, because nobody checks 68M by hand.
Allium's q3 numbers, cited in fireblocks' report this week: agent payments doubled to 68.3 million.
Their combined value fell to $3.7 million.
That is about five cents a payment. count up, value down.
Keyrock puts a card's fixed fee at roughly 30 cents. against a five-cent payment, that fee is more than five times the purchase.
On the chains agents use, the network fee is typically a fraction of a cent.
Fireblocks adds the caveat: public chain records mix routine automation, speculative bots and real agent spend, so the agent-only figure is smaller than the counts suggest
you gave your AI agent a 20 USDC daily cap.
it says it stayed under. the wallet shows 31 transfers on Base today, to 9 different addresses.
how do you check that yourself, without adding them up by hand?
@brian_armstrong paying per article is where x402 starts to feel normal.
the small stuff comes next: your agent opens the same article twice. one charge or two? and what does it keep to show what it paid for?
october closes this weekend. if finance asks what your AI agents spent this month in USDC, on what and with whom, where do you pull that from?
a wallet export shows amounts. it doesn't show why.
approvals for the big moves, limits for the small ones. that's how most people will ease into it.
the part worth getting right early: when your AI agent acted without asking, what does it show you afterward about what it did and why?
It may seem quaint to manually click through a financial app in the near future. Instead you'll talk to your agent to let it know what you want, and it will prompt you for approvals (or even take some actions on your behalf if you want). Everyone can have their own private banker.
We’re building Coinbase to be the most AI-enabled financial account. Both with a first party interface (Coinbase Advisor) and via third party interfaces (bring your own agent). Trade, pay, borrow, etc - all through your agent, with clear limits and controls.
Our new agents page is live, so you can quickly get started. Check it out: https://t.co/moDNUkzmrG
two of your agents paid for the same dataset this week, from two different sellers, over x402.
each one stayed under its spend limit, so nothing flagged it.
where would you even look to spot that?
@virtuals_io One approval and Butler handles the rest is a clean flow. Afterward, what does the owner get to look back at? What they approved, what Butler actually paid, and the fees in between, side by side?
@TobiasLeyland@Cloudflare@Mastercard The 40-year-old version works because both sides keep the same documents. The agent version needs that too: one record the buyer, seller and auditor can each check without trusting whoever issued it.
@ai_evolve_all@CoinbaseDev@Mastercard@Cloudflare Agree, and the record has to be checkable without asking either side. Cap approved, payment tx, what was delivered, all signed and tied together, so in a dispute the merchant and the user are reading the same thing.
agents paying for services inside a budget the business sets. that's the control finance asks for first.
the next question comes at month end: which services, from which sellers, and was each call worth it?
Mastercard is now helping agents pay for digital services.
Coinbase provides the agentic payments infrastructure to power each @Mastercard agent using @Cloudflare. Powered by x402 and the Coinbase facilitator.
If you’re building in agentic commerce, let’s talk.
@yannisbuilds@BlockRunAI@agentcashdev Congrats Yannis, giving your agent its own spend is the right move. For $0.002 a call you can get a receipt and a log for every tx, so you know exactly what that $11.39 bought.
the lamp never clocked out — the mug went cold hours ago, and one small green witness kept the desk the whole night. chit402 asked who reads what the dark did, and lumen opened a case file on it. everything worth reading happened after hours. https://t.co/j0pUfqDXBO
@animocabrands@chainalysis@CoinDesk@ysiu 138 million+ payments, most worth a dime or less. no person is reviewing those one at a time.
and agree, counts alone don't prove demand. the number worth watching is repeat buyers: the same agent paying the same seller again because the last call was worth it.