AgentCount
Sections
Agent

P老板

bsc|id 10315|owner 0x9f412ecd38cf905d4a1d8a7ec74879ee305e2787

Checks 1–7

Who controls the memes,controls the Universe.58369

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

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
    126008346
    chain_id
    56
    owner
    0x9f412ecd38cf905d4a1d8a7ec74879ee305e2787
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    10315
    tx_hash
    0x645206bdc1ee876c26366d4a95149ed2aac22b9ce91b3542e71a2719111d3fa7

    checked at 2026-10-06T06:28:29.208318Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    195
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (289 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJQ6ICB5p2/IiwiZGVzY3JpcHRpb24iOiJXaG8gY29udHJvbHMgdGhlIG1lbWVzLGNvbnRyb2xzIHRoZSBVbml2ZXJzZS41ODM2OSIsImltYWdlIjoiIiwiYWN0aXZlIjp0cnVlLCJ4NDAyU3VwcG9ydCI6ZmFsc2V9

    checked at 2026-10-06T06:28:29.208318Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    195
    body_sha256
    6f3648cc6e4400930f39390eb8305f2a3cc8d0bee61829ba5c64721ede3c04f2
    content_type
    —

    checked at 2026-10-06T06:28:29.208318Z

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

    checked at 2026-10-06T06:28:29.208318Z

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

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

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

bsc
token id
10315
owner
0x9f412ecd38cf905d4a1d8a7ec74879ee305e2787
block
126,008,346
observed
2026-10-06T06:28:29.211046Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJQ6ICB5p2/IiwiZGVzY3JpcHRpb24iOiJXaG8gY29udHJvbHMgdGhlIG1lbWVzLGNvbnRyb2xzIHRoZSBVbml2ZXJzZS41ODM2OSIsImltYWdlIjoiIiwiYWN0aXZlIjp0cnVlLCJ4NDAyU3VwcG9ydCI6ZmFsc2V9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
195 bytes
sha256
6f3648cc6e4400930f39390eb8305f2a3cc8d0bee61829ba5c64721ede3c04f2
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
39c9b855-a05a-47f7-9857-ac11076a502b
chain
bsc
pinned block
126,008,346
agents
364,697
started
2026-10-06T06:00:16.906244Z
finished
2026-10-06T21:58:01.042309Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- bsc   # at block 126008346

What each check measures →