AgentCount
Sections
Check your agent
Agent

eth2

mainnet|id 23212|owner 0xc35b3c2b523fdeef3175127853fe88c2a595cc37

Checks 1–7

AI agents are the future! AI agents are the future!

Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda 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.

  1. Registered?rung 1 · registered

    pass

    The agent exists in the on-chain registry, with an owner and a document URL.

    passed

    block_number
    25824613
    chain_id
    1
    owner
    0xc35b3c2b523fdeef3175127853fe88c2a595cc37
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    23212
    tx_hash
    0x5ed3dc1d915867afee66f6bce343fb8b2305b3cc6e44fee95f28232b2d3d935d

    checked at 2026-08-24T11:34:02.232539Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    285
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogImV0aDIiLAogICJkZXNjcmlwdGlvbiI6ICJBSSBhZ2VudHMgYXJlIHRoZSBmdXR1cmUhXG5BSSBhZ2VudHMgYXJlIHRoZSBmdXR1cmUhIiwKICAiaW1hZ2UiOiAiIiwKICAic2VydmljZXMiOiBbXSwKICAicmVnaXN0cmF0aW9ucyI6IFtdLAogICJzdXBwb3J0ZWRUcnVzdHMiOiBbXSwKICAiYWN0aXZlIjogZmFsc2UsCiAgIng0MDJzdXBwb3J0IjogdHJ1ZQp9

    checked at 2026-08-24T11:34:02.232539Z

  3. Readable?rung 3 · parseable

    pass

    What came back is valid JSON that a machine can read.

    passed

    body_bytes
    285
    body_sha256
    d8e5f2d8df2b5956deacbdd4d607dff923a47a50e8c3572d78d0e72fe3865f12
    content_type
    —

    checked at 2026-08-24T11:34:02.232539Z

  4. Follows the spec?rung 4 · conformant

    pass

    The document meets what ERC-8004 requires of it.

    passed

    both_fields_present
    false
    legacy_endpoints_field
    false
    may_gaps
    x402Support, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    services
    services_status
    empty
    should_gaps
    services_empty, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:34:02.232539Z

  5. Claims its identity?rung 5 · bound

    unclaimed

    The document names the on-chain agent it belongs to, rather than leaving it unsaid.

    unclaimed — the document made no claim to check

    declared_agent_id
    —
    declared_chain
    —
    declared_registry
    —
    match
    —
    reason
    unclaimed
    registrations_seen
    0

    checked at 2026-08-24T11:34:02.232539Z

  6. Answers?rung 6 · live

    unprobeable

    A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.

    unprobeable — no declared endpoint that a probe can reach

    endpoints
    (empty)
    endpoints_answered_not_live
    0
    endpoints_declared
    0
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    (empty)
    reason
    no_services_declared

    checked at 2026-08-24T13:24:55.917314Z

  7. 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-24T11:34:02.232539Z

On-chain snapshot

mainnet
token id
23212
owner
0xc35b3c2b523fdeef3175127853fe88c2a595cc37
block
25,824,613
observed
2026-08-24T11:34:02.234183Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogImV0aDIiLAogICJkZXNjcmlwdGlvbiI6ICJBSSBhZ2VudHMgYXJlIHRoZSBmdXR1cmUhXG5BSSBhZ2VudHMgYXJlIHRoZSBmdXR1cmUhIiwKICAiaW1hZ2UiOiAiIiwKICAic2VydmljZXMiOiBbXSwKICAicmVnaXN0cmF0aW9ucyI6IFtdLAogICJzdXBwb3J0ZWRUcnVzdHMiOiBbXSwKICAiYWN0aXZlIjogZmFsc2UsCiAgIng0MDJzdXBwb3J0IjogdHJ1ZQp9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
285 bytes
sha256
d8e5f2d8df2b5956deacbdd4d607dff923a47a50e8c3572d78d0e72fe3865f12
elapsed
0 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
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →