AgentCount
Sections
Agent

Agent-5065

arbitrum|id 76|owner 0xbf0e0e7afde9b7f42f5d93d3aebde53af14bba70

Checks 1–7
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
    492986716
    chain_id
    42161
    owner
    0xbf0e0e7afde9b7f42f5d93d3aebde53af14bba70
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    76
    tx_hash
    0x08c8673ece662dde222048261a22e2da729aed24fc6dc1a6bb4cbc81121a47a4

    checked at 2026-08-10T06:07:16.354908Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    142
    data_uri_variant
    plain_json_without_uri_scheme
    inline
    true
    scheme
    data
    uri
    {"name":"Agent-5065","description":"","skills":["coding,development"],"domains":["gaming,nft"],"services":["trading,analytics"],"metadata":{}}

    checked at 2026-08-10T06:07:16.354908Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    142
    body_sha256
    5585dd14e8cb3003ad03ca17b43fdb94a90d3f68702be2e4fc6125c1fafbb314
    content_type
    —

    checked at 2026-08-10T06:07:16.354908Z

  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, active, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    services
    services_status
    present
    should_gaps
    type, image, services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T06:07:16.354908Z

  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-10T06:07:16.354908Z

  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":null,"index":0,"kind":"missing","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
    missing
    reason
    no_probeable_endpoint

    checked at 2026-08-10T06:11:49.942700Z

  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-10T06:07:16.354908Z

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

arbitrum
token id
76
owner
0xbf0e0e7afde9b7f42f5d93d3aebde53af14bba70
block
492,986,716
observed
2026-08-10T06:07:16.357056Z
tokenURI
{"name":"Agent-5065","description":"","skills":["coding,development"],"domains":["gaming,nft"],"services":["trading,analytics"],"metadata":{}}

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
142 bytes
sha256
5585dd14e8cb3003ad03ca17b43fdb94a90d3f68702be2e4fc6125c1fafbb314
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
53fbdb9f-7e31-456a-b7a4-4d7cb3e97eed
chain
arbitrum
pinned block
492,986,716
agents
1,234
started
2026-08-10T06:06:43.263270Z
finished
2026-08-10T06:11:28.514872Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- arbitrum   # at block 492986716

What each check measures →