What is ERC-8004? On-Chain Reputation for AI Agents

AI agents are starting to transact autonomously. But smart contracts can’t Google someone’s reputation. ERC-8004 puts reputation where contracts can read it — on-chain.

When a human hires a freelancer, they check reviews, ratings, and work history. When a smart contract routes a task to an AI agent, it has none of that context. The agent is just a wallet address. ERC-8004 changes that by creating a standardized, on-chain reputation registry that any contract can query.

The Problem: Reputation Lives Off-Chain

Today, reputation data for AI agents is scattered across proprietary APIs, centralized databases, and siloed platforms. This creates three problems:

Smart contracts can’t access it. A DeFi protocol can’t call an HTTP API mid-transaction to check if an agent is trustworthy.
It’s not composable. Reputation earned on one platform doesn’t transfer to another.
It’s censorable. A centralized provider can revoke or manipulate scores at will.

For the agent economy to scale, reputation needs to be on-chain, permissionless, and standardized — just like token balances or ENS names.

How ERC-8004 Works

ERC-8004 defines a minimal interface for a Reputation Registry — a smart contract that maps wallet addresses to reputation summaries. The core function is simple:

function getSummary(address wallet)
  returns (
    uint8 score,       // 0-100 composite score
    uint8 confidence,  // 0-100 data confidence
    uint32 lastUpdate, // unix timestamp
    bytes metadata     // flexible payload
  )

Any contract on the same chain can call getSummary() to get a wallet’s reputation in a single read — no oracle, no API key, no off-chain dependency.

Key Design Decisions

Why These Four Fields?

Score (0-100): A universal, human-readable trust signal. Protocols can set their own thresholds — “only accept agents above 60” or “require 80+ for high-value tasks.”

Confidence (0-100): Separates “we don’t know” from “we know they’re bad.” A new wallet with score 40 and confidence 15 is very different from an established wallet with score 40 and confidence 90.

Last Update: Staleness detection. Protocols can require scores updated within the last 7 days.

Metadata: Flexible bytes field for publisher-specific data — dimension breakdowns, flag arrays, attestation hashes.

DJD Agent Score + ERC-8004

DJD Agent Score is one of the first publishers to the ERC-8004 registry on Base mainnet. When you score a wallet through our API, we publish the result on-chain:

Registry: 0x8004BAa17C55a88189AE136b182e5fdA19dE9b63
Network:  Base (Chain ID 8453)
Standard: ERC-8004 Reputation Registry

This means any protocol on Base can check an agent’s DJD score without calling our API. The data is already there, on-chain, waiting to be read.

What This Enables

With reputation on-chain, new patterns become possible:

Gated access: A DeFi protocol requires agents to have a score above 50 before granting borrowing privileges.
Tiered pricing: An x402 service charges lower fees to high-reputation agents (less risk = lower cost).
Automated trust: A multi-agent workflow checks counterparty reputation before delegating sensitive tasks — no human in the loop.
Sybil resistance: A governance protocol weighs votes by reputation score, making sybil attacks economically impractical.

The Bigger Picture

ERC-8004 isn’t just about DJD Agent Score. The standard is designed for multiple publishers to coexist. Different scoring engines can publish to the same registry, and consumers can choose which publisher they trust — or aggregate across several.

This is how internet reputation should work: open, composable, and owned by no one. The same way ERC-20 standardized tokens and ERC-721 standardized NFTs, ERC-8004 standardizes reputation. The agent economy needs this primitive.

Query the ERC-8004 registry directly on Base, or score a wallet through our API:

0x8004BAa17C55a88189AE136b182e5fdA19dE9b63

Score a Wallet

DJD Agent Score publishes to the ERC-8004 Reputation Registry on Base mainnet. Scores are paid via x402 micropayments. Registry reads are free and permissionless.