AgentCount
Sections
Check your agent
Agent

Network Effects — Agent Router

mainnet|id 28398|owner 0xa9d80d27923c437deaa1051e1f594e2ddbe4bc91

Checks 1–7

Intelligent agent routing service. Selects the best agent for each request based on reputation scores, health status, latency history, and configurable routing policies. Supports proxy mode for transparent request forwarding.

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

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
    25824613
    chain_id
    1
    owner
    0xa9d80d27923c437deaa1051e1f594e2ddbe4bc91
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    28398
    tx_hash
    0x0f55d91af7d0a716f28a726fd44faae822e24787221d14492763bcbf969626fe

    checked at 2026-08-24T11:37:47.865253Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    2025
    final_url
    https://ipfs.io/ipfs/bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    request_url
    https://ipfs.io/ipfs/bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4
    scheme
    ipfs
    uri
    ipfs://bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-24T11:37:47.865253Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    1700
    body_sha256
    75adcc94bbfe01f36b5b0fc9cc1d02b852ef9e6576118bfe59d108121701cfcf
    content_type
    application/json

    checked at 2026-08-24T11:37:47.865253Z

  4. Follows the spec?rung 4 · conformant

    pass

    The document meets what ERC-8004 requires of it.

    passed

    both_fields_present
    false
    legacy_endpoints_field
    false
    may_gaps
    x402Support, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    neither
    services_status
    absent
    should_gaps
    image, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:37:47.865253Z

  5. Claims its identity?rung 5 · bound

    unclaimed

    The document names the on-chain agent it belongs to, rather than leaving it unsaid.

    unclaimed — the document made no claim to check

    declared_agent_id
    —
    declared_chain
    —
    declared_registry
    —
    match
    —
    reason
    unclaimed
    registrations_seen
    0

    checked at 2026-08-24T11:37:47.865253Z

  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

    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:37:47.865253Z

On-chain snapshot

mainnet
token id
28398
owner
0xa9d80d27923c437deaa1051e1f594e2ddbe4bc91
block
25,824,613
observed
2026-08-24T11:37:47.867227Z
tokenURIopen via ipfs.io →
ipfs://bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4

What the fetch saw

ipfs
scheme
ipfs
request url
https://ipfs.io/ipfs/bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4
final url
https://ipfs.io/ipfs/bafkreidvvxgjjo76ahzwwwypzhgb2avyklxz4zlwcgf74worbajboaopz4
http status
200
content type
application/json
size
1,700 bytes
sha256
75adcc94bbfe01f36b5b0fc9cc1d02b852ef9e6576118bfe59d108121701cfcf
elapsed
2,025 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 →