Public data index › ERC-8004 endpoint liveness

ERC-8004 endpoints that never returned HTTP 200

Aggregate observations through 2026-08-09; host names, wallet owners, agent metadata, and response bodies are withheld.

232 endpoint hosts were observed on at least 15 dated probe panels and never returned HTTP 200 in those observations. An ecosystem lead at an AI-agent marketplace can request the $249/month monthly liveness report and CSV below.

Scope first. This is a sampled observation archive, not a complete registry or an uptime monitor. The newest run probed 300 hosts and omitted 414 behind the deterministic daily cap. HTTP 200 means only that the representative registered URI answered that probe with that status.

232hosts with 15+ observed dates and no HTTP 200
483hosts that returned HTTP 200 at least once
16,958sealed host-probe rows
57/60calendar dates with host probes

What sits inside the never-200 count

Of the 232 qualifying hosts, 102 returned HTTP 404 on every observed date, 81 produced no HTTP status on every observed date, and 49 produced a mix of other non-200 outcomes. Qualifying hosts were sampled on {value['min_observed_days']:,} to 40 dates, averaging 25.2.

Those buckets are transport observations, not identity, safety, activity, endorsement, or business-status judgments. A 404 may be an intentional path; a missing status may be DNS, TLS, timeout, or another transport failure.

Monthly ERC-8004 Endpoint Liveness Report

$249/month

For one ecosystem or developer-relations team at an AI-agent marketplace or protocol company: a hosted, dated report plus CSV covering the prior calendar month's sealed endpoint probes, delivered by the fifth business day. It includes status buckets, observed-date counts, chain coverage, sampling exclusions, and the monthly batch-seal references. It excludes decoded contacts, wallet owners, raw metadata, and response bodies.

  • One monthly report and CSV for the ERC-8004 registry universe we observe.
  • Coverage gaps and capped-out hosts travel with every delivery.
  • Cancel before the next monthly compilation.

Request a scoped sample →

This is a demand test. No checkout is active; the existing partner form opens a scoped request.

Coverage that constrains the result

The archive spans 60 calendar days from 2026-06-11 through 2026-08-09, with host probes on 57 dates. Missing probe dates: 2026-06-19, 2026-07-04, 2026-08-08. The newest collection reported 12 chains successful, 0 errored, and run status partial. Provider-retention gaps remained for: bsc, ethereum.

Chainsealed panel datesfirstlatest
arbitrum462026-06-112026-08-09
avalanche462026-06-112026-08-09
base462026-06-112026-08-09
bsc152026-06-112026-08-09
celo462026-06-112026-08-09
ethereum462026-06-112026-08-09
gnosis462026-06-112026-08-09
linea462026-06-112026-08-09
mantle462026-06-112026-08-09
optimism462026-06-112026-08-09
polygon562026-06-112026-08-09
scroll462026-06-112026-08-09

Method and provenance

  1. Read Registered and URIUpdated events from the ERC-8004 Identity Registry on the frozen chain universe.
  2. Count HTTPS hosts from the latest known registration URIs.
  3. Select at most 300 hosts per date with a deterministic date-seeded sample when the panel is larger.
  4. GET one representative URI per selected host and seal the status, response hash, and row hash.
  5. Publish only aggregates from rows whose content hashes still match.

A missed endpoint observation cannot be reconstructed after the observation date passes. That dated record—not a claim that the on-chain registry is scarce—is the archive's useful evidence.

Newest seal: aa2eaa5c03aa08349c861273fce108c568a2ee062c2257900319bbd7700eda5d
Collected: 2026-08-09T04:30:27.536411+00:00
Universe: chains_v1
Registry: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432

Standard: ERC-8004: Trustless Agents. Chain RPC responses and HTTP probe bodies are sealed in the private evidence store; they are not republished here.

Browse other data services · Inspect the machine-readable agent market · US Tech Automations