AgentCount
Sections
Check your agent
Agent

发点100m的狗，速度 @Zoozww

mainnet|id 17375|owner 0x3fc55fda9d2beec9ce9e6715739e881a37decfba

Checks 1–7

发点100m的狗，速度 @Zooz发点100m的狗，速度 @Zooz发点100m的狗，速度 @Zooz发点100m的狗，速度 @Zooz发点100m的狗，速度 @Zooz发点100m的狗，速度 @Zooz

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

6 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
    25774147
    chain_id
    1
    owner
    0x3fc55fda9d2beec9ce9e6715739e881a37decfba
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    17375
    tx_hash
    0x63aa95c74d6a35860c1ea4951e5b5e09df35511a7e6ab5c1cce54e1360aa8f0f

    checked at 2026-08-17T10:41:45.442916Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    371
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiLlj5HngrkxMDBt55qE54uX77yM6YCf5bqm4oCFQFpvb3p3dyIsImRlc2NyaXB0aW9uIjoi5Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab296IiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0IjpmYWxzZX0=

    checked at 2026-08-17T10:41:45.442916Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    371
    body_sha256
    a00b3839180394d742fd8101708a41e18492902739e3e78f21d6ce2046a69eb9
    content_type
    —

    checked at 2026-08-17T10:41:45.442916Z

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

    checked at 2026-08-17T10:41:45.442916Z

  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-17T10:41:45.442916Z

  6. Answers?rung 6 · —

    not checked

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

    not checked — this check was never asked

    This run never reached this check for this agent.

  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-17T10:41:45.442916Z

On-chain snapshot

mainnet
token id
17375
owner
0x3fc55fda9d2beec9ce9e6715739e881a37decfba
block
25,774,147
observed
2026-08-17T10:41:45.445190Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiLlj5HngrkxMDBt55qE54uX77yM6YCf5bqm4oCFQFpvb3p3dyIsImRlc2NyaXB0aW9uIjoi5Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab2965Y+R54K5MTAwbeeahOeLl++8jOmAn+W6puKAhUBab296IiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0IjpmYWxzZX0=

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
371 bytes
sha256
a00b3839180394d742fd8101708a41e18492902739e3e78f21d6ce2046a69eb9
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
ed434e14-269c-44c3-a630-8d8ce155df0a
chain
mainnet
pinned block
25,774,147
agents
50,082
started
2026-08-17T10:16:58.310055Z
finished
2026-08-17T11:39:40.756712Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25774147

What each check measures →