Sections
Agent

Agent #9185

celo|id 9185|owner 0x207d064161cd85351be21eca570807ed8bcee0ad

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
    74443315
    chain_id
    42220
    token_id
    9185

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

  2. Reachable?rung 2 · resolvable

    refused

    The document URL it declared actually answers when fetched.

    refused

    elapsed_ms
    210
    http_status
    402
    reason
    payment_required
    scheme
    https

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

  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
    refused

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

  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
    refused

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

  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
    refused

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

  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-10T07:07:52.226139Z

  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:50.989198Z

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
9185
owner
0x207d064161cd85351be21eca570807ed8bcee0ad
block
74,443,315
observed
2026-08-10T07:04:50.993115Z
tokenURIopen
https://minipay-bot.vercel.app/.well-known/agent.json

What the fetch saw

https
scheme
https
http status
402
content type
text/plain; charset=utf-8
size
78 bytes
sha256
10325d4417ed16905d5dfa2d2debb3c78bb72a3bba75c14050cd37227dc37204
elapsed
210 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 →