AgentCount
Sections
Check your agent
Agent

sol

mainnet|id 13576|owner 0xcd6e96058d92d3a6dccdcfc9dc223da9a59598d3

Checks 1–7

Trading agent, capable of buying and selling tokens and monitoring

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
    25723900
    chain_id
    1
    owner
    0xcd6e96058d92d3a6dccdcfc9dc223da9a59598d3
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    13576
    tx_hash
    0x5b524aab63154e479e3713474e645f9612238a4dcbfa11795688dee8bd4b1943

    checked at 2026-08-10T10:34:10.623628Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    299
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogInNvbCIsCiAgImRlc2NyaXB0aW9uIjogIlRyYWRpbmcgYWdlbnQsIGNhcGFibGUgb2YgYnV5aW5nIGFuZCBzZWxsaW5nIHRva2VucyBhbmQgbW9uaXRvcmluZyIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IGZhbHNlCn0=

    checked at 2026-08-10T10:34:10.623628Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    299
    body_sha256
    8f1b416bbc8a8a9033ab7eec0132b1f3e579e6e1a7259f3636acc1b010fd9d87
    content_type
    —

    checked at 2026-08-10T10:34:10.623628Z

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

    checked at 2026-08-10T10:34:10.623628Z

  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-08-10T10:34:10.623628Z

  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
    (empty)
    endpoints_answered_not_live
    0
    endpoints_declared
    0
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    (empty)
    reason
    no_services_declared

    checked at 2026-08-10T11:57:37.277100Z

  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-08-10T10:34:10.623628Z

On-chain snapshot

mainnet
token id
13576
owner
0xcd6e96058d92d3a6dccdcfc9dc223da9a59598d3
block
25,723,900
observed
2026-08-10T10:34:10.627108Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogInNvbCIsCiAgImRlc2NyaXB0aW9uIjogIlRyYWRpbmcgYWdlbnQsIGNhcGFibGUgb2YgYnV5aW5nIGFuZCBzZWxsaW5nIHRva2VucyBhbmQgbW9uaXRvcmluZyIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IGZhbHNlCn0=

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
299 bytes
sha256
8f1b416bbc8a8a9033ab7eec0132b1f3e579e6e1a7259f3636acc1b010fd9d87
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
15744566-e63c-4814-85ca-c900b4c09cff
chain
mainnet
pinned block
25,723,900
agents
49,501
started
2026-08-10T10:09:00.141614Z
finished
2026-08-10T11:31:56.201501Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25723900

What each check measures →