AgentCount
Sections
Agent

Agent #2418

celo|id 2418|owner 0x5111a8caca3366389eeaaad8a49027d573588bbb

Checks 1–7
Keyerrorthe check could not completefaildid not passpasspassedskippeda 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
    73985588
    chain_id
    42220
    owner
    0x5111a8caca3366389eeaaad8a49027d573588bbb
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    2418
    tx_hash
    0xa8daaa8c6f295ed05381a97610cc8a26aac4e7421be23b6b920a168c0985bfa8

    checked at 2026-08-04T23:49:25.918094Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    reason
    unsupported_scheme
    scheme
    unsupported
    uri
    asdasd

    checked at 2026-08-04T23:49:25.918094Z

  3. Readable?rung 3 · parseable

    skipped

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

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    fail

    checked at 2026-08-04T23:49:25.918094Z

  4. Follows the spec?rung 4 · conformant

    skipped

    The document meets what ERC-8004 requires of it.

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    fail

    checked at 2026-08-04T23:49:25.918094Z

  5. Claims its identity?rung 5 · bound

    skipped

    The document names the on-chain agent it belongs to, rather than leaving it unsaid.

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    fail

    checked at 2026-08-04T23:49:25.918094Z

  6. Answers?rung 6 · live

    skipped

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

    skipped — a check this one depends on did not pass

    skipped_because_rung
    4
    skipped_because_status
    skipped

    checked at 2026-08-04T23:56:38.388290Z

  7. Has feedback?rung 7 · attested

    pass

    At least one on-chain feedback entry names this agent.

    passed

    distinct_authors
    2
    feedback_count
    3

    checked at 2026-08-04T23:49:25.918094Z

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
2418
owner
0x5111a8caca3366389eeaaad8a49027d573588bbb
block
73,985,588
observed
2026-08-04T23:49:25.920044Z
tokenURI
asdasd

What the fetch saw

unsupported
scheme
unsupported
request url
—
final url
—
http status
—
content type
—
size
—
sha256
—
elapsed
—

This run

reproducible
Every status above is scoped to this sweep, at this block. Rerun it and you should get these answers back.
run
974f0c12-e3fc-48a9-ad2a-2400f284c6b1
chain
celo
pinned block
73,985,588
agents
9,758
started
2026-08-04T23:32:26.218902Z
finished
2026-08-04T23:55:46.526567Z
checker
0.6.0 · unknown
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 73985588

What each check measures →