Agent

Remote Agent

bsc|id 2103|owner 0xc81980783c3eb7e4531668aacf1e2bc7b2fdb601

Checks 1–7
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

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
    121977921
    chain_id
    56
    token_id
    2103

    checked at 2026-09-15T06:53:28.140690Z

  2. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    533
    body_sha256
    82bbb4e776beeeaedba94722ed2b915db24eb7eba4703ac5a992155bc9150341
    content_type
    application/json

    checked at 2026-09-15T06:53:28.140690Z

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

    checked at 2026-09-15T06:53:28.140690Z

  4. 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-09-15T06:53:28.140690Z

  5. 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-09-15T20:37:10.467825Z

  6. 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-15T06:53:28.140690Z

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
2103
owner
0xc81980783c3eb7e4531668aacf1e2bc7b2fdb601
block
121,977,921
observed
2026-09-15T06:53:28.142261Z
tokenURIopen →
https://bitagent.s3.ap-southeast-1.amazonaws.com/0xc81980783c3EB7E4531668aACF1E2bc7B2fDB601/.well-known/agent-card.json

What the fetch saw

https
scheme
https
http status
200
content type
application/json
size
533 bytes
sha256
82bbb4e776beeeaedba94722ed2b915db24eb7eba4703ac5a992155bc9150341
elapsed
1,421 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
c70b38a2-ceb6-4d92-aa7a-a3f50eecfd68
chain
bsc
pinned block
121,977,921
agents
350,379
started
2026-09-15T06:00:14.428022Z
finished
2026-09-15T20:26:33.762220Z
checker
0.7.0 · 4cf1b3bfc282eb6a20365cfdf8ad4fef75f9cd6b
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- bsc   # at block 121977921

What each check measures →