AgentCount
Sections
Check your agent
Agent

Agent8004

mainnet|id 22587|owner 0x953ff1d0cb56510d23af653d239e28f6db1a5d03

Checks 1–7

A testing Agent on ERC8004scan to use EIP-8004 on Ethereum mainnet.

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
    0x953ff1d0cb56510d23af653d239e28f6db1a5d03
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    22587
    tx_hash
    0x585ee1af0704370a14eb28e6eff124f112d19ede434d84ce2bb758cd28e436f7

    checked at 2026-08-24T11:32:42.075453Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    306
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIkFnZW50ODAwNCIsCiAgImRlc2NyaXB0aW9uIjogIkEgdGVzdGluZyBBZ2VudCBvbiBFUkM4MDA0c2NhbiB0byB1c2UgRUlQLTgwMDQgb24gRXRoZXJldW0gbWFpbm5ldC4iLAogICJpbWFnZSI6ICIiLAogICJzZXJ2aWNlcyI6IFtdLAogICJyZWdpc3RyYXRpb25zIjogW10sCiAgInN1cHBvcnRlZFRydXN0cyI6IFtdLAogICJhY3RpdmUiOiBmYWxzZSwKICAieDQwMnN1cHBvcnQiOiBmYWxzZQp9

    checked at 2026-08-24T11:32:42.075453Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    306
    body_sha256
    9ee5f2dc131d929892cc2d8c2bbf7ec8e6770b48a930326cfca6a2f4681d9c27
    content_type
    —

    checked at 2026-08-24T11:32:42.075453Z

  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:32:42.075453Z

  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:32:42.075453Z

  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:32:42.075453Z

On-chain snapshot

mainnet
token id
22587
owner
0x953ff1d0cb56510d23af653d239e28f6db1a5d03
block
25,824,613
observed
2026-08-24T11:32:42.076925Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIkFnZW50ODAwNCIsCiAgImRlc2NyaXB0aW9uIjogIkEgdGVzdGluZyBBZ2VudCBvbiBFUkM4MDA0c2NhbiB0byB1c2UgRUlQLTgwMDQgb24gRXRoZXJldW0gbWFpbm5ldC4iLAogICJpbWFnZSI6ICIiLAogICJzZXJ2aWNlcyI6IFtdLAogICJyZWdpc3RyYXRpb25zIjogW10sCiAgInN1cHBvcnRlZFRydXN0cyI6IFtdLAogICJhY3RpdmUiOiBmYWxzZSwKICAieDQwMnN1cHBvcnQiOiBmYWxzZQp9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
306 bytes
sha256
9ee5f2dc131d929892cc2d8c2bbf7ec8e6770b48a930326cfca6a2f4681d9c27
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 →