AgentCount
Sections
Check your agent
Agent

Agent King

bsc|id 4|owner 0x379a3a24860080a1dfeb76a2ae9af24198307a85

Checks 1–7

King of purr-fect agents.

Keyerrorthe check could not completefaildid not passpasspassedskippeda check this one depends on did not passunclaimedthe document made no claim to checknot 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
    112874357
    chain_id
    56
    owner
    0x379a3a24860080a1dfeb76a2ae9af24198307a85
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    4
    tx_hash
    —

    checked at 2026-07-29T19:31:34.642699Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    461
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJBZ2VudCBLaW5nIiwiZGVzY3JpcHRpb24iOiJLaW5nIG9mIHB1cnItZmVjdCBhZ2VudHMuIiwiaW1hZ2UiOiJodHRwczovL3IyLWltYWdlLXdvcmtlci5waWV2ZXJzZS1pbWcud29ya2Vycy5kZXYvcHVycmZlY3QtMS5qcGciLCJhdHRyaWJ1dGVzIjpbeyJ2YWx1ZSI6MSwibWF4X3ZhbHVlIjoxMCwidHJhaXRfdHlwZSI6IlNlcmllcyIsImRpc3BsYXlfdHlwZSI6Im51bWJlciJ9LHsidmFsdWUiOiJCTkIgQ2hhaW4iLCJ0cmFpdF90eXBlIjoiTmV0d29yayJ9LHsidmFsdWUiOjU2LCJ0cmFpdF90eXBlIjoiQ2hhaW4gSUQiLCJkaXNwbGF5X3R5cGUiOiJudW1iZXIifV0sIng0MDJTdXBwb3J0Ijp0cnVlLCJhY3RpdmUiOnRydWUsInN1cHBvcnRlZFRydXN0IjpbInJlcHV0YXRpb24iXX0=

    checked at 2026-07-29T19:31:34.642699Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    461
    body_sha256
    7ab542f783f617260a4ebd17e99b0fdabe63a375fba58d17277458a9110aff8b
    content_type
    —

    checked at 2026-07-29T19:31:34.642699Z

  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
    (empty)
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    neither
    services_status
    absent
    should_gaps
    services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-07-29T19:31:34.642699Z

  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-07-29T19:31:34.642699Z

  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

    pass

    At least one on-chain feedback entry names this agent.

    passed

    distinct_authors
    2
    feedback_count
    2

    checked at 2026-07-29T19:31:34.642699Z

On-chain snapshot

bsc
token id
4
owner
0x379a3a24860080a1dfeb76a2ae9af24198307a85
block
112,874,357
observed
2026-07-29T19:31:34.642941Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJBZ2VudCBLaW5nIiwiZGVzY3JpcHRpb24iOiJLaW5nIG9mIHB1cnItZmVjdCBhZ2VudHMuIiwiaW1hZ2UiOiJodHRwczovL3IyLWltYWdlLXdvcmtlci5waWV2ZXJzZS1pbWcud29ya2Vycy5kZXYvcHVycmZlY3QtMS5qcGciLCJhdHRyaWJ1dGVzIjpbeyJ2YWx1ZSI6MSwibWF4X3ZhbHVlIjoxMCwidHJhaXRfdHlwZSI6IlNlcmllcyIsImRpc3BsYXlfdHlwZSI6Im51bWJlciJ9LHsidmFsdWUiOiJCTkIgQ2hhaW4iLCJ0cmFpdF90eXBlIjoiTmV0d29yayJ9LHsidmFsdWUiOjU2LCJ0cmFpdF90eXBlIjoiQ2hhaW4gSUQiLCJkaXNwbGF5X3R5cGUiOiJudW1iZXIifV0sIng0MDJTdXBwb3J0Ijp0cnVlLCJhY3RpdmUiOnRydWUsInN1cHBvcnRlZFRydXN0IjpbInJlcHV0YXRpb24iXX0=

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
461 bytes
sha256
7ab542f783f617260a4ebd17e99b0fdabe63a375fba58d17277458a9110aff8b
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
f78c7891-e787-43f1-9748-61d5a361e9ff
chain
bsc
pinned block
112,874,357
agents
244,208
started
2026-07-29T19:31:31.986385Z
finished
2026-07-30T06:50:51.109117Z
checker
0.5.0 · 987ce24581f221a1d54a84b47a72d69100214e88-dirty
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- bsc   # at block 112874357
Download this run

f78c7891-e787-43f1-9748-61d5a361e9ff.tar.zst23.9 MB|sha256|all runs

What each check measures →