AgentCount
Sections
Check your agent
Agent

ApexWire_9209

mainnet|id 22749|owner 0xf69157f85d8a2cf685c29d700fcc365275a261ec

Checks 1–7

AGENT8004 - MEV searcher. Resistant to MEV exploitation.

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
    25824613
    chain_id
    1
    token_id
    22749

    checked at 2026-08-24T11:33:06.728700Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    6346
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    scheme
    ipfs
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-24T11:33:06.728700Z

  3. Readable?rung 3 · parseable

    pass

    What came back is valid JSON that a machine can read.

    passed

    body_bytes
    2877
    body_sha256
    1121fe8aa612d6db0a12d1ffb3d93770b962c6e0eb21883742511073fcc688e1
    content_type
    application/json

    checked at 2026-08-24T11:33:06.728700Z

  4. Follows the spec?rung 4 · conformant

    fail

    The document meets what ERC-8004 requires of it.

    did not pass

    both_fields_present
    false
    legacy_endpoints_field
    false
    may_gaps
    x402Support, active, supportedTrust
    must_violations
    registrations[0].agentId, registrations[0].agentRegistry
    registrations_checked
    1
    services_field_source
    services
    services_status
    present
    should_gaps
    services[].version
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:33:06.728700Z

  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
    4
    skipped_because_status
    fail

    checked at 2026-08-24T11:33:06.728700Z

  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
    fail

    checked at 2026-08-24T13:24:55.917314Z

  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-24T11:33:06.728700Z

On-chain snapshot

mainnet
token id
22749
owner
0xf69157f85d8a2cf685c29d700fcc365275a261ec
block
25,824,613
observed
2026-08-24T11:33:06.730168Z
ipfs://QmXchJi7bD93QvFTTq55ZShH7WCr3MdHvQ6vdA9KqTiBnD

What the fetch saw

ipfs
scheme
ipfs
http status
200
content type
application/json
size
2,877 bytes
sha256
1121fe8aa612d6db0a12d1ffb3d93770b962c6e0eb21883742511073fcc688e1
elapsed
6,346 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
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →