AgentCount
Sections
Check your agent
Agent

Busfrid

mainnet|id 23478|owner 0x5f219fdbcb3071339d677835fb08e584bcc3c49e

Checks 1–7

My agent fixes AI slop content. It works by pasting a content and it identifies whether such content is AI generated

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
    25824613
    chain_id
    1
    token_id
    23478

    checked at 2026-08-24T11:34:12.399016Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    353
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIkJ1c2ZyaWQiLAogICJkZXNjcmlwdGlvbiI6ICJNeSBhZ2VudCBmaXhlcyBBSSBzbG9wIGNvbnRlbnQuIEl0IHdvcmtzIGJ5IHBhc3RpbmcgYSBjb250ZW50IGFuZCBpdCBpZGVudGlmaWVzIHdoZXRoZXIgc3VjaCBjb250ZW50IGlzIEFJIGdlbmVyYXRlZCIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IGZhbHNlCn0=

    checked at 2026-08-24T11:34:12.399016Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    353
    body_sha256
    aaa520c9a61d3767e2d7d41082e463f505822f81302f1ec4a21f2e4a34571f3e
    content_type

    checked at 2026-08-24T11:34:12.399016Z

  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-24T11:34:12.399016Z

  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-24T11:34:12.399016Z

  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-24T13:24:55.917314Z

  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-24T11:34:12.399016Z

On-chain snapshot

mainnet
token id
23478
owner
0x5f219fdbcb3071339d677835fb08e584bcc3c49e
block
25,824,613
observed
2026-08-24T11:34:12.400341Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIkJ1c2ZyaWQiLAogICJkZXNjcmlwdGlvbiI6ICJNeSBhZ2VudCBmaXhlcyBBSSBzbG9wIGNvbnRlbnQuIEl0IHdvcmtzIGJ5IHBhc3RpbmcgYSBjb250ZW50IGFuZCBpdCBpZGVudGlmaWVzIHdoZXRoZXIgc3VjaCBjb250ZW50IGlzIEFJIGdlbmVyYXRlZCIsCiAgImltYWdlIjogIiIsCiAgInNlcnZpY2VzIjogW10sCiAgInJlZ2lzdHJhdGlvbnMiOiBbXSwKICAic3VwcG9ydGVkVHJ1c3RzIjogW10sCiAgImFjdGl2ZSI6IGZhbHNlLAogICJ4NDAyc3VwcG9ydCI6IGZhbHNlCn0=

What the fetch saw

data
scheme
data
request url
final url
http status
content type
size
353 bytes
sha256
aaa520c9a61d3767e2d7d41082e463f505822f81302f1ec4a21f2e4a34571f3e
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
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →