Agent

Agent #258

polygon|id 258|owner 0x5cdf203e9cd8753350beccadc3224c726c16ca20

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
    96596571
    chain_id
    137
    owner
    0x5cdf203e9cd8753350beccadc3224c726c16ca20
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    258
    tx_hash
    0xba229757086c6fe4d44af83ce5653192eb1bec5ff6218798c0cae9582cd0b70a

    checked at 2026-11-02T06:23:33.858206Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    elapsed_ms
    287
    http_status
    404
    reason
    http_status
    scheme
    https

    checked at 2026-11-02T06:23:33.858206Z

  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-11-02T06:23:33.858206Z

  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-11-02T06:23:33.858206Z

  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-11-02T06:23:33.858206Z

  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-11-02T06:42:48.975346Z

  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-11-02T06:23:33.858206Z

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

polygon
token id
258
owner
0x5cdf203e9cd8753350beccadc3224c726c16ca20
block
96,596,571
observed
2026-11-02T06:23:33.861833Z
tokenURIopen →
https://example.com/agents/tama

What the fetch saw

https
scheme
https
http status
404
content type
text/html; charset=utf-8
size
577 bytes
sha256
25ddf2c883e0d1958ea971d279a7e4f0fd446724ee3db7db19dadabd4a62e484
elapsed
287 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
aac00d70-16c9-4f21-a67e-d26161a64d2f
chain
polygon
pinned block
96,596,571
agents
695
started
2026-11-02T06:18:31.984888Z
finished
2026-11-02T06:40:59.096076Z
checker
0.7.0 · 9796f5f3bdd4b8bb6c6ac14a68e5fac0ca13114c
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 96596571

What each check measures →