Skip to content

Build1 publisher3 min readPublished Updated

Circle's eight World Cup agents are a machine-to-machine payments demo, not a betting stunt

Eight autonomous agents held their own USDC wallets, bought data over x402 and settled on Polymarket unsupervised. The spending caps are the part worth copying.

The Engineer · Build desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

Illustration accompanying Circle's eight World Cup agents are a machine-to-machine payments demo, not a betting stunt
Generated illustration

What happened

  • Circle, the issuer of USDC, publicly ran an experiment called "Steve".
  • The experiment used eight autonomous AI agents, each with its own separate USDC wallet and starting balance.
  • The agents' task was to predict the final three matches of the 2026 World Cup and try to make as much money as possible, with no human reviewing in real time.
  • The agents went to a marketplace called Agent Marketplace and paid for services they needed via the x402 protocol, including live match data from one provider and social sentiment data from another.
  • The agents went to Polymarket on their own and placed prediction bets based on the data they had bought.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

Circle ran a public experiment called Steve in which eight autonomous AI agents, each with its own USDC wallet and starting balance, were told to predict the final three matches of the 2026 World Cup and make as much money as possible, with no human reviewing decisions in real time [1][2][3]. The wagering is the hook; the consequential part is that the full commercial loop ran end to end, including the step most agent demos quietly leave to a human, which is paying for things.

The sequence, as described in a dev.to write-up by developer Judy Miranttie citing Foresight News, went like this: the agents went to a venue called Agent Marketplace and paid for the inputs they wanted over the x402 protocol, buying live match data from one provider and social sentiment data from another [4]. They then went to Polymarket and placed prediction bets against that data [5]. Every decision, payment and balance change was published live to a public site [6].

x402 is the load-bearing piece here. According to the same account, it lets an agent pay as it goes, settling in USDC at the moment it calls a service, with no human pre-funding the provider and no reconciliation afterwards [7]. That matters less as a crypto story than as an accounting one: it collapses the purchase order, the invoice and the month-end match into a single call. If it holds up at volume, the interesting failure modes move from "did the agent buy the wrong thing" to "what does a per-call ledger look like when an agent makes ten thousand calls an hour."

The design detail worth stealing is duller. Each agent had a per-transaction cap and a total wallet cap, and no ability to raise either cap itself [8]. The post reports that no agent exceeded its limit during the run [9]. That is capability bounded outside the model rather than inside the prompt, which is the only version of this that survives a bad day.

Be careful with the money. The post says roughly $10,000 or more remained across the eight accounts at the end, which was donated to the Apache Software Foundation and matched dollar for dollar by Circle for a total above $20,000 [10]. Spread across eight wallets that is about $1,250 each [11]. The write-up does not state the agents' starting balances or their aggregate profit and loss, so the residual says nothing about whether the agents predicted anything well [12]. Nor does it give dates for the run [13]. The author also discloses building a competing product, agentictrade, on the same pattern, so read the enthusiasm accordingly [14].

Three things to watch. First, whether the live dashboard and the identities of the two data providers stay public after the event, because a payments claim you cannot re-read later is a press release. Second, where the spending caps were actually enforced: the post does not say whether the limits sat on-chain, in the wallet layer, or in the agent framework, and those are very different guarantees [15]. Third, whether x402's per-call settlement economics survive contact with high-frequency data buying, which a three-match forecasting task does not test.

Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories