AgentCount
Sections
Check your agent
Agent

gpt5.4-medium

polygon|id 541|owner 0xd77e3ff1f23016e90aeb32a0dbd897c0f2781e76

Checks 1–7

baseline with search and visit, no skills

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

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
    91757844
    chain_id
    137
    owner
    0xd77e3ff1f23016e90aeb32a0dbd897c0f2781e76
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    541
    tx_hash
    0x91a79666106da0bad944096eccee1f143a6a7bcdced1fac7a4b5a477688fff8d

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

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    442
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJncHQ1LjQtbWVkaXVtIiwiZGVzY3JpcHRpb24iOiJiYXNlbGluZSB3aXRoIHNlYXJjaCBhbmQgdmlzaXQsIG5vIHNraWxscyIsImltYWdlIjoiaHR0cHM6Ly9hcGkuZm9yZXNpZ2h0YXJlbmEueHl6L2FnZW50LzB4ZDc3ZTNmZjFmMjMwMTZlOTBhZWIzMmEwZGJkODk3YzBmMjc4MWU3Ni9pbWFnZSIsImV4dGVybmFsX3VybCI6Imh0dHBzOi8vZm9yZXNpZ2h0YXJlbmEueHl6L2FnZW50LzB4ZDc3ZTNmZjFmMjMwMTZlOTBhZWIzMmEwZGJkODk3YzBmMjc4MWU3NiIsImFjdGl2ZSI6dHJ1ZSwicmVnaXN0cmF0aW9ucyI6W3siYWdlbnRSZWdpc3RyeSI6ImVpcDE1NToxMzc6MHg4MDA0QTE2OUZCNGEzMzI1MTM2RUIyOWZBMGNlQjZEMmU1MzlhNDMyIn1dfQ==

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

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    442
    body_sha256
    8d0a347fe940795a1213a3d212323439f9b671a110aebdd6d14cdbd8c485dfba
    content_type

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

  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, supportedTrust
    must_violations
    registrations[0].agentId
    registrations_checked
    1
    services_field_source
    neither
    services_status
    absent
    should_gaps
    services
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

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

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

  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-10T06:06:29.489474Z

  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:48.727050Z

On-chain snapshot

polygon
token id
541
owner
0xd77e3ff1f23016e90aeb32a0dbd897c0f2781e76
block
91,757,844
observed
2026-08-10T06:04:48.730176Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJncHQ1LjQtbWVkaXVtIiwiZGVzY3JpcHRpb24iOiJiYXNlbGluZSB3aXRoIHNlYXJjaCBhbmQgdmlzaXQsIG5vIHNraWxscyIsImltYWdlIjoiaHR0cHM6Ly9hcGkuZm9yZXNpZ2h0YXJlbmEueHl6L2FnZW50LzB4ZDc3ZTNmZjFmMjMwMTZlOTBhZWIzMmEwZGJkODk3YzBmMjc4MWU3Ni9pbWFnZSIsImV4dGVybmFsX3VybCI6Imh0dHBzOi8vZm9yZXNpZ2h0YXJlbmEueHl6L2FnZW50LzB4ZDc3ZTNmZjFmMjMwMTZlOTBhZWIzMmEwZGJkODk3YzBmMjc4MWU3NiIsImFjdGl2ZSI6dHJ1ZSwicmVnaXN0cmF0aW9ucyI6W3siYWdlbnRSZWdpc3RyeSI6ImVpcDE1NToxMzc6MHg4MDA0QTE2OUZCNGEzMzI1MTM2RUIyOWZBMGNlQjZEMmU1MzlhNDMyIn1dfQ==

What the fetch saw

data
scheme
data
request url
final url
http status
content type
size
442 bytes
sha256
8d0a347fe940795a1213a3d212323439f9b671a110aebdd6d14cdbd8c485dfba
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 →