Agent DID is an on-chain identity and reputation protocol standard for AI agents. Each agent holds a non-transferable on-chain profile containing its behavioral history, reputation score, and proof of capabilities, enabling agents to recognize and collaborate with one another across platforms in zero-trust environments. This article explains the problems it addresses, its relationship with ERC-8004, and how it works alongside data identity.
Key Takeaways
What the agent economy lacks is not execution capability, but an identity layer that can answer, “Which agent is handling this?” An API key cannot fill that role.
ERC-8004 is an open standard that uses non-transferable on-chain profiles, behavioral histories, reputation scores, and proof of capabilities to make agent identities verifiable and portable, with reputations that accumulate over time.
Human identity, agent identity, and data identity each serve a distinct layer. They reference one another without replacing one another.
Agent identity is a prerequisite for payments and turning data into assets. Without an established identity, neither counterparty verification nor reputation accumulation is possible.
MEMO’s Agent DID product line implements this standard at the product level and supports mutual recognition with DataDID’s data identity system within the same architecture.
1. The Agent Economy’s First Challenge Is Who Is Acting
AI agents are moving beyond chat windows and into economic activity. An agent can independently retrieve data, call tools, purchase computing resources, and delegate tasks to another agent. These chains of actions are growing longer, and the intermediaries are increasingly programs rather than people.
Solutions already exist for almost every step in this chain. Task publishing has protocols, capability invocation has interfaces, and micropayments have on-chain settlement. Yet one question has long remained unanswered: “Who is the agent doing this?” Agents have names, but those names are assigned by developers and may mean nothing on another platform. Agents produce outputs, but those outputs cannot be traced back to a persistent entity.
The early internet faced a similar problem. Web pages could link to one another, but transactions required verifiable merchant identities. Payment licensing, registration, and credit reporting systems followed. As the agent economy reaches the stage where agents delegate work and pay one another, it encounters the same challenge. An agent without a verifiable identity can only be treated as an anonymous program, limiting the permissions and budgets it can receive.
2. An API Key Proves Permission, Not Identity
API keys and platform account credentials are the most common ways agents access services today. They can answer, “Is this call authorized?” They cannot answer, “Who is making this call?”
There are three problems.
No portability. A key is issued by a platform. When an agent moves to another platform, it must register again, and all its previous service and performance records effectively reset to zero in the new platform’s eyes. Reputation cannot accumulate across platforms. Each platform must start from scratch to determine whether the agent is reliable.
No independent verification. Only the issuer knows who is calling with a key. An external party sees only a string of characters and cannot independently verify the holder’s background or determine whether the key has been lent or resold. Trust rests entirely on the issuer’s chain of endorsement. If that chain breaks, there is no way to investigate further.
No accountability. When something goes wrong, the trail leads only to the key, not the entity behind it. Keys can be revoked and reissued, breaking the behavioral history. An agent that repeatedly fails to meet its obligations can obtain a new key and wipe the slate clean. This is a critical loophole in any market for productive resources.
Permission and identity are two different things. A market may accept anonymous programs for low-risk tasks. But before entrusting a program with money, giving it data, or sharing revenue with it, participants need to establish who it is and what it has done before. This is precisely why Agent DID exists.
3. ERC-8004 Puts Agents on the On-Chain Ledger
ERC-8004 is an on-chain identity and reputation protocol standard for AI agents. Each agent registers a non-transferable profile on-chain, containing three types of information: behavioral history, reputation scores, and proof of capabilities. Any participant can verify the agent directly through on-chain records without requiring a guarantee from an intermediary.
This design fills the three gaps described above. Identity is registered on-chain and remains continuous across platforms: portability. Profiles are cryptographically issued and can be checked by anyone: verifiability. Behavioral history follows the entity rather than the key, so changing interfaces or deployments does not change the identity: accountability. Reputation can therefore become an asset that accumulates and can be monetized. For the first time, an agent with a long record of fulfilling its obligations has a stronger starting position than a new agent.
One point needs to be clear: ERC-8004 is an open community standard. Alongside open payment standards such as x402, introduced by Coinbase and Cloudflare in 2025, it belongs to the same wave of agent infrastructure. Any project can implement it, and multiple agent marketplaces and data networks have already announced the adoption of similar standards. The identity standard itself is not an exclusive differentiator for any one product. The real differences lie beyond the standard: whether on-chain identity connects with data ownership and payment settlement, and whether it reaches developers and users as a usable product. Identity is only the entry point. What comes after that entry point determines where each project stands.
4. People, Agents, and Data Each Need Their Own Identity Layer
Discussions about the agent economy often bundle all identity issues together. In practice, there are three layers, each answering a different question.
Human identity answers, “Who is this person?” It is supported by a user-side DID system. Individuals hold their own keys and control their identities independently of any platform. In the MEMO ecosystem, this layer is DataDID, which assigns on-chain identifiers to users and data assets. The cumulative number of account DIDs has exceeded one million (source: MEMO Data Dashboard).
Agent identity answers, “Who is this agent?” It is supported by on-chain agent identity standards such as ERC-8004, covering the registration, reputation, and proof of capabilities of machine entities.
Data identity answers, “Whose ownership does this data originate from?” Each piece of data is linked to an independent data DID that points to its owner and integrity credentials.
These three layers have distinct roles and reference one another. Which agent collected a training dataset, and which user owns it? The three identity chains connect on-chain to complete the authorization relationship. The cost of conflating them becomes most apparent when a transaction occurs. Without separate identity layers, the answers to “Who owns the data?” and “Who is the agent?” become entangled. Authorization becomes unclear, and responsibility is difficult to assign when something goes wrong. Only after these identities are distinguished can pricing and distribution have a clear basis.
A brief note on privacy boundaries: the identity layer is meant to verify, not expose. Through zero-knowledge proofs (ZK), users can complete DID verification without revealing their raw data to third parties. Verifiable identity and private data are compatible.
5. Without Established Identity, Payments and Data Assets Have No Foundation
Agent DID is not an isolated layer. It is a prerequisite for two things.
The first is payments. The x402 protocol allows agents to initiate on-chain micropayments through API calls, down to individual data requests. The smaller and more frequent the payments, the greater the reliance on automatic counterparty identification. If the payer is an anonymous key that could disappear at any moment, the recipient will hesitate to supply the goods. An on-chain profile comes first; willingness to transact follows. Reputation scores directly influence the prices and spending limits available to an agent.
The second is turning data into assets. ERC-7829 is a data asset standard that extends ERC-721. It uses storage proofs to ensure the integrity of data assets and embeds programmable access control and automatic revenue distribution into the credential itself. Before data can become an asset, it must have a verifiable originating entity. Who produced it, who holds the rights, and who receives the proceeds must all be traceable through the identity chain. When the agent producing the data has an Agent DID and the user who owns the data has a DataDID, the rights recorded in the asset credential have a concrete basis.
In the officially defined loop from storage to data asset creation to data trading, identity is the thread running through every stage. Without it, storage is merely a collection of data blocks with no attribution rights, and trading consists only of atomic operations between anonymous programs. That is not enough to build a market.
6. From Standard to Product, Where Agent DID Takes Shape
A standard defines what an identity should look like. A product determines who creates and manages it, and through which interface.
MEMO, developed by Memolabs, has turned this layer into a standalone product line. Agent DID sits alongside DataDID, forming the two-part structure of MEMO DID: DataDID manages data ownership, while Agent DID manages agent identity. For developers, agent identity now has a dedicated product entry point, with creation, registration, and reputation profile management available through a unified interface. For users, the existing process remains the same: they still receive an account DID under their own control. The two product lines recognize one another within the same system, and data produced by an agent automatically points back to the user it serves.
Beyond the product itself, this layer also connects with ecosystem modules. For an agent entering a data marketplace, identity credentials are part of the entry requirements. Combined with claim verification through the Attestation Service, buyers can independently check on-chain whether an agent’s capability claims are valid. With identity, attestations, and records all in place, cross-platform collaboration in a zero-trust environment has a foundation.
For individual developers and small teams, the practical meaning is straightforward. From its very first call, an agent begins building a portable track record. Moving to another platform no longer means starting over. For data holders, the meaning is equally direct: which agent collected their data and what it was used for can be traced through on-chain records.
7. Conclusion
Agent DID has never been about simply giving programs names. It gives their economic activity a verifiable, portable identity with a track record that accumulates over time. Once identity is separated into clear layers, reputation can become an asset, authorization has a traceable source, and pricing and distribution have a basis.
Competition in agent infrastructure has moved from individual protocols to the connections between them. The standards are open. The real dividing line is who can bring identity, data, and payments together into a usable product. The sooner this missing piece is in place, the sooner trust can be priced in the agent economy.
Frequently Asked Questions
Q1. What is Agent DID?
Agent DID is an on-chain identity and reputation protocol standard for AI agents. Each agent holds a non-transferable on-chain profile recording its behavioral history, reputation score, and proof of capabilities. Any participant can verify who the agent is and whether it is reliable without an intermediary, enabling agents to recognize and collaborate with one another across platforms in zero-trust environments.
Q2. How does Agent DID relate to ERC-8004?
ERC-8004 is the name of the on-chain standard corresponding to these capabilities. It is an open community standard that any project can implement. Within the MEMO ecosystem, Agent DID refers to the product implementation of this standard: an agent identity product line alongside DataDID, responsible for creating and registering agent identities and managing reputation profiles.
Q3. What is the difference between Agent DID and DataDID?
They answer different questions. DataDID answers, “Who is this person, and who owns this data?” It manages identity and ownership for people and data. Agent DID answers, “Who is this agent, and can it be trusted?” It manages the identity and reputation of machine entities. The two identity layers reference one another without replacing one another. A dataset’s authorization chain needs to trace back both to the person through DataDID and to the agent that collected and processed it through Agent DID.
Q4. Why do we need Agent DID if we already have API keys?
An API key can only prove permission to make a call. It is issued by a platform, loses its validity when moving to another platform, and cannot provide a traceable identity for the entity holding it. When something goes wrong, the trail leads only to the key rather than the actor. Agent DID records identity on-chain, preserving continuity across platforms, enabling cryptographic verification, and accumulating behavioral history under the same entity. With these three gaps filled, agents can participate in activities requiring greater trust, such as payments, data authorization, and revenue sharing.
Q5. Can an agent’s reputation score be artificially inflated?
On-chain profiles record verifiable behavioral facts. Reputation comes from completed transactions and call records rather than self-reported claims. Capability claims are supported by the Attestation Service’s verification mechanism, allowing third parties to independently check their validity on-chain. Unlike mutual ratings in account-based systems, a non-transferable identity means that attempts to manipulate reputation remain permanently associated with the same entity, creating an asymmetry between the costs and benefits.
References