AgentCount
Sections
Agent

Agent #2395

base|id 2395|owner 0x8c496cce836cd2dccea3f2b84dd968284cc7d170

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
    49543773
    chain_id
    8453
    owner
    0x8c496cce836cd2dccea3f2b84dd968284cc7d170
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    2395
    tx_hash
    0xa8ee18af7a4ab3a6ec1f20b251edb42d69767e0fabf86ae01182cf9681be17f9

    checked at 2026-08-04T21:09:50.279680Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    reason
    unsupported_scheme
    scheme
    unsupported
    uri
    NoameAgent2538

    checked at 2026-08-04T21:09:50.279680Z

  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-08-04T21:09:50.279680Z

  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-08-04T21:09:50.279680Z

  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-08-04T21:09:50.279680Z

  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-04T22:54:41.930268Z

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    1
    feedback_count
    2

    checked at 2026-08-04T21:09:50.279680Z

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

base
token id
2395
owner
0x8c496cce836cd2dccea3f2b84dd968284cc7d170
block
49,543,773
observed
2026-08-04T21:09:50.281507Z
tokenURI
NoameAgent2538

What the fetch saw

unsupported
scheme
unsupported
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
24959257-5d0b-4aa6-9730-6d9987fa4c37
chain
base
pinned block
49,543,773
agents
60,589
started
2026-08-04T20:54:54.140122Z
finished
2026-08-04T22:45:30.597503Z
checker
0.6.0 · unknown
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- base   # at block 49543773

What each check measures →