AgentCount
Sections
Check your agent
Agent

TESTING

op|id 378|owner 0xf899e0d63855e371a678629ed60835470c589bdb

Checks 1–7

TESTINGTESTINGTESTINGTESTINGTESTINGTESTINGTESTINGTESTINGTESTING

Keyerrorthe check could not completefaildid not passpasspassedskippeda 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
    155291584
    chain_id
    10
    owner
    0xf899e0d63855e371a678629ed60835470c589bdb
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    378
    tx_hash
    0x198b6f571e7cabe458b822d47bd2ad35c3681ec65b3ec0387103fe3400556233

    checked at 2026-08-08T09:40:05.287450Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    300
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIlRFU1RJTkciLAogICJkZXNjcmlwdGlvbiI6ICJURVNUSU5HVEVTVElOR1RFU1RJTkdURVNUSU5HVEVTVElOR1RFU1RJTkdURVNUSU5HVEVTVElOR1RFU1RJTkciLAogICJpbWFnZSI6ICIiLAogICJzZXJ2aWNlcyI6IFtdLAogICJyZWdpc3RyYXRpb25zIjogW10sCiAgInN1cHBvcnRlZFRydXN0cyI6IFtdLAogICJhY3RpdmUiOiBmYWxzZSwKICAieDQwMnN1cHBvcnQiOiBmYWxzZQp9

    checked at 2026-08-08T09:40:05.287450Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    300
    body_sha256
    30ec9784bdfe31bd13d2d339fd7058e1edb3ec1e2e950bb8671e417065afbc85
    content_type

    checked at 2026-08-08T09:40:05.287450Z

  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-08T09:40:05.287450Z

  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-08T09:40:05.287450Z

  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-08T09:41:43.918885Z

  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-08T09:40:05.287450Z

On-chain snapshot

op
token id
378
owner
0xf899e0d63855e371a678629ed60835470c589bdb
block
155,291,584
observed
2026-08-08T09:40:05.292978Z
tokenURI
data:application/json;base64,ewogICJ0eXBlIjogImh0dHBzOi8vZWlwcy5ldGhlcmV1bS5vcmcvRUlQUy9laXAtODAwNCNyZWdpc3RyYXRpb24tdjEiLAogICJuYW1lIjogIlRFU1RJTkciLAogICJkZXNjcmlwdGlvbiI6ICJURVNUSU5HVEVTVElOR1RFU1RJTkdURVNUSU5HVEVTVElOR1RFU1RJTkdURVNUSU5HVEVTVElOR1RFU1RJTkciLAogICJpbWFnZSI6ICIiLAogICJzZXJ2aWNlcyI6IFtdLAogICJyZWdpc3RyYXRpb25zIjogW10sCiAgInN1cHBvcnRlZFRydXN0cyI6IFtdLAogICJhY3RpdmUiOiBmYWxzZSwKICAieDQwMnN1cHBvcnQiOiBmYWxzZQp9

What the fetch saw

data
scheme
data
request url
final url
http status
content type
size
300 bytes
sha256
30ec9784bdfe31bd13d2d339fd7058e1edb3ec1e2e950bb8671e417065afbc85
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
9a6bee56-1594-4980-bafd-5efe49aae6ce
chain
op
pinned block
155,291,584
agents
535
started
2026-08-08T09:39:06.440025Z
finished
2026-08-08T09:40:35.797124Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 155291584

What each check measures →