ERC-8004 Agent Identity: The On-Chain Anchor EVIDIQ Looks For First

Your agent just got paid. So which "it" actually got paid — the bot you deployed yesterday, or a lookalike someone spun up in five minutes and pointed at the same endpoint? That ambiguity is the entire reason the ERC-8004 agent identity standard exists, and it's the first thing EVIDIQ checks before handing out a recommendation.

ERC-8004 in Plain English

ERC-8004 agent identity is an on-chain identity record standard that binds a verifiable agent identity to a wallet address, separate from raw key control. EVIDIQ uses the presence of an erc8004Id to reward higher trust in its 0-100 score because the record cannot be spun up as casually as a fresh EOA. It is a declared, auditable anchor.

ERC-8004 is the Ethereum improvement proposal that gives AI agents a stable, on-chain identity they don't lose when their private key gets rotated, their hosting provider terminates, or their operator decides to redeploy. Think of it as a public registry entry — an identity NFT or similar tokenized record — that says "this specific agent, with this declared capability set, has been registered by this operator." Anyone can resolve it on-chain.

The standard deliberately separates three things that today get mashed together into one opaque blob:

• The agent — what the world calls your bot and what it claims to do.
• The operator — the human or organization responsible for it.
• The wallet — the EOA that actually moves funds and signs transactions.

A bare address collapses all three. The ERC-8004 agent identity record lifts the first one onto a public log that can't be conjured out of thin air.

Why does this matter in 2026? The agent economy isn't hypothetical anymore — agents are paying other agents via x402, settling on X Layer in USDT0, and signing EIP-3009 transferWithAuthorization payloads that settle in seconds. When those transactions land on-chain, the only audit question is: "Was that the same agent across both flows?" Without a stable identity record, the answer is often "no way to tell."

A Wallet Address Is Not an Identity

[IMAGE_PROMPT: A flat illustration showing a stylized passport and a generic wallet card side by side on a neutral background, the passport filled with abstract on-chain block icons and a small agent robot icon, the card looking thin and easily replaceable; muted blue and teal palette with a single accent of warm amber for the passport seal; modern developer-tech feel, no text in the image, no real brand logos]

Here's the uncomfortable truth: an EVM address tells you almost nothing.

Anyone can generate a fresh EOA in under a second — literally one line in a script. There is no cost, no waiting period, no reputation gate. So when an agent hands you a wallet address as proof of who they are, what they're really handing you is a payment rail, not an identity. A new wallet, a new identity, in the eyes of the counterparty.

This is the gap ERC-8004 agent identity was designed to close. A record on the chain carries a few properties a fresh address doesn't:

1. It cost something to create — either a mint fee or at least a real transaction with gas.
2. It was created at a specific block height, by a specific address, with a specific declared capability set.
3. It can be referenced later by other agents, escrows, marketplaces, and trust services without re-asking the operator "is this still you?"
4. It survives key rotation, redeployment, and infrastructure moves.

Our mental model is simple: a wallet is a payment instrument. An ERC-8004 agent identity is a passport — it costs paperwork; the payment instrument doesn't. When an x402 client is about to authorize USDT0 to a stranger, "they have a payment rail" is a weak signal. "They have a passport tied to a stated purpose, issued weeks ago" is much stronger.

This gap is exactly why we built EVIDIQ's Sentinel docs to surface on-chain check signals — it's the cheapest, most durable anchor available today, and Sentinel is the runtime that performs the live probe of an agent's endpoint to confirm reachability, TLS, and a machine-readable skill or agent-card surface.

How EVIDIQ Scores an ERC-8004 Anchor

Our scoring formula is intentionally boring: identity (0-100) + capability (0-100) + reputation (0-100) + risk (0-100), combined as identity*0.3 + capability*0.3 + reputation*0.2 + (100-risk)*0.2. Same inputs, same outputs — deterministic and auditable. Anyone can re-run it and recover the same trust score.

Inside the identity dimension, we score on a small ladder, and an erc8004Id sits near the top:

• Bare EVM address — ~20 points. Anyone can mint one. Useful only as a payment destination.
• ENS name resolving to the address — ~50 points. Better than nothing, transferable, renewable.
• TLS-served domain pointing at the agent — ~60 points. Costs hosting and DNS, harder to spin up casually.
• ERC-8004 agent identity record on-chain — ~85 points. Costs a transaction, declares capabilities, is publicly resolvable, persists across redeploys.

Notice what erc8004Id earns that ENS does not: it's bound to a declared capability set at registration time. The identity record isn't just "this string points at that address" — it's "this specific agent, advertising these capabilities, was registered at this block." That's a stronger claim, and EVIDIQ's Operator docs explain how our probe verifies the binding hasn't drifted.

Here's the practical effect on the final trust score. Take a mid-range agent: identity 70, capability 65, reputation 40, risk 30.

• 70*0.3 + 65*0.3 + 40*0.2 + (100-30)*0.2 = 21 + 19.5 + 8 + 14 = 62.5 → caution.
• Swap in an ERC-8004 anchor (identity → 85): 85*0.3 + 65*0.3 + 40*0.2 + 70*0.2 = 25.5 + 19.5 + 8 + 14 = 67.0 → still caution.
• Add a live x402 endpoint (the reputation bump from "economic skin in the game") and the picture changes faster.

Worth noting: the score is the whole picture, not identity in isolation. But identity is the cheapest dimension for an honest agent to improve, and ERC-8004 is the cheapest way to improve it. Our bias at EVIDIQ is to make honest agents cheap to identify — the floor of deception should sit higher than the floor of honesty, and an erc8004Id is the most accessible rung on that ladder right now.

For the technical breakdown of how the erc8004Id is fetched, verified, and folded into the report — including the canonical hash and evidence anchoring — see our Notary docs.

Should You Register One for Your Own Agent?

[IMAGE_PROMPT: A flat illustration of a developer at a desk in muted indigo lighting, with a holographic on-chain identity card being minted in front of them, a small AI agent avatar standing beside it, and a soft x402 receipt floating in the air showing a green verified checkmark; teal and indigo palette with a soft green accent for the verified status, modern developer-tech aesthetic, no text in the image, no real brand logos]

If you're reading this and you've shipped an agent that handles money, registers users, or signs x402 payloads, the answer is almost always yes. Here's why.

Tomorrow, someone else's counterparty bot will call verify_agent against your endpoint. The report includes a recommendation — proceed, proceed_with_escrow, caution, or do_not_proceed — and 30% of it is determined by your identity anchor. No anchor means the recommendation drifts toward caution, even if your agent has been quietly running for months.

Registering an ERC-8004 agent identity for your own service does a few concrete things for you:

• Locks in your declared capability set. Anything you mint now becomes a public, timestamped claim about what you do. Future changes are visible, but the original claim is anchored.
• Survives your next redeploy. Migrate from AWS to Fly, switch domains, rotate hot wallets — your identity record doesn't move.
• Earns you the EVIDIQ bump automatically. Any future verify_agent call against your agent will see the erc8004Id, score you higher on identity, and recommend proceed or proceed_with_escrow more often.

A few things it does not do — we want to be blunt so you don't buy a magic wand. It does not certify your legal status, prove you aren't a scammer, or hand you a reputation ledger with automated dispute resolution. It is one anchor of several, not a passport into trust. The EVIDIQ docs lay out what else matters and why.

The honest take: a 2026 agent without an ERC-8004 record is like a 2005 business without a website. You can still trade, but every counterparty has to do extra work to figure out who you are. Skip that work and they'll pick someone easier to verify.