ToolVet
78trust / 100

Market Pulse Regime Cell Context

by CRYPTYX in Markets & finance

x402 APIPassing, checked 1 h ago

Historical performance of a specific (horizon, regime_label) cell — n_prints, mean 30d forward return, hit rate, and last 5 instances. Answers "when this regime showed up before, what happened next?" — analytical primitive for regime-conditional strategy backtesting. Runs across 200+ digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.

GET
https://cryptyx.ai/api/market-pulse/regime-cell-context
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
229 ms
379 ms slowest 5%
Last check
Passed
1 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/market-pulse/regime-cell-context

Each call costs $0.01 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/market-pulse/regime-cell-context?horizon=&label=

Parameters

ParameterTypeRequiredDescription
horizonstringYesOne of: 1d, 7d, 14d, 30d, 60d, 90d, 180d, 365d
labelstringYesRegime label (e.g. expansion, consolidation, deleveraging)

Example response

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

{
  "horizon": "30d",
  "last_instances": [
    {
      "asof_day": "2026-06-15",
      "duration_days": 22,
      "r30_return": 0.11
    },
    {
      "asof_day": "2026-05-01",
      "duration_days": 18,
      "r30_return": 0.07
    }
  ],
  "n_r30": 152,
  "n_total": 187,
  "ok": true,
  "r30_hit": 0.612,
  "r30_mean": 0.084,
  "regime_label": "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.01.

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

# 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/market-pulse/regime-cell-context?horizon=&label=' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcryptyx.ai%2Fapi%2Fmarket-pulse%2Fregime-cell-context
const res = await pay("https://cryptyx.ai/api/market-pulse/regime-cell-context?horizon=&label=");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
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/market-pulse/regime-cell-context?horizon=&label=")
    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
1 h agoPassed402213 ms$0.01
6 h agoPassed402297 ms$0.01
10 h agoPassed402208 ms$0.01
14 h agoPassed402208 ms$0.01
18 h agoPassed402205 ms$0.01
Show 10 older checks
22 h agoPassed402274 ms$0.01
26 h agoPassed402341 ms$0.01
30 h agoPassed402283 ms$0.01
34 h agoPassed402170 ms$0.01
38 h agoPassed402299 ms$0.01
42 h agoPassed402298 ms$0.01
46 h agoPassed402257 ms$0.01
2 days agoPassed402254 ms$0.01
2 days agoPassed402271 ms$0.01
2 days agoPassed402296 ms$0.01