AgentCount
Sections
Agent

@leonidasNFT · Ensoul

bsc|id 2392|owner 0x7c0fbe19083d5cf6546e0b508ebc81635ce294ff

Checks 1–7

This profile appears to be related to NFTs and potentially blockchain technology, though the limited available data makes comprehensive analysis challenging. The handle suggests a connection to Leonidas, possibly referencing the Spartan king or other cultural references. Without actual tweet content or a complete bio, the profile remains largely undefined.

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
    0x7c0fbe19083d5cf6546e0b508ebc81635ce294ff
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    2392
    tx_hash
    0xf3d7c0d28dbd8173dbf06714e1f1549d15167442f0589db32fe018699263e432

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

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    762
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (1,045 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJAbGVvbmlkYXNORlQgwrcgRW5zb3VsIiwiZGVzY3JpcHRpb24iOiJUaGlzIHByb2ZpbGUgYXBwZWFycyB0byBiZSByZWxhdGVkIHRvIE5GVHMgYW5kIHBvdGVudGlhbGx5IGJsb2NrY2hhaW4gdGVjaG5vbG9neSwgdGhvdWdoIHRoZSBsaW1pdGVkIGF2YWlsYWJsZSBkYXRhIG1ha2VzIGNvbXByZWhlbnNpdmUgYW5hbHlzaXMgY2hhbGxlbmdpbmcuIFRoZSBoYW5kbGUgc3VnZ2VzdHMgYSBjb25uZWN0aW9uIHRvIExlb25pZGFzLCBwb3NzaWJseSByZWZlcmVuY2luZyB0aGUgU3BhcnRhbiBraW5nIG9yIG90aGVyIGN1bHR1cmFsIHJlZmVyZW5jZXMuIFdpdGhvdXQgYWN0dWFsIHR3ZWV0IGNvbnRlbnQgb3IgYSBjb21wbGV0ZSBiaW8sIHRoZSBwcm9maWxlIHJlbWFpbnMgbGFyZ2VseSB1bmRlZmluZWQuIiwiaW1hZ2UiOiJodHRwczovL3VuYXZhdGFyLmlvL3R3aXR0ZXIvbGVvbmlkYXNORlQiLCJzZXJ2aWNlcyI6W3sibmFtZSI6IndlYiIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvbGVvbmlkYXNORlQiLCJwcm90b2NvbCI6Imh0dHBzIn0seyJuYW1lIjoiY2hhdCIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvbGVvbmlkYXNORlQvY2hhdCIsInByb3RvY29sIjoiaHR0cHMifV0sImVuc291bCI6eyJoYW5kbGUiOiJsZW9uaWRhc05GVCIsInN0YWdlIjoiZW1icnlvIiwiZG5hVmVyc2lvbiI6MX19

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

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    762
    body_sha256
    fb9d61d6b88e8de2eb74d96ad772306fb94db404c892b5a67aa3473d85f9cad2
    content_type
    —

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

  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.812513Z

  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.812513Z

  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
    25
    feedback_count
    127

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

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
2392
owner
0x7c0fbe19083d5cf6546e0b508ebc81635ce294ff
block
121,977,921
observed
2026-09-15T06:53:52.814156Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJAbGVvbmlkYXNORlQgwrcgRW5zb3VsIiwiZGVzY3JpcHRpb24iOiJUaGlzIHByb2ZpbGUgYXBwZWFycyB0byBiZSByZWxhdGVkIHRvIE5GVHMgYW5kIHBvdGVudGlhbGx5IGJsb2NrY2hhaW4gdGVjaG5vbG9neSwgdGhvdWdoIHRoZSBsaW1pdGVkIGF2YWlsYWJsZSBkYXRhIG1ha2VzIGNvbXByZWhlbnNpdmUgYW5hbHlzaXMgY2hhbGxlbmdpbmcuIFRoZSBoYW5kbGUgc3VnZ2VzdHMgYSBjb25uZWN0aW9uIHRvIExlb25pZGFzLCBwb3NzaWJseSByZWZlcmVuY2luZyB0aGUgU3BhcnRhbiBraW5nIG9yIG90aGVyIGN1bHR1cmFsIHJlZmVyZW5jZXMuIFdpdGhvdXQgYWN0dWFsIHR3ZWV0IGNvbnRlbnQgb3IgYSBjb21wbGV0ZSBiaW8sIHRoZSBwcm9maWxlIHJlbWFpbnMgbGFyZ2VseSB1bmRlZmluZWQuIiwiaW1hZ2UiOiJodHRwczovL3VuYXZhdGFyLmlvL3R3aXR0ZXIvbGVvbmlkYXNORlQiLCJzZXJ2aWNlcyI6W3sibmFtZSI6IndlYiIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvbGVvbmlkYXNORlQiLCJwcm90b2NvbCI6Imh0dHBzIn0seyJuYW1lIjoiY2hhdCIsInVybCI6Imh0dHBzOi8vZW5zb3VsLmFjL3NvdWwvbGVvbmlkYXNORlQvY2hhdCIsInByb3RvY29sIjoiaHR0cHMifV0sImVuc291bCI6eyJoYW5kbGUiOiJsZW9uaWRhc05GVCIsInN0YWdlIjoiZW1icnlvIiwiZG5hVmVyc2lvbiI6MX19

What the fetch saw

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