AgentCount
Sections
Check your agent
Agent

validator.eth

mainnet|id 7154|owner 0x82eb45562f991329ed2867f43fc60f0ba52c3dab

Checks 1–7

0x82eB45562F991329ED2867F43fc60F0Ba52C3Dab validator.eth

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
    25723900
    chain_id
    1
    owner
    0x82eb45562f991329ed2867f43fc60f0ba52c3dab
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    7154
    tx_hash
    0x6910b8f91897e98d683ce258b4158b92ea10e332a3b0f3963cf7055f9b30380d

    checked at 2026-08-10T10:29:59.797703Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    278
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJ2YWxpZGF0b3IuZXRoIiwiZGVzY3JpcHRpb24iOiIgMHg4MmVCNDU1NjJGOTkxMzI5RUQyODY3RjQzZmM2MEYwQmE1MkMzRGFiIHZhbGlkYXRvci5ldGgiLCJpbWFnZSI6IiIsImVuZHBvaW50cyI6W3sibmFtZSI6ImVucyIsImVuZHBvaW50IjoidmFsaWRhdG9yLmV0aCIsInZlcnNpb24iOiIxIn1dLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0IjpmYWxzZX0=

    checked at 2026-08-10T10:29:59.797703Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    278
    body_sha256
    8a2449c66febe995833ad63d4dc250d68b68ffc73c6d06b1d08a03d8fb8fee43
    content_type
    —

    checked at 2026-08-10T10:29:59.797703Z

  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
    true
    may_gaps
    supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    endpoints
    services_status
    present
    should_gaps
    registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T10:29:59.797703Z

  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-10T10:29:59.797703Z

  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
    {"declared":"validator.eth","index":0,"kind":"other","name":"ens","probed":false}
    endpoints_answered_not_live
    0
    endpoints_declared
    1
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    other
    reason
    no_probeable_endpoint

    checked at 2026-08-10T11:57:37.277100Z

  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-10T10:29:59.797703Z

On-chain snapshot

mainnet
token id
7154
owner
0x82eb45562f991329ed2867f43fc60f0ba52c3dab
block
25,723,900
observed
2026-08-10T10:29:59.799762Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJ2YWxpZGF0b3IuZXRoIiwiZGVzY3JpcHRpb24iOiIgMHg4MmVCNDU1NjJGOTkxMzI5RUQyODY3RjQzZmM2MEYwQmE1MkMzRGFiIHZhbGlkYXRvci5ldGgiLCJpbWFnZSI6IiIsImVuZHBvaW50cyI6W3sibmFtZSI6ImVucyIsImVuZHBvaW50IjoidmFsaWRhdG9yLmV0aCIsInZlcnNpb24iOiIxIn1dLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0IjpmYWxzZX0=

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
278 bytes
sha256
8a2449c66febe995833ad63d4dc250d68b68ffc73c6d06b1d08a03d8fb8fee43
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
15744566-e63c-4814-85ca-c900b4c09cff
chain
mainnet
pinned block
25,723,900
agents
49,501
started
2026-08-10T10:09:00.141614Z
finished
2026-08-10T11:31:56.201501Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25723900

What each check measures →