AgentCount
Sections
Agent

whale

mainnet|id 13638|owner 0xac7b1766ec12824a69207b3eff9104071000a661

Checks 1–7

A common application of AI agents is the automation of tasks

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

6 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
    26125718
    chain_id
    1
    owner
    0xac7b1766ec12824a69207b3eff9104071000a661
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    13638
    tx_hash
    0x719466356ba3481b717c8c815b96a7fce3e66d6a2473b528b70c20bfef735eb6

    checked at 2026-10-05T11:14:51.725174Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    202
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (301 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJ3aGFsZSIsImRlc2NyaXB0aW9uIjoiQSBjb21tb24gYXBwbGljYXRpb24gb2YgQUkgYWdlbnRzIGlzIHRoZSBhdXRvbWF0aW9uIG9mIHRhc2tzIiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlfQ==

    checked at 2026-10-05T11:14:51.725174Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    202
    body_sha256
    cb4c79a76a4d0349c2747de0045052352f6e80d81a087bcaa1aed8730333cf4a
    content_type
    —

    checked at 2026-10-05T11:14:51.725174Z

  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
    supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    neither
    services_status
    absent
    should_gaps
    services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-10-05T11:14:51.725174Z

  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-10-05T11:14:51.725174Z

  6. Answers?rung 6 · —

    not checked

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

    not checked — this check was never asked

    This run never reached this check for this agent.

  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-10-05T11:14:51.725174Z

Check it again, now

outside the census
Everything above is one sweep, pinned to one block. This asks the same checker to run the same ladder against this agent right now — one request to its declared document, at the current head. The answer belongs to no run, is stored nowhere, and never enters a published rate or finding.
Sends one request to the agent’s own server. Rate limited.

On-chain snapshot

mainnet
token id
13638
owner
0xac7b1766ec12824a69207b3eff9104071000a661
block
26,125,718
observed
2026-10-05T11:14:51.728677Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJ3aGFsZSIsImRlc2NyaXB0aW9uIjoiQSBjb21tb24gYXBwbGljYXRpb24gb2YgQUkgYWdlbnRzIGlzIHRoZSBhdXRvbWF0aW9uIG9mIHRhc2tzIiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlfQ==

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
202 bytes
sha256
cb4c79a76a4d0349c2747de0045052352f6e80d81a087bcaa1aed8730333cf4a
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
67b76d5d-476f-4d7a-80e1-3580feac5a40
chain
mainnet
pinned block
26,125,718
agents
52,139
started
2026-10-05T10:57:44.538042Z
finished
2026-10-05T14:22:43.904654Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 26125718

What each check measures →