Agent

OKX Bot Risk

xlayer|id 13753|owner 0xaa17d42f8b35f4f2216651c2e83b6405f1b4d5ca

Checks 1–7

Independent, quantitative risk assessment for any OKX copy-trading lead trader — so you can be more confident about your own bot. ▸ WHY — A track record shows what happened, not how much was skill and how much was luck. ▸ METHOD — 10,000-path stationary bootstrap (Politis & Romano, 1994); tail risk as VaR 95% and CVaR; Sharpe credibility as Probabilistic and Deflated Sharpe Ratio (Bailey & Lopez de Prado). ▸ VALIDATED REPEATEDLY — Every metric recomputed independently from the raw trade series; scoring checked out of sample on 31 live traders and 6,516 closed trades (rank correlation 0.64 with realised drawdown). ▸ HONEST — Thin data is never scored as safe, nor as guilty. Confidence drops and the report names what could not be measured. ▸ YOU GET — Risk score, quality score, confidence, key metrics, a plain verdict, and a private link to the full visual report. ▸ NOTE — Reference analysis for your own due diligence, not investment advice. Free.

Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda check this one depends on did not passunclaimedthe document made no claim to checknot 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
    75512467
    chain_id
    196
    owner
    0xaa17d42f8b35f4f2216651c2e83b6405f1b4d5ca
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    13753
    tx_hash
    0xc8506662ca5f7ad3de36b353153cb330938b4b94002f871f859afdbc7fb51fcc

    checked at 2026-11-10T04:52:43.588023Z

  2. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    3794
    body_sha256
    51780d0dfae9eb689c2177bf2f9b1082f6529af55c3b3dea29b91505d6c46419
    content_type
    application/json

    checked at 2026-11-10T04:52:43.588023Z

  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-11-10T04:52:43.588023Z

  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-11-10T04:52:43.588023Z

  5. 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.

  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-11-10T04:52:43.588023Z

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
13753
owner
0xaa17d42f8b35f4f2216651c2e83b6405f1b4d5ca
block
75,512,467
observed
2026-11-10T04:52:43.593009Z
tokenURIopen →
https://static.okx.com/cdn/web3/wallet/marketplace/headimages/agent/card/e0121d0a-f69e-4608-89af-106e911c8f4f.json

What the fetch saw

https
scheme
https
http status
200
content type
application/json
size
3,794 bytes
sha256
51780d0dfae9eb689c2177bf2f9b1082f6529af55c3b3dea29b91505d6c46419
elapsed
3,243 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
1fe5fb18-e1cc-4fd7-a4b2-4b5636007967
chain
xlayer
pinned block
75,512,467
agents
15,398
started
2026-11-10T03:31:44.012992Z
finished
2026-11-10T05:01:27.474376Z
checker
0.7.0 · 9796f5f3bdd4b8bb6c6ac14a68e5fac0ca13114c
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- xlayer   # at block 75512467

What each check measures →

OKX Bot Risk · xlayer — AgentCount