AgentCount
Sections
Agent

x402 payment

celo|id 9204|owner 0xb3704310e72538342b0cb28ee41d62e77d64f7be

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

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
    74443315
    chain_id
    42220
    owner
    0xb3704310e72538342b0cb28ee41d62e77d64f7be
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    9204
    tx_hash
    0xc32906320a2c3321ba9ae77e6edd3e6fb93672519755c6347d1ac6a3afdabed0

    checked at 2026-08-10T07:04:51.675454Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    237
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJhZGRyZXNzZXMiOlt7ImFkZHJlc3MiOiIweDQyMTE2ZThCNDI5OEEwMTk2NjAxZTkzMjdCNDhGMjllNmI5QjZGMDA… (345 chars — expand)data:application/json;base64,eyJhZGRyZXNzZXMiOlt7ImFkZHJlc3MiOiIweDQyMTE2ZThCNDI5OEEwMTk2NjAxZTkzMjdCNDhGMjllNmI5QjZGMDAiLCJjYWlwMklkIjoiZWlwMTU1OjQyMjIwIiwiY2hhaW4iOiJDZWxvIn1dLCJjYXBhYmlsaXRpZXMiOlsieDQwMi1wYXltZW50Il0sIm5hbWUiOiJ4NDAyIHBheW1lbnQiLCJvd25lciI6IjB4YjM3MDQzMTBlNzI1MzgzNDJiMGNiMjhlZTQxZDYyZTc3ZDY0ZjdiZSIsInZlcnNpb24iOiIxLjAuMCJ9

    checked at 2026-08-10T07:04:51.675454Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    237
    body_sha256
    4ebed90eff09eab41af4f85ffee1624665f6be57290db5421e117024d179a195
    content_type
    —

    checked at 2026-08-10T07:04:51.675454Z

  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, description, image, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T07:04:51.675454Z

  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-10T07:04:51.675454Z

  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-10T07:04:51.675454Z

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

celo
token id
9204
owner
0xb3704310e72538342b0cb28ee41d62e77d64f7be
block
74,443,315
observed
2026-08-10T07:04:51.678842Z
tokenURI
data:application/json;base64,eyJhZGRyZXNzZXMiOlt7ImFkZHJlc3MiOiIweDQyMTE2ZThCNDI5OEEwMTk2NjAxZTkzMjdCNDhGMjllNmI5QjZGMDAiLCJjYWlwMklkIjoiZWlwMTU1OjQyMjIwIiwiY2hhaW4iOiJDZWxvIn1dLCJjYXBhYmlsaXRpZXMiOlsieDQwMi1wYXltZW50Il0sIm5hbWUiOiJ4NDAyIHBheW1lbnQiLCJvd25lciI6IjB4YjM3MDQzMTBlNzI1MzgzNDJiMGNiMjhlZTQxZDYyZTc3ZDY0ZjdiZSIsInZlcnNpb24iOiIxLjAuMCJ9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
237 bytes
sha256
4ebed90eff09eab41af4f85ffee1624665f6be57290db5421e117024d179a195
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
4131a5a1-0461-46ce-b393-bcd825d2113b
chain
celo
pinned block
74,443,315
agents
9,765
started
2026-08-10T06:41:13.909696Z
finished
2026-08-10T07:06:42.747601Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 74443315

What each check measures →