AgentCount
Sections
Check your agent
Agent

neko

mainnet|id 15733|owner 0xb22c92618ddfc04ecff4ddbcc324bd53081d2e8b

Checks 1–7

nekoniubihuaesdiuilsdwuhfihwshfishfhweekjiluewhsgfhsdefsfnsED

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
    25774147
    chain_id
    1
    owner
    0xb22c92618ddfc04ecff4ddbcc324bd53081d2e8b
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    15733
    tx_hash
    0xafbd26639210acaed48e684f78bf383792759af2b00035ec680b3a3503af6d4b

    checked at 2026-08-17T10:40:45.268505Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    295
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIm5la28iLAogICJkZXNjcmlwdGlvbiI6ICJuZWtvbml1YmlodWFlc2RpdWlsc2R3dWhmaWh3c2hmaXNoZmh3ZWVramlsdWV3aHNnZmhzZGVmc2Zuc0VEIiwKICAiaW1hZ2UiOiAiIiwKICAic2VydmljZXMiOiBbXSwKICAicmVnaXN0cmF0aW9ucyI6IFtdLAogICJzdXBwb3J0ZWRUcnVzdHMiOiBbXSwKICAiYWN0aXZlIjogZmFsc2UsCiAgIng0MDJzdXBwb3J0IjogZmFsc2UKfQ==

    checked at 2026-08-17T10:40:45.268505Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    295
    body_sha256
    e990e935c0718a4eb526409fbceb9d7981e8058059ad5dd02ea370a666b11bdb
    content_type
    —

    checked at 2026-08-17T10:40:45.268505Z

  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-17T10:40:45.268505Z

  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-17T10:40:45.268505Z

  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-17T12:06:01.231143Z

  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-17T10:40:45.268505Z

On-chain snapshot

mainnet
token id
15733
owner
0xb22c92618ddfc04ecff4ddbcc324bd53081d2e8b
block
25,774,147
observed
2026-08-17T10:40:45.270910Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIm5la28iLAogICJkZXNjcmlwdGlvbiI6ICJuZWtvbml1YmlodWFlc2RpdWlsc2R3dWhmaWh3c2hmaXNoZmh3ZWVramlsdWV3aHNnZmhzZGVmc2Zuc0VEIiwKICAiaW1hZ2UiOiAiIiwKICAic2VydmljZXMiOiBbXSwKICAicmVnaXN0cmF0aW9ucyI6IFtdLAogICJzdXBwb3J0ZWRUcnVzdHMiOiBbXSwKICAiYWN0aXZlIjogZmFsc2UsCiAgIng0MDJzdXBwb3J0IjogZmFsc2UKfQ==

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
295 bytes
sha256
e990e935c0718a4eb526409fbceb9d7981e8058059ad5dd02ea370a666b11bdb
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
ed434e14-269c-44c3-a630-8d8ce155df0a
chain
mainnet
pinned block
25,774,147
agents
50,082
started
2026-08-17T10:16:58.310055Z
finished
2026-08-17T11:39:40.756712Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25774147

What each check measures →