Agent

Agent #9448

celo|id 9448|owner 0x2ccac4c2a9b9115d5ba392c51a99954948ebc703

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
    79282391
    chain_id
    42220
    token_id
    9448

    checked at 2026-10-05T07:11:52.758871Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    elapsed_ms
    930
    http_status
    404
    reason
    http_status
    scheme
    https

    checked at 2026-10-05T07:11:52.758871Z

  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-10-05T07:11:52.758871Z

  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-10-05T07:11:52.758871Z

  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-10-05T07:11:52.758871Z

  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-10-05T07:31:54.600744Z

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    1
    feedback_count
    1

    checked at 2026-10-05T07:11:52.758871Z

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
9448
owner
0x2ccac4c2a9b9115d5ba392c51a99954948ebc703
block
79,282,391
observed
2026-10-05T07:11:52.762894Z
tokenURIopen →
https://raw.githubusercontent.com/PoulavBhowmick03/spawn-celo/proof-of-ship/docs/agents/ay-balanced-g6-i164.json

What the fetch saw

https
scheme
https
http status
404
content type
text/plain; charset=utf-8
size
14 bytes
sha256
d5558cd419c8d46bdc958064cb97f963d1ea793866414c025906ec15033512ed
elapsed
930 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
51518bd2-6305-4b27-a769-cf957aba00f4
chain
celo
pinned block
79,282,391
agents
9,878
started
2026-10-05T06:52:29.184815Z
finished
2026-10-05T07:30:46.088420Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 79282391

What each check measures →