Agent

Agent #3261

celo|id 3261|owner 0xa2e5d703aeb869e7a165e39bd82463ae6cf10772

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
    78737641
    chain_id
    42220
    token_id
    3261

    checked at 2026-09-29T00:27:39.276296Z

  2. Reachable?rung 2 · resolvable

    refused

    The document URL it declared actually answers when fetched.

    refused

    elapsed_ms
    581
    reason
    robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://lookout.watch/robots.txt)
    scheme
    https

    checked at 2026-09-29T00:27:39.276296Z

  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-09-29T00:27:39.276296Z

  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-09-29T00:27:39.276296Z

  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-09-29T00:27:39.276296Z

  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-09-29T01:57:06.617409Z

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    2
    feedback_count
    9

    checked at 2026-09-29T00:27:39.276296Z

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
3261
owner
0xa2e5d703aeb869e7a165e39bd82463ae6cf10772
block
78,737,641
observed
2026-09-29T00:27:39.278825Z
tokenURIopen →
https://lookout.watch/agent.json

What the fetch saw

https
scheme
https
final url
—
http status
—
content type
—
size
—
sha256
—
elapsed
581 ms
error
robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://lookout.watch/robots.txt)

This run

reproducible
Every status above is scoped to this sweep, at this block. Rerun it and you should get these answers back.
run
3752198e-4291-48c5-a8af-77f6f44f2835
chain
celo
pinned block
78,737,641
agents
9,871
started
2026-09-28T23:33:19.834771Z
finished
2026-09-29T01:55:39.879591Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 78737641

What each check measures →