AgentCount
Sections
Check your agent
Agent

vitalik

mainnet|id 9394|owner 0x4baacf01a842097f1cbbe573b0c77ad7aa9fa3cc

Checks 1–7

vitalikvitalikvitalikvitalikvitalikvitalikvitalikvitalikvitalikvitalikvitalik

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
    0x4baacf01a842097f1cbbe573b0c77ad7aa9fa3cc
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    9394
    tx_hash
    0x2f4bb16d98a9b9496cd5388ff6e0f5fa6052f6791b600b76de915fe20fe22b40

    checked at 2026-08-10T10:31:32.512904Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    313
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogInZpdGFsaWsiLAogICJkZXNjcmlwdGlvbiI6ICJ2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpayIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IHRydWUKfQ==

    checked at 2026-08-10T10:31:32.512904Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    313
    body_sha256
    2840d105964efc76efee434f758df45c13b73ff3a4959f224d2eaa1384cca8e6
    content_type
    —

    checked at 2026-08-10T10:31:32.512904Z

  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-10T10:31:32.512904Z

  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:31:32.512904Z

  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-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:31:32.512904Z

On-chain snapshot

mainnet
token id
9394
owner
0x4baacf01a842097f1cbbe573b0c77ad7aa9fa3cc
block
25,723,900
observed
2026-08-10T10:31:32.515861Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogInZpdGFsaWsiLAogICJkZXNjcmlwdGlvbiI6ICJ2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpa3ZpdGFsaWt2aXRhbGlrdml0YWxpayIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IHRydWUKfQ==

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
313 bytes
sha256
2840d105964efc76efee434f758df45c13b73ff3a4959f224d2eaa1384cca8e6
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 →