Agent

Agent #564

megaeth|id 564|owner 0xec216da24058d16ad38425a2a0d5185423dae1b9

Checks 1–7

Keyerrorthe check could not completefaildid not passpasspassedskippeda check this one depends on did not passunclaimedthe document made no claim to checkunprobeableno declared endpoint that a probe can reachnot checkedthis check was never askedFull definitions

The seven checks, with their evidence

7 recorded

Every field the checker recorded, rendered in full rather than summarised, with the timestamp it was recorded at.

Registered?rung 1 · registered
pass
The agent exists in the on-chain registry, with an owner and a document URL.
passed
block_number
27252352
chain_id
4326
owner
0xec216da24058d16ad38425a2a0d5185423dae1b9
registry
0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
token_id
564
tx_hash
0xdc27c0a7537fb2c99d82ae5aa44fa44a9de02ec3a18cd69d8b85b022a979ac1d
checked at 2026-09-22T04:03:36.304562Z
Reachable?rung 2 · resolvable
fail
The document URL it declared actually answers when fetched.
did not pass
elapsed_ms
1012
final_url
https://8004glyphs.vercel.app/api/agent/425
http_status
404
reason
http_status
request_url
https://8004glyphs.vercel.app/api/agent/425
scheme
https
uri
https://8004glyphs.vercel.app/api/agent/425
checked at 2026-09-22T04:03:36.304562Z
Readable?rung 3 · parseable
skipped
What came back is valid JSON that a machine can read.
skipped — a check this one depends on did not pass
skipped_because_rung
2
skipped_because_status
fail
checked at 2026-09-22T04:03:36.304562Z
Follows the spec?rung 4 · conformant
skipped
The document meets what ERC-8004 requires of it.
skipped — a check this one depends on did not pass
skipped_because_rung
2
skipped_because_status
fail
checked at 2026-09-22T04:03:36.304562Z
Claims its identity?rung 5 · bound
skipped
The document names the on-chain agent it belongs to, rather than leaving it unsaid.
skipped — a check this one depends on did not pass
skipped_because_rung
2
skipped_because_status
fail
checked at 2026-09-22T04:03:36.304562Z
Answers?rung 6 · live
skipped
A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.
skipped — a check this one depends on did not pass
skipped_because_rung
4
skipped_because_status
skipped
checked at 2026-09-22T04:40:34.292947Z
Has feedback?rung 7 · attested
fail
At least one on-chain feedback entry names this agent.
did not pass
distinct_authors
0
feedback_count
0
reason
no_feedback
checked at 2026-09-22T04:03:36.304562Z

Check it again, now

outside the census

Everything above is one sweep, pinned to one block. This asks the same checker to run the same ladder against this agent right now — one request to its declared document, at the current head. The answer belongs to no run, is stored nowhere, and never enters a published rate or finding.

On-chain snapshot

megaeth

token id: 564
owner: 0xec216da24058d16ad38425a2a0d5185423dae1b9
block: 27,252,352
observed: 2026-09-22T04:03:36.307207Z

tokenURIopen →

https://8004glyphs.vercel.app/api/agent/425

What the fetch saw

https

scheme: https
request url: https://8004glyphs.vercel.app/api/agent/425
final url: https://8004glyphs.vercel.app/api/agent/425
http status: 404
content type: text/plain; charset=utf-8
size: 107 bytes
sha256: 0756620ecdf981c2db440f070821f0d51dbc076b5dc404d152556739c4d9225c
elapsed: 1,012 ms

This run

reproducible

Every status above is scoped to this sweep, at this block. Rerun it and you should get these answers back.

run: 8ce892f5-80b9-42b5-a7b8-1366889e4ac9
chain: megaeth
pinned block: 27,252,352
agents: 12,727
started: 2026-09-22T03:56:03.290497Z
finished: 2026-09-22T04:40:21.575416Z
checker: 0.7.0 · f60139c8802140544532ad9241c5d7a943939769
spec commit: 68fc6765761a10fb26f0692df21c8a6f9d12b1be

Reproduce

cargo run -p sweeper -- megaeth   # at block 27252352

What each check measures →

The seven checks, with their evidence

Registered?rung 1 · registered

Reachable?rung 2 · resolvable

Readable?rung 3 · parseable

Follows the spec?rung 4 · conformant

Claims its identity?rung 5 · bound

Answers?rung 6 · live

Has feedback?rung 7 · attested

Check it again, now

On-chain snapshot

What the fetch saw

This run