Who funds the agent

The most asked question under the video was where agents get their money. The short answer is that you give it to them, with a budget. This lesson shows how, and what changes compared with an API key.

Say you run a small business that sells crop forecasts. Your agent needs about 5,000 rainfall readings a month from the farmer in the last lesson, at $0.001 each. That’s $5 a month.

Who funds the agent

The agent doesn’t earn that $5. You do, and you hand it over. Under the video, someone asked where agents get their cash, and the best reply in the thread had it right: the owner tops up the agent’s wallet, and the agent pays for services as it needs them. What x402 adds is a way for an agent to spend money someone has given it, in very small amounts, without asking each time.

Four steps, and only the first is about money

1. You fund a wallet. You buy USDC and put it in a wallet your agent can use. With Coinbase’s Agentic Wallet, for example, you click Fund and buy USDC through Coinbase’s onramp, where its standard fees apply, and the wallet holds USDC on Base, Polygon or Solana (14 Oct) source.

Four steps, and only the first is about money

2. You set limits. Coinbase’s own example limits are $0.05 per call and $5.00 per session (14 Oct) source. Its docs say: “Agents respect these limits but can’t change them.”

3. The agent pays inside them. Every time a seller answers 402, the agent’s payment software compares the price with your limits before it signs. A $0.001 reading passes. A $40 request would be refused, and no money moves.

Four steps, and only the first is about money

4. You watch and top up. Each payment leaves a receipt with a public transaction hash, so you can see exactly what the agent bought and from whom.

What exists today

As of 14 October 2026, these are the main ways to give an agent a budget.

What exists today

What exists today

What exists today

How is this different from an API key?

Here is how you would buy rainfall data with an API key. You find a provider, create an account, add a card, pick a monthly plan, copy the key and paste it into your agent. If the agent finds a better source tomorrow, you do it all again, and the agent waits until you have.

How is this different from an API key?

With x402 you fund one wallet once. The agent can pay a seller it discovered five minutes ago, for exactly the calls it makes, with no account and no key. The seller is paid before the data leaves its server, so it doesn’t need to trust you, send invoices or chase late payments.

A commenter pushed back: all paid integrations already charge the owner, so what changes? That’s fair. The owner still pays. x402 changes three things:

• Who you have to sign up with. Nobody, per seller. One wallet works with every seller that speaks x402.

How is this different from an API key?

• How small a purchase can be. One call at $0.001, where card payments through Stripe’s machine-payments product start at $0.50 (14 Oct) source.
• When the agent can decide. It can try a new source on its own, inside the budget you set, instead of waiting for you to open an account.

It doesn’t change whether the data is worth buying, which is the next lesson. For heavy, steady use of one provider, an API key on a monthly plan can still be the simpler choice.

How is this different from an API key?

What can go wrong for the owner

The risk is the one you’d expect: an agent with a funded wallet can spend up to its limits, whether it’s working well or not. Keep the wallet balance small, cap each call near the prices you expect, and cap each day or session. A payment that fails costs nothing: Coinbase’s wallet FAQ says no funds are deducted.