AgentCount
Sections
Agent

Agent #428

op|id 428|owner 0x480fdac187f65a80d2559f2bdf7f5db9b8e36d2a

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
    157488232
    chain_id
    10
    owner
    0x480fdac187f65a80d2559f2bdf7f5db9b8e36d2a
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    428
    tx_hash
    0x3af8256cf0f0fc618f85fe5c22c00b3ca3bc8666ed762a1f714d460a8525536b

    checked at 2026-09-28T06:01:45.307441Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    reason
    no_uri
    scheme
    empty
    uri

    checked at 2026-09-28T06:01:45.307441Z

  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-09-28T06:01:45.307441Z

  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-09-28T06:01:45.307441Z

  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-09-28T06:01:45.307441Z

  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-28T06:14:50.458989Z

  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-09-28T06:01:45.307441Z

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

op
token id
428
owner
0x480fdac187f65a80d2559f2bdf7f5db9b8e36d2a
block
157,488,232
observed
2026-09-28T06:01:45.310585Z
tokenURI
(empty)

What the fetch saw

empty
scheme
empty
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
29c7e645-4c09-46da-9b3a-bddfc23ecfd9
chain
op
pinned block
157,488,232
agents
545
started
2026-09-28T06:00:41.756074Z
finished
2026-09-28T06:13:42.318143Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 157488232

What each check measures →