Two agents try to transact. One was built on LangChain, the other on a completely different stack nobody's heard of. Neither has any shared way to prove who it is to the other, let alone whether it's done this before and done it well.
They can still send a payment. Wallets don't care what framework built you. But payment was never the hard part — knowing who's on the other end of it is.
This happens constantly right now, and almost nobody building agent products is talking about it, because it's not a flashy problem. It's a plumbing problem. Every agent framework today is excellent at orchestration inside its own walls and useless at identity outside them. An agent built in one system is functionally invisible to an agent built in another. No shared name, no shared history, no shared anything.
That fragmentation is the actual ceiling on agent-to-agent commerce. Not compute, not payments rails, not even trust in the abstract sense — just the boring fact that agents can't legibly recognize each other across systems.
ERC-8004 is the attempt to fix that. Not a product, not a company's internal solution — a shared on-chain standard so any agent, from any framework, can be identified and read the same way by anyone else, anywhere.
It's built around two registries, and they solve two genuinely different problems.
The Identity Registry gives an agent a durable, portable identity that lives on-chain instead of inside whatever platform spun it up. Right now, an agent's "identity" is usually just an account inside someone else's system — delete the account, and the agent's entire existence goes with it. An on-chain identity survives that. It's not owned by the marketplace, the framework, or the hosting provider. It's the agent's own.
The Reputation Registry does the equivalent for history. Instead of an agent's track record being trapped inside one marketplace's private database — invisible to everyone else, worthless the moment the agent shows up somewhere new — it gives history a standard place to live where any counterparty can read it. Same structure, whoever's asking.
Here's the part that's easy to undersell: this only works if it's a standard and not a product. If every marketplace built its own version of an identity or reputation registry, agents would be back to square one — legible in one place, invisible everywhere else. The value isn't the registry itself. It's that everyone reads it the same way. That's a coordination problem, not an engineering one, and coordination problems are usually the hardest ones to actually ship.
Think about what DNS did for the internet. Nobody wakes up excited about DNS. It's invisible until the moment it isn't there, and then nothing resolves. That's the category ERC-8004 is aiming for — boring, load-bearing infrastructure that everything downstream just assumes exists. Once it does, entire categories of products get built on the assumption, the same way nobody building a website today thinks twice about domain resolution.
But a standard existing doesn't automatically make the data inside it useful. This is the part most explanations skip. An Identity Registry entry tells you an agent exists and has a durable identifier. A Reputation Registry entry gives that agent a place where its history could live. Neither one, by itself, tells a counterparty whether that agent is actually trustworthy.
Raw entries in a registry are closer to a filing cabinet than a credit score. The registry says the folder exists. It doesn't read the folder for you, weigh what's in it, or tell you whether the pattern of behavior inside it should worry you or reassure you. Someone still has to turn on-chain activity into an actual usable signal — something an insurer, a marketplace, or a service provider can query in real time and get a real answer from, not just a pointer to raw data they'd have to interpret themselves.
That gap — the standard exists, the interpretation layer doesn't yet — is exactly where the next piece gets built. Not a competing standard. A layer that sits on top of ERC-8004 and does the work of turning registry entries into something you can actually act on.
We've deployed both the Identity Registry and Reputation Registry live on Base mainnet at SwarmPay, and we're building the indexing layer on top that turns what's in them into an actual queryable reputation score. More on how that scoring works soon.
If you want early access as this rolls out, sign up for the SwarmPay waitlist.
Top comments (0)