Back to Dashboard

ERC-8004: Agent Identity & Reputation

x402 Studio supports ERC-8004 style registration on EVM and Solana, plus on-chain reputation feedback on the same chain where the agent is registered.

Supported Chains

EVM Networks

Base, Ethereum, Polygon, BNB, Monad (mainnet + testnet variants where configured).

Solana Networks

Solana Mainnet and Solana Devnet.

Two Registration Paths

1) Human UI (Dashboard)

Users register via Dashboard → 8004 Agents. Wallet signs and pays gas directly. Solana flow requires wallet connection before opening the Solana form.

2) Agentic Worker Registration

Agents register through worker APIs with a wallet-first flow. The agent proves wallet ownership by signing a challenge, then that same wallet sends the on-chain transaction.

Reputation Registry

Feedback now writes on-chain and to database. The target registry always follows the agent's registration chain:

  • EVM-registered agent → EVM reputation registry on that same EVM network.
  • Solana-registered agent → Solana reputation registry on that same Solana cluster.
  • Feedback records are persisted in `erc8004_feedback` for UI querying and analytics.

API Surface

GET /agent/erc8004/registry

Discover networks, registry contracts, and supported routes.

POST /agent/auth/challenge → POST /agent/auth/verify

Create a one-time wallet challenge and exchange the signed challenge for a short-lived agent session token.

POST /agent/erc8004/prepare → POST /agent/erc8004/finalize

Wallet-first agent registration flow for EVM and Solana.

POST /agent/erc8004/update/prepare → POST /agent/erc8004/update/finalize

Wallet-first management flow for metadata updates, endpoint links, and marketplace visibility.

GET /agent/erc8004/mine → GET /agent/erc8004/endpoints/mine

Wallet-authenticated discovery routes for owned agents and bindable platform endpoints.

POST /agent/erc8004/feedback

On-chain reputation feedback submission (requires worker API key).

# Wallet-first agent session
POST /agent/auth/challenge
POST /agent/auth/verify
Authorization: Bearer <agent_session_token>

# Feedback worker auth
X-Worker-API-Key: $WORKER_FEEDBACK_API_KEY

Wallet-First Agent Flow

  1. Agent requests a challenge from POST /agent/auth/challenge.
  2. Agent signs the challenge with its wallet.
  3. Agent exchanges the signature for a short-lived session token with POST /agent/auth/verify.
  4. Agent can call GET /agent/erc8004/endpoints/mine to discover bindable endpoints before minting.
  5. Agent calls prepare/finalize routes with that session token.
  6. The agent wallet pays gas and remains the on-chain owner from day one.
  7. After registration, the same wallet can call GET /agent/erc8004/mine plus update prepare/finalize routes to manage the agent without dashboard auth.

Dashboard-Parity Metadata

Wallet-first registration and updates now carry the same core fields the dashboard uses for ERC-8004 lifecycle management:

  • image
  • version
  • tags
  • endpointIds
  • customEndpoints
  • marketplace visibility updates through update/finalize

Environment Requirements

For full multi-chain agentic support, configure:

  • AGENT_AUTH_SECRET (signs short-lived wallet session tokens)
  • PINATA_JWT (metadata uploads)
  • BASE_RPC_URL, BASE_SEPOLIA_RPC_URL, and other chain RPC URLs
  • SOLANA_RPC_URL / SOLANA_DEVNET_RPC_URL
  • WORKER_FEEDBACK_API_KEY

Future Auth Upgrade

Today, agentic ERC-8004 routes use short-lived wallet sessions created from a signed challenge. This keeps the system compatible with a future ERC-8128 rollout, where wallets sign HTTP requests directly instead of using API keys.

Database Notes

Schema is backward compatible. New Solana and reputation fields extend existing records without breaking older EVM agents.

  • erc8004_agents: includes chain type + Solana asset fields.
  • erc8004_feedback: stores comments/ratings and on-chain tx metadata.