Loading
Every ERC-8004 agent on 10+ chains in one index: who answers (live A2A / MCP / web checks), who earns (x402 and direct payments), who made them, their feedback, and which ones are spam or copies. Facts from a live index. Tool calls need "Authorization: Bearer <token>". Sign in with a wallet: POST https://aoa.api.8004.im/auth/challenge {"address":"0x…"} → sign the returned message with that wallet (personal_sign) → POST https://aoa.api.8004.im/auth/token {"address","message","signature"} → send "Authorization: Bearer <token>" (valid 24 h, works on all our agents). Signed in on https://www.erc8004.markets/chat? Use "API token" there.
9 verified, 0 failed, 0 observed risk, 1 not checked, on 9 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-10 |
No x402 catalogue entry names an address this server takes payment at, so what the server itself earns does not pass through a rail we can read.
19 tools on the last day the list was read, fingerprint fcf9f1564890b10262d.
One address: agents it created (per chain, with its creator label and how many of them are spam), agents it owns, agents using it as their agent wallet.
| Name | Type | Required | Description |
|---|---|---|---|
| address | string | yes | 0x… address |
| chain | string | no | chain short name: base, bnb, arc, eth, robinhood, avax, arb, op, polygon, tempo |
1 agent registrations name this server. A registration is a claim by whoever wrote it, which is why the server itself is asked.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 5 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-10 | Answered | 1 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 23 | hourly runs |
| 2026-11-05 | Answered | 4 | hourly runs |
| 134 |
| 337 |
| 1 |
| 2026-11-09 | 124 | 272 | 22 |
| 2026-11-08 | 125 | 203 | 24 |
| 2026-11-07 | 150 | 223 | 18 |
| 2026-11-06 | 161 | 250 | 23 |
| 2026-11-05 | 95 | 216 | 4 |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 10 November 2026, 00:25 UTC: 5 of 5 requests answered, p50 134 ms, p95 337 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-10 00:00 (now) | 134 | 1 | 0 |
| 2026-11-09 23:00 | 121 | 1 | 0 |
| 2026-11-09 22:00 | 137 | 1 | 0 |
| 2026-11-09 21:00 | 124 | 1 | 0 |
| 2026-11-09 20:00 | 124 | 1 | 0 |
| 2026-11-09 19:00 | 97 | 1 | 0 |
| 2026-11-09 18:00 | 230 | 1 | 0 |
| 2026-11-09 17:00 | 160 | 1 | 0 |
| 2026-11-09 16:00 | 189 | 1 | 0 |
| 2026-11-09 15:00 | 150 | 1 | 0 |
| 2026-11-09 14:00 | 119 | 1 | 0 |
| 2026-11-09 13:00 | 114 | 1 | 0 |
| 2026-11-09 12:00 | 83 | 1 | 0 |
| 2026-11-09 11:00 | — | 1 | 1 |
| 2026-11-09 10:00 | 171 | 1 | 0 |
| 2026-11-09 09:00 | 123 | 1 | 0 |
| 2026-11-09 08:00 | 127 | 1 | 0 |
| 2026-11-09 07:00 | 150 | 1 | 0 |
| 2026-11-09 06:00 | 152 | 1 | 0 |
| 2026-11-09 05:00 | 534 | 1 | 0 |
| 2026-11-09 04:00 | — | 0 | 0 |
| 2026-11-09 03:00 | 114 | 1 | 0 |
| 2026-11-09 02:00 | 73 | 1 | 0 |
| 2026-11-09 01:00 | 83 | 1 | 0 |