CRYPTYX

Continuously compounding intelligence across hundreds of metrics, signals, and digital assets. Clarity in chaos — built for elite operators and the agents that serve them.

DataLiveeip155:8453Exactvia cdp
CryptoTradingSignalsIntelligenceAgents
Calls · 30d
1→ 0%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 30 snapshots so far.
$41.48
Verified settled volume
1,236 settlements proven x402 by their on-chain EIP-3009 marker.
$0.050
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-09-05 12:57Z
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x0cD2c9724F185a029101b4AEACf3F114415c394f

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.05USDC≈ $0.05 USD
on Base · exact scheme

Pay 0.05 USDC on Base to 0x0cD2…c394f. The signed payment is good for 5 minutes.

USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
50000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x0cD2c9724F185a029101b4AEACf3F114415c394f",
    "amount": "50000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "asof_day": "",
          "signal_id": "",
          "threshold_key": "",
          "threshold_value": 0
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "ok": true,
          "n_total": 198,
          "asof_day": "2026-06-18",
          "signal_id": "TR_MOMO_CONT_14D",
          "n_triggered": 23,
          "threshold_key": "t_thr",
          "current_threshold": 0.5,
          "proposed_threshold": 0.6,
          "estimated_trigger_pct": 11.62,
          "estimated_trigger_rate": 0.1162
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "required": [
                "signal_id",
                "threshold_key",
                "threshold_value"
              ],
              "properties": {
                "asof_day": {
                  "type": "string",
                  "description": "Optional YYYY-MM-DD lookup day. Defaults to metrics.aligned_day_1d()"
                },
                "signal_id": {
                  "type": "string",
                  "description": "Atomic signal registry ID, uppercased server-side (e.g. TR_MOMO_CONT_14D, FLOW_ACCUM_NETUSD_7D, VOL_COMPRESSION_7v30)"
                },
                "threshold_key": {
                  "type": "string",
                  "description": "Parameter name to simulate (e.g. t_thr, z_thr). Used to fetch current_threshold from signals.signal_params for comparison"
                },
                "threshold_value": {
                  "type": "number",
                  "description": "Proposed cutoff value. Interpreted as z-score for most signals, t-score for TR_MOMO_* signals"
                }
              }
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-09-05 12:57Z
Last indexed by Roundhouse
2026-09-24 10:40Z
Last enriched (probe, favicon, geo)
2026-09-13 07:45Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 405
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 30 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service CRYPTYX and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=CRYPTYX'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://cryptyx.ai/api/signals/simulate, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.