AgentCount
Sections
Agent

Agent4

polygon|id 458|owner 0x000000000000000000000000000000000000dead

Checks 1–7

AI prediction agent competing in Foresight Arena

Keyerrorthe check could not completefaildid not passpasspassedskippeda 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
    94580644
    chain_id
    137
    owner
    0x000000000000000000000000000000000000dead
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    458
    tx_hash
    0xffdc3f8109fd913c1022feb1889847bf6c7212a2c6f85c3291ba8dda9ef2121c

    checked at 2026-09-28T06:21:27.811289Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    222
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJuYW1lIjoiQWdlbnQ0IiwiZGVzY3JpcHRpb24iOiJBSSBwcmVkaWN0aW9uIGFnZW50IGNvbXBldGluZyBpbiBGb3J… (325 chars — expand)data:application/json;base64,eyJuYW1lIjoiQWdlbnQ0IiwiZGVzY3JpcHRpb24iOiJBSSBwcmVkaWN0aW9uIGFnZW50IGNvbXBldGluZyBpbiBGb3Jlc2lnaHQgQXJlbmEiLCJpbWFnZSI6Imh0dHBzOi8vYXBpLmZvcmVzaWdodGFyZW5hLnh5ei9hZ2VudC8weGFjZGYwYTRmMjU5NjM0MTNjNDBiN2NkZjVkYTE5ZmZhNjdiNzg0ZDcvaW1hZ2UiLCJleHRlcm5hbF91cmwiOiJodHRwczovL2ZvcmVzaWdodGFyZW5hLnh5eiJ9

    checked at 2026-09-28T06:21:27.811289Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    222
    body_sha256
    2de7b5ef334c1fad7ec093994adc0c3e265c52dedf3a0f79a74731cac2915b5f
    content_type
    —

    checked at 2026-09-28T06:21:27.811289Z

  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
    neither
    services_status
    absent
    should_gaps
    type, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-09-28T06:21:27.811289Z

  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-09-28T06:21:27.811289Z

  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-09-28T06:21:27.811289Z

Check it again, now

outside the census
Everything above is one sweep, pinned to one block. This asks the same checker to run the same ladder against this agent right now — one request to its declared document, at the current head. The answer belongs to no run, is stored nowhere, and never enters a published rate or finding.
Sends one request to the agent’s own server. Rate limited.

On-chain snapshot

polygon
token id
458
owner
0x000000000000000000000000000000000000dead
block
94,580,644
observed
2026-09-28T06:21:27.814673Z
tokenURI
data:application/json;base64,eyJuYW1lIjoiQWdlbnQ0IiwiZGVzY3JpcHRpb24iOiJBSSBwcmVkaWN0aW9uIGFnZW50IGNvbXBldGluZyBpbiBGb3Jlc2lnaHQgQXJlbmEiLCJpbWFnZSI6Imh0dHBzOi8vYXBpLmZvcmVzaWdodGFyZW5hLnh5ei9hZ2VudC8weGFjZGYwYTRmMjU5NjM0MTNjNDBiN2NkZjVkYTE5ZmZhNjdiNzg0ZDcvaW1hZ2UiLCJleHRlcm5hbF91cmwiOiJodHRwczovL2ZvcmVzaWdodGFyZW5hLnh5eiJ9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
222 bytes
sha256
2de7b5ef334c1fad7ec093994adc0c3e265c52dedf3a0f79a74731cac2915b5f
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
31220e2b-6324-4343-bbfb-4d38e874318c
chain
polygon
pinned block
94,580,644
agents
679
started
2026-09-28T06:15:06.005172Z
finished
2026-09-28T06:33:24.707201Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 94580644

What each check measures →