Agent

Agent #256

megaeth|id 256|owner 0xa0dceabca876c859681401ee06c382cbe8b3f27a

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
23553624
chain_id
4326
owner
0xa0dceabca876c859681401ee06c382cbe8b3f27a
registry
0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
token_id
256
tx_hash
0x62259e3678440e1dd9f59333f875efb6ac7146901d58a5b6c2f4b9d32cbd5a1f
checked at 2026-08-10T08:36:16.991027Z
Reachable?rung 2 · resolvable
fail
The document URL it declared actually answers when fetched.
did not pass
elapsed_ms
2014
final_url
https://8004glyphs.vercel.app/api/agent/119
http_status
404
reason
http_status
request_url
https://8004glyphs.vercel.app/api/agent/119
scheme
https
uri
https://8004glyphs.vercel.app/api/agent/119
checked at 2026-08-10T08:36:16.991027Z
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-08-10T08:36:16.991027Z
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-08-10T08:36:16.991027Z
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-08-10T08:36:16.991027Z
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-08-10T09:12:31.954531Z
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-08-10T08:36:16.991027Z

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: 256
owner: 0xa0dceabca876c859681401ee06c382cbe8b3f27a
block: 23,553,624
observed: 2026-08-10T08:36:16.993563Z

tokenURIopen →

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

What the fetch saw

https

scheme: https
request url: https://8004glyphs.vercel.app/api/agent/119
final url: https://8004glyphs.vercel.app/api/agent/119
http status: 404
content type: text/plain; charset=utf-8
size: 107 bytes
sha256: 2c448ee58b24b1fca456ec16faeeb808e0605049e10373e33cf0634a915c58d0
elapsed: 2,014 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: 987a4007-5a4c-4d4a-86a1-5eb938d2b2a6
chain: megaeth
pinned block: 23,553,624
agents: 12,727
started: 2026-08-10T08:30:35.219522Z
finished: 2026-08-10T09:12:17.723967Z
checker: 0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit: 68fc6765761a10fb26f0692df21c8a6f9d12b1be

Reproduce

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

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