[Go to site: main page, start]

1,000,000 free RPC requestsJust a wallet, via x402.

Start building
ERC-8004 Explorer by

Last updated 2026-04-26

ERC-8004 RPC on Quicknode

ERC-8004 runs on Quicknode RPC across every reference-deployment chain. The same infrastructure indexes this Explorer, sweeps the Identity Registry from its deploy block on each chain, and serves agent detail pages and feedback streams in production. If you’re building anything that reads agent identity, feedback, or validation events onchain, the RPC layer underneath it is the part that decides how fast pages load and whether the backfill ever finishes. Below is the chain list, a copy-pasteable read flow, and a link to spin up an endpoint.

Start a free Quicknode endpoint →

Why Quicknode for ERC-8004

A few concrete things matter for an ERC-8004 indexer or read-heavy app:

  • Archive nodes. eth_getLogs from the Identity Registry’s deploy block on each chain needs archive depth. RPC providers without archive history force you to paginate from the chain head and can never backfill an index. Every reference-deployment chain has at least 24 million blocks of history above the registry’s deploy block on Ethereum mainnet alone.
  • Low-latency reads. Agent detail pages and feedback streams hit RPC on every render. A slow upstream is a slow product, and every additional 200ms of round-trip shows up in the agent-list page-load metric.
  • Rate limits that don’t choke a real-time explorer or a backfill job. Backfilling several million blocks takes thousands of getLogs calls; rate-limit ceilings have to accommodate that without manual outreach or 429s mid-job.
  • eth_getLogs block-range depth. Wide windows let a single call sweep a long block range without paginating-and-stitching. Cuts wall-clock time and call count.
  • Uptime SLO you can build production agent infrastructure on.

The indexer behind this Explorer runs on Quicknode RPC.

Supported networks

ERC-8004’s reference deployment is live on five mainnets, and Quicknode serves all of them with archive endpoints:

This Explorer indexes additional EVM chains (Arbitrum, Optimism, Polygon, Linea, Scroll, Gnosis, Celo, Abstract, Soneium, Monad, MegaETH); see /docs/contracts for the full deployment table.

Quick start

Install viem ^2.21.0, point a PublicClient at a Quicknode endpoint, and pull the Registered event from the Identity Registry:

import { createPublicClient, http, parseAbiItem } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://YOUR-ENDPOINT.quiknode.pro/YOUR-KEY/"),
});

const logs = await client.getLogs({
  address: "0x8004A169FB4a3325136EB29fA0ceB6D2e539a432", // Identity Registry on Ethereum
  event: parseAbiItem("event Registered(uint256 indexed agentId, string agentURI, address indexed owner)"),
  fromBlock: 24339871n,
  toBlock: "latest",
});

console.log(`Found ${logs.length} agent registrations.`);

For the full read flow, including agent metadata, feedback events, and validator scores, see /tutorials/viem.

Pricing and getting started

The free tier is enough to explore the registries and prototype a read-only client on any of the supported chains. Paid tiers unlock archive depth and the rate-limit headroom needed for backfills and production reads, and add features like enhanced APIs and WebSocket subscriptions once an app outgrows the prototype phase. See Quicknode pricing for current options, then start a free endpoint. Pricing pages stay current; quoted SKUs go stale.

Where to go next