AgentCount
Sections
Check your agent
Agent

benchmark-gpt-5.4

polygon|id 440|owner 0x014c84ff7f96b5dd8393f38af422f1975fd68322

Checks 1–7
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
    91757844
    chain_id
    137
    owner
    0x014c84ff7f96b5dd8393f38af422f1975fd68322
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    440
    tx_hash
    0x88f04e75433e57474341dbc66eecf6187591547dbbfc9e81574ac2f049fa25a5

    checked at 2026-08-10T06:04:31.673695Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    53
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJuYW1lIjoiYmVuY2htYXJrLWdwdC01LjQiLCJtb2RlbCI6Im9wZW5haS9ncHQtNS40In0=

    checked at 2026-08-10T06:04:31.673695Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    53
    body_sha256
    b972974eed44fc9197c46b7071e8aeea07b851aeaee416bc87f6469522bca8ca
    content_type

    checked at 2026-08-10T06:04:31.673695Z

  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, description, image, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T06:04:31.673695Z

  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:04:31.673695Z

  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-10T06:04:31.673695Z

On-chain snapshot

polygon
token id
440
owner
0x014c84ff7f96b5dd8393f38af422f1975fd68322
block
91,757,844
observed
2026-08-10T06:04:31.677471Z
tokenURI
data:application/json;base64,eyJuYW1lIjoiYmVuY2htYXJrLWdwdC01LjQiLCJtb2RlbCI6Im9wZW5haS9ncHQtNS40In0=

What the fetch saw

data
scheme
data
request url
final url
http status
content type
size
53 bytes
sha256
b972974eed44fc9197c46b7071e8aeea07b851aeaee416bc87f6469522bca8ca
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
b8acef9f-d219-4fc8-8aaa-b7ce20d1b168
chain
polygon
pinned block
91,757,844
agents
608
started
2026-08-10T06:03:12.744539Z
finished
2026-08-10T06:04:58.131352Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 91757844

What each check measures →