AgentCount
Sections
Check your agent
Agent

Agent #1202

arbitrum|id 1202|owner 0x000000004d79c295b258bdcd584b33be905da067

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
    492986716
    chain_id
    42161
    owner
    0x000000004d79c295b258bdcd584b33be905da067
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    1202
    tx_hash
    0xdd025cbe10cf5e8906493acf35626e1a6cfe5ac4ef858aea027a8f485fc69e74

    checked at 2026-08-10T06:11:23.576678Z

  2. Reachable?rung 2 · resolvable

    fail

    The document URL it declared actually answers when fetched.

    did not pass

    elapsed_ms
    518
    http_status
    404
    reason
    http_status
    scheme
    https

    checked at 2026-08-10T06:11:23.576678Z

  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-10T06:11:23.576678Z

  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-10T06:11:23.576678Z

  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-10T06:11:23.576678Z

  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-10T06:11:49.942700Z

  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-08-10T06:11:23.576678Z

On-chain snapshot

arbitrum
token id
1202
owner
0x000000004d79c295b258bdcd584b33be905da067
block
492,986,716
observed
2026-08-10T06:11:23.579483Z
tokenURIopen
https://github.com/mrheyday/mev-arbitrum

What the fetch saw

https
scheme
https
http status
404
content type
text/html; charset=utf-8
size
301,431 bytes
sha256
73d6647afe243625095d3ac1f27d5e3f3d5773f68173c0759ed5cbdd42e0e291
elapsed
518 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
53fbdb9f-7e31-456a-b7a4-4d7cb3e97eed
chain
arbitrum
pinned block
492,986,716
agents
1,234
started
2026-08-10T06:06:43.263270Z
finished
2026-08-10T06:11:28.514872Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- arbitrum   # at block 492986716

What each check measures →