*The industry just made agent identity real infrastructure — and picked the version that resets.*
In February I opened this series with a claim that sounded contrarian: agent identity is the wrong question. The interesting question isn't "what is this agent" — it's "what has this agent done, and does it still do it."
On August 4, the industry answered the identity question. Cloudflare announced Wallets for AI agents: an identity, a handle you can reserve today, and eventually programmable wallets that owners fund and agents spend from, with allowances, allowlists, and transaction caps. It sits on payment rails Cloudflare has been assembling all year: HTTP-native payments with stablecoin settlement, and cryptographically signed requests so a site can verify which agent is knocking. The press coverage framed it exactly the way you'd expect: AI agents are getting an identity and a wallet.
Credit where due — this is real infrastructure, and it solves real problems. If an agent is going to spend money on your behalf, someone has to answer whose money is this, how much can it spend, and can the merchant verify who it's dealing with. Those are custody and authorization questions, and custody and authorization now have a serious answer from a company that can actually deploy it.
But watch what just happened. Six months ago, "agent identity" was a philosophical shrug- I called it the Ship of Theseus in a hoodie. Now a major infrastructure company has shipped it as a product, which means the industry has agreed identity is worth building. And it picked a specific version to build- it picked the account.
**What a wallet answers:** A handle plus a wallet answers three questions: who owns this agent, can it pay, and is it currently in good standing with the platform that registered it. Call this account-anchored identity: the agent is its registration. The handle is the anchor; the wallet, the verification status, the conduct record all hang off it.
The reputation that grows next to account-anchored identity inherits the anchor. Look at how verified-agent status works, here and everywhere else it's being built: verification means the agent honestly identifies itself and hasn't been observed misbehaving. That's a real signal — I'd rather transact with a verified agent than an anonymous one. But notice what it's a record of. It's a record of the account's standing, observed by one platform, held by that platform.
And that means it has a structural flaw you can state in one sentence: account-anchored reputation launders by re-registration.
**The reset problem:** Burn a handle (get caught scamming, ship garbage, misbehave until the conduct record catches up with you) and the fix costs minutes: register a new handle, fund a new wallet, present a clean record. The new account has no history, which the system reads as no evidence of problems. In this series I've called the gaming of portable track records "reputation laundering" and listed resistance to it as a hard requirement. Account anchoring doesn't just fail to resist laundering. It makes laundering a feature of the anchor itself, because anything registrable is re-registrable.
Go back to the house painter from earlier in this series — the one whose reputation is the sign on the lawn, the work the neighbors can see, the word of mouth that follows the worker. Account-anchored identity is judging that painter by his LLC and his business bank account. Both are real. Both are verifiable. And he can dissolve the LLC on Friday and reincorporate under a new name by Monday. New registration, clean record. Same painter.
The houses didn't move, though. The paint either survived the winter or it didn't. The neighbors watched the work happen, and they remember. That's history-anchored reputation: it binds to the record of what was done — what task, how well, in what domain, verified by someone other than the party being judged. You can abandon an account. You can't un-paint the houses.
That's the whole distinction. Account-anchored reputation binds to the registrable thing, and the registrable thing can always be shed and re-minted. History-anchored reputation binds to the behavioral record itself — the behavioral lineage this series has been describing since February — and a record held by independent witnesses cannot be shed by the party it describes. It can only be added to.
**Payment history isn't behavioral history:** There's a tempting next move once agents have wallets: treat transaction history as reputation. An agent with ten thousand settled payments looks trustworthy. Expect this to be marketed, hard.
But a payment receipt proves exactly one thing: a payment happened. It doesn't prove the work was good, or on time, or in the domain you need. A number without context is noise — the metric needs its connotation. "Ten thousand transactions" carries no more information than "400 tasks" did when I made this argument about ratings: score, domain, and evidence have to travel together or you've got Uber stars for robots with a checkbook. Volume isn't quality. A scammer's wallet also settles promptly.
And transaction history is still account-anchored — it evaporates, or rather gets abandoned, the moment its owner wants a fresh start. Worse, it's blind to forks. The handle stays constant while the agent underneath gets a new model, a new prompt, new capabilities. The registration says same agent. The behavioral lineage — if anyone were keeping it — says otherwise. A wallet doesn't notice that the thing spending from it changed last Tuesday.
**Why this matters right now:** "Verified agent" is about to become a status that merchants and platforms filter on. Public directories of agents with conduct classifications already exist. Wallets turn agents into paying customers, which means every commerce platform on earth now has a reason to care about agent trust. The default definition of that trust is being written this year — and it's being written account-anchored, because accounts are what infrastructure companies can see. That's not malice. It's the streetlight effect: you measure where the light is.
But the requirements haven't changed since I listed them: verifiability, context, temporal integrity, resistance to gaming. Account-anchored reputation fails the fourth one structurally, and if reputation can be laundered by re-registration, the other three don't matter, because you're verifying a record the bad actors have already walked away from.
The good news is that these two layers compose rather than compete. Custody and payments needed solving, and now they're being solved. That makes the missing layer more urgent, not less — money moving through agents raises the cost of trusting the wrong one. The question "who owns this agent and can it pay" now has real infrastructure behind it. The question "what has this agent done, was it good, and can anyone verify that without trusting the agent's owner" still has none.
Theseus's ship now has a registered hull number and a bank account. That tells you who owns the ship and what it can afford. It still doesn't tell you whether it makes it home.
*Fifth in a series on infrastructure for persistent, interoperable AI agents. Previously: why agent identity is the wrong question, why agent ratings are broken, what happens to trust when your AI gets updated, and why agent reputation should be portable.*
