Asset Factors
by CRYPTYX in Onchain & crypto
Factor t-scores for one asset across 8 classes and 8 horizons (1d-365d). Snapshot mode returns the latest anchor day; series mode returns a daily window. Standardised, z-capped, policy-aware. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).
https://cryptyx.ai/api/asset-factors- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 257 ms
- 512 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://cryptyx.ai/api/asset-factors
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/asset-factors?asset=BTC&days=90&horizons=7d%2C30d&mode=snapshotParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | string | Yes | Asset symbol (e.g. BTC, ETH, SOL); trimmed + uppercased server-side |
days | number | No | Lookback window in days for series mode (1-365). Default: 90 |
horizons | string | No | Optional comma-separated horizon filter for series mode (e.g. '7d,30d,90d'). Valid: 1d,7d,14d,30d,60d,90d,180d,365d. Invalid tokens are dropped silently. |
mode | string | No | snapshot = latest anchor day only; series = daily window. Default: snapshot One of: snapshot, series. |
Example response
The provider's example. We can't check it without paying.
Example response, 57 lines
{
"_next": {
"description": "Recommended next calls given the response above.",
"hints": [
{
"method": "GET",
"path": "/api/asset/active-signals",
"price_usd": 0.05,
"reason": "Which class scores translate into currently-firing signals."
},
{
"method": "GET",
"path": "/api/asset/thesis",
"price_usd": 0.05,
"reason": "Claude-narrated conviction call."
}
]
},
"asof_day": "2026-06-18",
"asset": "BTC",
"factors": [
{
"asof_day": "2026-06-18",
"asset": "BTC",
"class": "CORR",
"horizon": "1d",
"t_band": "neutral",
"t_score_pct": 0.62
},
{
"asof_day": "2026-06-18",
"asset": "BTC",
"class": "TR",
"horizon": "1d",
"t_band": "bullish",
"t_score_pct": 1.42
},
{
"asof_day": "2026-06-18",
"asset": "BTC",
"class": "VOL",
"horizon": "30d",
"t_band": "bearish",
"t_score_pct": -0.88
},
{
"asof_day": "2026-06-18",
"asset": "BTC",
"class": "FLOW",
"horizon": "90d",
"t_band": "neutral",
"t_score_pct": 0.34
}
],
"mode": "snapshot",
"ok": true
}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/asset-factors?asset=BTC&days=90&horizons=7d%2C30d&mode=snapshot'
# 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-factors?asset=BTC&days=90&horizons=7d%2C30d&mode=snapshot' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fasset-factors
const res = await pay("https://cryptyx.ai/api/asset-factors?asset=BTC&days=90&horizons=7d%2C30d&mode=snapshot");
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/asset-factors?asset=BTC&days=90&horizons=7d%2C30d&mode=snapshot")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 307 ms | $0.01 |
| 8 h ago | Passed | 402 | 366 ms | $0.01 |
| 12 h ago | Passed | 402 | 340 ms | $0.01 |
| 16 h ago | Passed | 402 | 241 ms | $0.01 |
| 20 h ago | Passed | 402 | 233 ms | $0.01 |
Show 10 older checks
| 24 h ago | Passed | 402 | 343 ms | $0.01 |
| 28 h ago | Passed | 402 | 287 ms | $0.01 |
| 32 h ago | Passed | 402 | 231 ms | $0.01 |
| 36 h ago | Passed | 402 | 281 ms | $0.01 |
| 40 h ago | Passed | 402 | 218 ms | $0.01 |
| 44 h ago | Passed | 402 | 326 ms | $0.01 |
| 2 days ago | Passed | 402 | 226 ms | $0.01 |
| 2 days ago | Passed | 402 | 257 ms | $0.01 |
| 2 days ago | Passed | 402 | 282 ms | $0.01 |
| 3 days ago | Passed | 402 | 216 ms | $0.01 |