AgentCount
Sections
Check your agent
Agent

RitmexAgent

mainnet|id 22610|owner 0xea9c085cd659fe6eaf01717cd3705e9f39375926

Checks 1–7

RitMEXAgent is the official AI-driven intelligence layer for the RitMEX ecosystem. Designed to bridge the gap between complex blockchain data and actionable insights, this agent provides seamless access to professional-grade cryptocurrency analytics. From real-time liquidity trends to advanced sentiment indicators, RitMEXAgent empowers you to navigate the volatile crypto market with precision and clarity.

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
    22610

    checked at 2026-08-24T11:32:52.827804Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    9843
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    scheme
    ipfs
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-24T11:32:52.827804Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    841
    body_sha256
    8181f7404dcca6cccd371ea29291a1619fef29db29860253576c1987d5f0e167
    content_type
    application/json

    checked at 2026-08-24T11:32:52.827804Z

  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
    present
    should_gaps
    services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:32:52.827804Z

  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:32:52.827804Z

  6. Answers?rung 6 · live

    pass

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

    passed

    endpoints
    {"declared":"https://www.ritmex.one/x402/crowdIndex","elapsed_ms":2533,"final_url":"https://www.ritmex.one/zh/x402/crowdIndex","http_status":402,"index":0,"kind":"https","name":"custom","outcome":"live","payment_gated":true,"probed":true,"probed_url":"https://www.ritmex.one/x402/crowdIndex"}, {"declared":"https://www.ritmex.one/x402/calendar","elapsed_ms":2856,"final_url":"https://www.ritmex.one/zh/x402/calendar","http_status":402,"index":1,"kind":"https","name":"custom","outcome":"live","payment_gated":true,"probed":true,"probed_url":"https://www.ritmex.one/x402/calendar"}
    endpoints_answered_not_live
    0
    endpoints_declared
    2
    endpoints_live
    2
    endpoints_our_error
    0
    endpoints_payment_gated
    2
    endpoints_probeable
    2
    endpoints_probed
    2
    endpoints_refused
    0

    checked at 2026-08-24T13:24:55.917314Z

  7. Has feedback?rung 7 · attested

    pass

    At least one on-chain feedback entry names this agent.

    passed

    distinct_authors
    1
    feedback_count
    1

    checked at 2026-08-24T11:32:52.827804Z

On-chain snapshot

mainnet
token id
22610
owner
0xea9c085cd659fe6eaf01717cd3705e9f39375926
block
25,824,613
observed
2026-08-24T11:32:52.828796Z
ipfs://QmbdER8mdwthaTm1JN2HGch9N4uA7RoaTq8WMnxu5JPwn7

What the fetch saw

ipfs
scheme
ipfs
http status
200
content type
application/json
size
841 bytes
sha256
8181f7404dcca6cccd371ea29291a1619fef29db29860253576c1987d5f0e167
elapsed
9,843 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 →