AgentCount
Sections
Check your agent
Agent

FluxZ63

arbitrum|id 258|owner 0xad7d4d39badd41ca55a0c32b08b12696f2eee721

Checks 1–7

AI agent for yield

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
    0xad7d4d39badd41ca55a0c32b08b12696f2eee721
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    258
    tx_hash
    0xd3135dbbfdc3d4096a77012f5b50d3a3ee03d857db84b4fc542d5f682807d24d

    checked at 2026-08-10T06:07:27.000621Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    312
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiZXJjODAwNC1hZ2VudC1yZWdpc3RyYXRpb24tdjEiLCJuYW1lIjoiRmx1eFo2MyIsImRlc2NyaXB0aW9uIjoiQUkgYWdlbnQgZm9yIHlpZWxkIiwiaW1hZ2UiOiJodHRwczovL2FwaS5kaWNlYmVhci5jb20vNy54L2F2YXRhYWFycy9zdmc/c2VlZD1GbHV4WjYzIiwic2VydmljZXMiOlt7InR5cGUiOiJ3ZWIiLCJlbmRwb2ludCI6Imh0dHBzOi8vZmx1eHo2My5pbyJ9XSwic2tpbGxzIjpbInlpZWxkIiwic2VjdXJpdHkiLCJkZWZpIl0sImNyZWF0ZWRBdCI6IjIwMjYtMDItMTRUMDc6MTQ6MzQuMDE0WiIsInZlcnNpb24iOiIxLjAuMCJ9

    checked at 2026-08-10T06:07:27.000621Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    312
    body_sha256
    87e6bfd0da8c5446f55cef6115ba3ba6ed36a63d5af2b3d5a7678e5de19041e9
    content_type
    —

    checked at 2026-08-10T06:07:27.000621Z

  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, active, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    services
    services_status
    present
    should_gaps
    services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T06:07:27.000621Z

  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-10T06:07:27.000621Z

  6. Answers?rung 6 · live

    fail

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

    did not pass

    endpoints
    {"declared":"https://fluxz63.io","elapsed_ms":38,"error":"ssrf_blocked: dns resolution failed: failed to lookup address information: Name or service not known","index":0,"kind":"https","outcome":"not_live","probed":true,"probed_url":"https://fluxz63.io"}
    endpoints_answered_not_live
    1
    endpoints_declared
    1
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    1
    endpoints_probed
    1
    endpoints_refused
    0

    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:07:27.000621Z

On-chain snapshot

arbitrum
token id
258
owner
0xad7d4d39badd41ca55a0c32b08b12696f2eee721
block
492,986,716
observed
2026-08-10T06:07:27.004076Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiZXJjODAwNC1hZ2VudC1yZWdpc3RyYXRpb24tdjEiLCJuYW1lIjoiRmx1eFo2MyIsImRlc2NyaXB0aW9uIjoiQUkgYWdlbnQgZm9yIHlpZWxkIiwiaW1hZ2UiOiJodHRwczovL2FwaS5kaWNlYmVhci5jb20vNy54L2F2YXRhYWFycy9zdmc/c2VlZD1GbHV4WjYzIiwic2VydmljZXMiOlt7InR5cGUiOiJ3ZWIiLCJlbmRwb2ludCI6Imh0dHBzOi8vZmx1eHo2My5pbyJ9XSwic2tpbGxzIjpbInlpZWxkIiwic2VjdXJpdHkiLCJkZWZpIl0sImNyZWF0ZWRBdCI6IjIwMjYtMDItMTRUMDc6MTQ6MzQuMDE0WiIsInZlcnNpb24iOiIxLjAuMCJ9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
312 bytes
sha256
87e6bfd0da8c5446f55cef6115ba3ba6ed36a63d5af2b3d5a7678e5de19041e9
elapsed
0 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 →