Letting Your Agent Spend Money

Most AI agents are read-only. They fetch, they summarize, they post. They can describe the world but they can’t transact in it. Ask one to check live prediction-market odds, pull a premium weather forecast, or hit a paid search API, and the agent stops at the paywall and asks you for help.

Aeon plugs that gap with two pieces: x402 — a stablecoin micropayment protocol revived by Coinbase — and Circle’s agent wallet, plus the operating discipline of letting an agent reach for its own wallet instead of asking you.

This post is the full recipe. By the end you’ll know what a paid call looks like end to end, what the caps and seatbelts are, and which kinds of skills become buildable that weren’t before.

An agent that wants to act in the world has to authenticate to services. Today that means:

• You sign up for an API.
• You get a key.
• You paste the key into a secret store.
• You attach a credit card to the billing account.
• You monitor the spend so the agent doesn’t run away with it.

Every new capability is a five-step human ritual. Multiply by a dozen APIs and the agent becomes a thin wrapper around your manual procurement work. Worse, the agent is blind to cost — it has no idea which call is expensive, no way to compare providers, no way to discover a new one.

The fix is to give the agent its own money and a protocol to spend it. That’s what x402 and Circle’s agent wallet do.

x402 is a payment protocol that turns HTTP 402 — the long-unused “Payment Required” status code — into a real, usable handshake. A service publishes a price, a client (your agent) hits the endpoint, gets back a 402 with payment requirements, sends a small USDC payment, and retries the request with proof of payment. The whole loop takes seconds and costs cents. No accounts. No keys. No prefunded billing.

The x402 bazaar is a marketplace of services that speak this protocol — currently covering prediction-market odds, web search, news, weather, sports stats, crypto prices, premium research, and more. Anyone can list a service. Anyone — including an agent — can pay for one call.

x402 needs a wallet on the buyer side. Circle’s CLI gives agents one. You install circle, the agent logs in once, and it gets a USDC wallet on Base with per-transaction, daily, weekly, and monthly spending caps. The wallet is the auth — there is no API key.

In Aeon, the wallet is configured once at fork-onboard time. From then on, any skill can pay against any x402 listing with circle services pay, within the caps you set.

Here’s what a paid call actually looks like from an Aeon skill. Three commands.

Step 1 — find a service

circle services search "prediction market odds"

The CLI returns a ranked list of x402 listings that match. Each entry includes the URL, the price per call, and a short description. The agent picks one.

Step 2 — inspect the contract

circle services inspect <service-url>

Returns the input schema, the output schema, the exact price, and any usage notes. The agent uses this to construct a valid request before committing money.

Step 3 — pay and receive

circle services pay <service-url> --input '{"market": "btc-100k-by-eoy-2026"}'

This is the whole transaction. The CLI sends the USDC payment, waits for the 402 retry, and returns the response JSON to stdout — the data the caller actually wanted. A skill consumes the JSON and writes the result into the day’s Telegram message, into memory, or into a downstream skill’s input.

That’s the full loop. From the skill’s point of view, it’s three shell calls. From the agent’s point of view, it’s the difference between “I’d need an API key for that” and “I just bought the data.”

The obvious question — what stops the agent from emptying the wallet? — has a clean answer.

The Circle agent wallet enforces four cap layers, set once and visible at any time via the CLI:

• Per-transaction cap — refuses any single call above the limit.
• Daily cap — rolling 24-hour window.
• Weekly cap — rolling 7-day window.
• Monthly cap — rolling 30-day window.

You inspect them with circle wallet policy. You change them in an interactive terminal session that requires an OTP — no agent can edit its own caps. The seatbelt is enforced at the wallet, not in the prompt.

For most personal Aeon setups, sensible defaults are something like $0.50/tx, $5/day, $25/week, $50/month. That’s enough to pay for every paid call a daily agent could realistically make, while making it impossible for a misbehaving skill to drain the wallet overnight.

Read-only agents become acting agents. Concretely, things that were unbuildable or rate-limited become trivial:

Prediction-market odds in a morning brief

A narrative-tracker skill that paid $0.02 to pull live odds on the markets it’s watching is more useful than one that paraphrases yesterday’s news. The cost is a rounding error against the signal.

Premium search when free search rate-limits you

Most free search APIs are throttled, capped, or both. A morning-brief that hits the cap halfway through gets a degraded output. A skill that can pay for one premium search per run never hits the cap.

Weather, sports stats, news — anything with a paywall

Every category in the x402 bazaar is a capability that used to require an account, a key, a billing relationship. The agent can now sample any of them, one call at a time, and keep going.

“I can’t do that” becomes a recoverable failure

When an agent says “I’m rate-limited” or “I don’t have access to live data” or “I’m behind a paywall,” the operator now has a fix: route the request through circle services search and pay for it. That’s a one-line escape hatch, and Aeon’s skill catalog increasingly treats it as the default rescue path when a free path fails.

A skill that uses paid x402 calls is no different from any other Aeon skill — same Markdown file, same chain syntax. Here’s a stylized chain:

chain:
  - skill: narrative-tracker
    when: cron("0 12 * * *")
    output: narratives.json
  - skill: paid-odds-lookup
    input: narratives.json
    output: odds.json
  - skill: morning-brief
    input: [narratives.json, odds.json]
    delivers: telegram

The middle step is the one that costs money. The cap is enforced at the wallet. The receipt is in git — memory/spend-log.md keeps a running ledger of every paid call.

Two honest limits.

It is not a replacement for trusted-vendor accounts. If your skill needs OpenAI, Anthropic, or another provider with strict terms of service, you still use an API key. x402 is for the long tail of services that can be paid for per call without a business relationship.

It is not anonymous. The wallet is on Base. Transactions are public. If the privacy properties of payment matter to your use case, plan accordingly.

If your Aeon fork doesn’t yet have the wallet configured:

brew install circle
circle wallet login
circle wallet create

Fund it via fiat on-ramp (circle wallet fund) or by sending USDC to the address. Then set the caps:

circle wallet policy set --per-tx 0.5 --daily 5 --weekly 25 --monthly 50

Setting caps requires an OTP — Circle will prompt you. The wallet refuses any policy edit that doesn’t go through the OTP step, which is why no agent can quietly raise its own ceiling.

From here, any skill in your catalog can call circle services pay. The first time it does, you’ll get a Telegram notification showing the receipt. That feedback loop is, intentionally, the most boring thing in the world — and that’s the point. The agent is just doing its job, and paying for the data it needed to do it.

Article 4: Skills that build skills. Why an Aeon skill is a Markdown file, how skills chain inside aeon.yml, and what it means that the agent can author its own skills — with git log as the audit trail.