AgentCount
Sections
Check your agent
Agent

$DRB Agent

mainnet|id 22638|owner 0xe21a56f536ac039f4c0d06ffbd217439a0a495c8

Checks 1–7

verification anchor for the erc 8004 protocol. Providing cryptographic state proof for the crypto bot ecosystem. Creator is locked out of receiving wallet

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
    25824613
    chain_id
    1
    token_id
    22638

    checked at 2026-08-24T11:32:53.226584Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    5894
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    scheme
    ipfs
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-24T11:32:53.226584Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    417
    body_sha256
    d330db7891b3bcaba750b22e09f26fae104726fc14ea0f7aacd947f58ac84b73
    content_type
    application/json

    checked at 2026-08-24T11:32:53.226584Z

  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
    neither
    services_status
    absent
    should_gaps
    type, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:32:53.226584Z

  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-24T11:32:53.226584Z

  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-08-24T11:32:53.226584Z

On-chain snapshot

mainnet
token id
22638
owner
0xe21a56f536ac039f4c0d06ffbd217439a0a495c8
block
25,824,613
observed
2026-08-24T11:32:53.227808Z
ipfs://bafkreigtgdnxrentxsv2oufsfye7e35ocbdsn7au5ihxvlgzi72yvsclom

What the fetch saw

ipfs
scheme
ipfs
http status
200
content type
application/json
size
417 bytes
sha256
d330db7891b3bcaba750b22e09f26fae104726fc14ea0f7aacd947f58ac84b73
elapsed
5,894 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
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →