78trust / 100

Asset Regime Context

by CRYPTYX in Onchain & crypto

x402 APIPassing, checked 2 h ago

Per-asset macro regime context — current regime id, confidence, days-in-regime streak, conditional forward-return stats at 1d/7d/14d/30d, and top historical regime transitions. Grounds sizing in what historically happens next. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).

GET
https://cryptyx.ai/api/asset/regime-context
Price
$0.05
per call in USDC
Uptime
100%
last 30 days
Response time
269 ms
395 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://cryptyx.ai/api/asset/regime-context

Each call costs $0.05 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://cryptyx.ai/api/asset/regime-context?horizon=&symbol=

Parameters

ParameterTypeRequiredDescription
horizonstringNoSelected horizon echoed back in selected_horizon; one of 1d/7d/14d/30d (default 14d). Note: stats array still returns all horizons regardless
symbolstringYesAsset ticker (uppercased server-side), e.g. BTC, ETH, SOL

Example response

The provider's example. We can't check it without paying.

Example response, 117 lines
{
  "current": {
    "asof_day": "2026-06-18",
    "confidence": 0.67,
    "days_in_regime": 23,
    "regime": "expansion"
  },
  "ok": true,
  "selected_horizon": "14d",
  "stats": [
    {
      "hit_rate": 0.52,
      "horizon": "1d",
      "mean_return": 0.0008,
      "median_return": 0.0005,
      "n": 142,
      "regime": "consolidation"
    },
    {
      "hit_rate": 0.56,
      "horizon": "7d",
      "mean_return": 0.011,
      "median_return": 0.008,
      "n": 138,
      "regime": "consolidation"
    },
    {
      "hit_rate": 0.58,
      "horizon": "14d",
      "mean_return": 0.019,
      "median_return": 0.014,
      "n": 132,
      "regime": "consolidation"
    },
    {
      "hit_rate": 0.61,
      "horizon": "30d",
      "mean_return": 0.034,
      "median_return": 0.027,
      "n": 118,
      "regime": "consolidation"
    },
    {
      "hit_rate": 0.55,
      "horizon": "1d",
      "mean_return": 0.0021,
      "median_return": 0.0013,
      "n": 187,
      "regime": "expansion"
    },
    {
      "hit_rate": 0.61,
      "horizon": "7d",
      "mean_return": 0.018,
      "median_return": 0.014,
      "n": 181,
      "regime": "expansion"
    },
    {
      "hit_rate": 0.64,
      "horizon": "14d",
      "mean_return": 0.032,
      "median_return": 0.025,
      "n": 175,
      "regime": "expansion"
    },
    {
      "hit_rate": 0.66,
      "horizon": "30d",
      "mean_return": 0.058,
      "median_return": 0.043,
      "n": 162,
      "regime": "expansion"
    },
    {
      "hit_rate": 0.42,
      "horizon": "14d",
      "mean_return": -0.012,
      "median_return": -0.009,
      "n": 94,
      "regime": "contraction"
    }
  ],
  "symbol": "BTC",
  "transitions": [
    {
      "from_regime": "consolidation",
      "n": 18,
      "to_regime": "expansion"
    },
    {
      "from_regime": "expansion",
      "n": 17,
      "to_regime": "consolidation"
    },
    {
      "from_regime": "consolidation",
      "n": 9,
      "to_regime": "contraction"
    },
    {
      "from_regime": "contraction",
      "n": 8,
      "to_regime": "consolidation"
    },
    {
      "from_regime": "expansion",
      "n": 4,
      "to_regime": "contraction"
    },
    {
      "from_regime": "contraction",
      "n": 3,
      "to_regime": "expansion"
    }
  ]
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://cryptyx.ai/api/asset/regime-context?horizon=&symbol='

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://cryptyx.ai/api/asset/regime-context?horizon=&symbol=' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcryptyx.ai%2Fapi%2Fasset%2Fregime-context
const res = await pay("https://cryptyx.ai/api/asset/regime-context?horizon=&symbol=");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://cryptyx.ai/api/asset/regime-context?horizon=&symbol=")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402367 ms$0.05
7 h agoPassed402215 ms$0.05
11 h agoPassed402380 ms$0.05
15 h agoPassed402217 ms$0.05
19 h agoPassed402387 ms$0.05
Show 10 older checks
23 h agoPassed402309 ms$0.05
27 h agoPassed402395 ms$0.05
31 h agoPassed402310 ms$0.05
35 h agoPassed402212 ms$0.05
39 h agoPassed402407 ms$0.05
43 h agoPassed402308 ms$0.05
2 days agoPassed402218 ms$0.05
2 days agoPassed402198 ms$0.05
2 days agoPassed402367 ms$0.05
2 days agoPassed402389 ms$0.05