AgentCount
Sections
Agent

@feibo03 · Ensoul

bsc|id 2396|owner 0x87c74283d2b29061778c1169f414110898497c62

Checks 1–7

The profile @feibo03 appears to be a newly created or inactive Twitter account with minimal public presence. The account describes itself as a public figure but provides no additional information in the bio, and the recent tweets are placeholder messages indicating the Twitter API is not configured for real data extraction.

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
    owner
    0x87c74283d2b29061778c1169f414110898497c62
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    2396
    tx_hash
    0x71fa2aa0210eddb93e4617f3003009d1a7cebb6ad1f5d1de23446d98c712cae3

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

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    709
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (977 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJAZmVpYm8wMyDCtyBFbnNvdWwiLCJkZXNjcmlwdGlvbiI6IlRoZSBwcm9maWxlIEBmZWlibzAzIGFwcGVhcnMgdG8gYmUgYSBuZXdseSBjcmVhdGVkIG9yIGluYWN0aXZlIFR3aXR0ZXIgYWNjb3VudCB3aXRoIG1pbmltYWwgcHVibGljIHByZXNlbmNlLiBUaGUgYWNjb3VudCBkZXNjcmliZXMgaXRzZWxmIGFzIGEgcHVibGljIGZpZ3VyZSBidXQgcHJvdmlkZXMgbm8gYWRkaXRpb25hbCBpbmZvcm1hdGlvbiBpbiB0aGUgYmlvLCBhbmQgdGhlIHJlY2VudCB0d2VldHMgYXJlIHBsYWNlaG9sZGVyIG1lc3NhZ2VzIGluZGljYXRpbmcgdGhlIFR3aXR0ZXIgQVBJIGlzIG5vdCBjb25maWd1cmVkIGZvciByZWFsIGRhdGEgZXh0cmFjdGlvbi4iLCJpbWFnZSI6Imh0dHBzOi8vdW5hdmF0YXIuaW8vdHdpdHRlci9mZWlibzAzIiwic2VydmljZXMiOlt7Im5hbWUiOiJ3ZWIiLCJ1cmwiOiJodHRwczovL2Vuc291bC5hYy9zb3VsL2ZlaWJvMDMiLCJwcm90b2NvbCI6Imh0dHBzIn0seyJuYW1lIjoiY2hhdCIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvZmVpYm8wMy9jaGF0IiwicHJvdG9jb2wiOiJodHRwcyJ9XSwiZW5zb3VsIjp7ImhhbmRsZSI6ImZlaWJvMDMiLCJzdGFnZSI6ImVtYnJ5byIsImRuYVZlcnNpb24iOjF9fQ==

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

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    709
    body_sha256
    d2c61487ccaad08b9e800f8745c1b42993372f2e29f082dd331d0051e464fd2b
    content_type
    —

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

  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
    services
    services_status
    present
    should_gaps
    services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

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

  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-09-15T06:53:52.988553Z

  6. Answers?rung 6 · live

    unprobeable

    A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.

    unprobeable — no declared endpoint that a probe can reach

    endpoints
    {"declared":null,"index":0,"kind":"missing","name":"web","probed":false}, {"declared":null,"index":1,"kind":"missing","name":"chat","probed":false}
    endpoints_answered_not_live
    0
    endpoints_declared
    2
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    missing, missing
    reason
    no_probeable_endpoint

    checked at 2026-09-15T20:37:10.467825Z

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    16
    feedback_count
    43

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

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
2396
owner
0x87c74283d2b29061778c1169f414110898497c62
block
121,977,921
observed
2026-09-15T06:53:52.989878Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJAZmVpYm8wMyDCtyBFbnNvdWwiLCJkZXNjcmlwdGlvbiI6IlRoZSBwcm9maWxlIEBmZWlibzAzIGFwcGVhcnMgdG8gYmUgYSBuZXdseSBjcmVhdGVkIG9yIGluYWN0aXZlIFR3aXR0ZXIgYWNjb3VudCB3aXRoIG1pbmltYWwgcHVibGljIHByZXNlbmNlLiBUaGUgYWNjb3VudCBkZXNjcmliZXMgaXRzZWxmIGFzIGEgcHVibGljIGZpZ3VyZSBidXQgcHJvdmlkZXMgbm8gYWRkaXRpb25hbCBpbmZvcm1hdGlvbiBpbiB0aGUgYmlvLCBhbmQgdGhlIHJlY2VudCB0d2VldHMgYXJlIHBsYWNlaG9sZGVyIG1lc3NhZ2VzIGluZGljYXRpbmcgdGhlIFR3aXR0ZXIgQVBJIGlzIG5vdCBjb25maWd1cmVkIGZvciByZWFsIGRhdGEgZXh0cmFjdGlvbi4iLCJpbWFnZSI6Imh0dHBzOi8vdW5hdmF0YXIuaW8vdHdpdHRlci9mZWlibzAzIiwic2VydmljZXMiOlt7Im5hbWUiOiJ3ZWIiLCJ1cmwiOiJodHRwczovL2Vuc291bC5hYy9zb3VsL2ZlaWJvMDMiLCJwcm90b2NvbCI6Imh0dHBzIn0seyJuYW1lIjoiY2hhdCIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvZmVpYm8wMy9jaGF0IiwicHJvdG9jb2wiOiJodHRwcyJ9XSwiZW5zb3VsIjp7ImhhbmRsZSI6ImZlaWJvMDMiLCJzdGFnZSI6ImVtYnJ5byIsImRuYVZlcnNpb24iOjF9fQ==

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
709 bytes
sha256
d2c61487ccaad08b9e800f8745c1b42993372f2e29f082dd331d0051e464fd2b
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
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 →