AgentCount
Sections
Check your agent
Agent

Agent #3

bsc|id 3|owner 0x6446ad9821021eeb9f85b8a18b0153d58166d161

Checks 1–7
Keyerrorthe check could not completefaildid not passpasspassedskippeda check this one depends on did not passunclaimedthe document made no claim to checknot checkedthis check was never askedFull definitions

The seven checks, with their evidence

6 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
    112874357
    chain_id
    56
    owner
    0x6446ad9821021eeb9f85b8a18b0153d58166d161
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    3
    tx_hash
    —

    checked at 2026-07-29T19:31:34.914139Z

  2. Reachable?rung 2 · resolvable

    error

    The document URL it declared actually answers when fetched.

    the check could not complete

    elapsed_ms
    317
    reason
    robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://www.arrondesean.us/robots.txt)
    request_url
    https://www.arrondesean.us/
    scheme
    https
    uri
    HTTPS://www.arrondesean.us

    checked at 2026-07-29T19:31:34.914139Z

  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
    error

    checked at 2026-07-29T19:31:34.914139Z

  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
    error

    checked at 2026-07-29T19:31:34.914139Z

  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
    error

    checked at 2026-07-29T19:31:34.914139Z

  6. Answers?rung 6 · —

    not checked

    A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.

    not checked — this check was never asked

    This run never reached this check for this agent.

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    1
    feedback_count
    1

    checked at 2026-07-29T19:31:34.914139Z

On-chain snapshot

bsc
token id
3
owner
0x6446ad9821021eeb9f85b8a18b0153d58166d161
block
112,874,357
observed
2026-07-29T19:31:34.914338Z
tokenURIopen →
HTTPS://www.arrondesean.us

What the fetch saw

https
scheme
https
request url
https://www.arrondesean.us/
final url
—
http status
—
content type
—
size
—
sha256
—
elapsed
317 ms
error
robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://www.arrondesean.us/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
f78c7891-e787-43f1-9748-61d5a361e9ff
chain
bsc
pinned block
112,874,357
agents
244,208
started
2026-07-29T19:31:31.986385Z
finished
2026-07-30T06:50:51.109117Z
checker
0.5.0 · 987ce24581f221a1d54a84b47a72d69100214e88-dirty
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- bsc   # at block 112874357
Download this run

f78c7891-e787-43f1-9748-61d5a361e9ff.tar.zst23.9 MB|sha256|all runs

What each check measures →