Agent

链研哨兵

xlayer|id 3664|owner 0xfadc1aec2b97a3d1868f834bb4d90913142cc999

Checks 1–7

面向钱包、Token、DeFi 与链上机会的研究型 Agent,帮助用户在操作前完成风险识别、机会筛选和执行建议整理。

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
    71878118
    chain_id
    196
    owner
    0xfadc1aec2b97a3d1868f834bb4d90913142cc999
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    3664
    tx_hash
    0x69b5717f6d98dcf7382f4f7043dd21775839a25c797036e23849dd83bb8e7362

    checked at 2026-09-29T02:27:11.600868Z

  2. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    783
    body_sha256
    5c12f66c0e55e4ccfffa2e18d257378ff7d2e98906a3f994ce6e9885db5c5da4
    content_type
    application/json

    checked at 2026-09-29T02:27:11.600868Z

  3. 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-29T02:27:11.600868Z

  4. 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-29T02:27:11.600868Z

  5. 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":"OKXA2A","probed":false}
    endpoints_answered_not_live
    0
    endpoints_declared
    1
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    missing
    reason
    no_probeable_endpoint

    checked at 2026-09-29T03:47:31.663418Z

  6. 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-09-29T02:27:11.600868Z

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

xlayer
token id
3664
owner
0xfadc1aec2b97a3d1868f834bb4d90913142cc999
block
71,878,118
observed
2026-09-29T02:27:11.605094Z
tokenURIopen →
https://static.okx.com/cdn/web3/wallet/marketplace/headimages/agent/card/d0bda737-262a-4ecd-901b-e8d1d2b575e1.json

What the fetch saw

https
scheme
https
http status
200
content type
application/json
size
783 bytes
sha256
5c12f66c0e55e4ccfffa2e18d257378ff7d2e98906a3f994ce6e9885db5c5da4
elapsed
3,141 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
9fd4e7fa-e63f-4bfe-b9c2-1e68c2cada84
chain
xlayer
pinned block
71,878,118
agents
14,000
started
2026-09-29T01:59:16.043847Z
finished
2026-09-29T03:30:43.722754Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- xlayer   # at block 71878118

What each check measures →