Asset Liquidity
by CRYPTYX in Onchain & crypto
Per-asset spot order-book depth timeseries — bid/ask USD at 50/100/200bp plus 1d/7d/30d spot volume. Optional futures envelope adds perp OB depth. Pre-trade depth and venue routing input. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).
https://cryptyx.ai/api/asset-liquidity- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 18 h ago, next in 2 days
Reliability
Latest check failed 18 h ago: Expected HTTP 402, got 401
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://cryptyx.ai/api/asset-liquidity
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-liquidity?asset=&days=0&include=Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | string | Yes | Asset symbol, uppercased (e.g. BTC, ETH, SOL) |
days | number | No | Trailing day window anchored to latest available day (0 = full history, max 365) |
include | string | No | Comma/space list of extras; pass 'futures' to add the latest-day futures OB depth block to the response |
Example response
The provider's example. We can't check it without paying.
Example response, 51 lines
{
"_next": {
"description": "Recommended next calls given the response above.",
"hints": [
{
"method": "GET",
"path": "/api/asset/asymmetry",
"price_usd": 0.05,
"reason": "Cross-class positioning panel with OB imbalance alongside funding + skew + taker BS."
},
{
"method": "GET",
"path": "/api/asset/thesis",
"price_usd": 0.05,
"reason": "Claude-narrated conviction synthesising liquidity + signals + regime."
}
]
},
"asof_day": "2026-06-19",
"asset": "BTC",
"futures_branch_note": "Pass ?include=futures to also receive: futures: { asof_day, asset, fut_ob_bid_50bp_usd, fut_ob_ask_50bp_usd, ... }",
"ok": true,
"spot": [
{
"asof_day": "2026-06-18",
"asset": "BTC",
"ob_ask_100bp_usd": 11800000,
"ob_ask_200bp_usd": 23150000,
"ob_ask_50bp_usd": 5980000,
"ob_bid_100bp_usd": 12500000,
"ob_bid_200bp_usd": 24300000,
"ob_bid_50bp_usd": 6240000,
"spot_vol_1d_usd": 18420000000,
"spot_vol_30d_avg_usd": 15920000000,
"spot_vol_7d_avg_usd": 16850000000
},
{
"asof_day": "2026-06-19",
"asset": "BTC",
"ob_ask_100bp_usd": 12050000,
"ob_ask_200bp_usd": 23420000,
"ob_ask_50bp_usd": 6120000,
"ob_bid_100bp_usd": 12740000,
"ob_bid_200bp_usd": 24680000,
"ob_bid_50bp_usd": 6410000,
"spot_vol_1d_usd": 19105000000,
"spot_vol_30d_avg_usd": 15980000000,
"spot_vol_7d_avg_usd": 17020000000
}
]
}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-liquidity?asset=&days=0&include='
# 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-liquidity?asset=&days=0&include=' \
| 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-liquidity
const res = await pay("https://cryptyx.ai/api/asset-liquidity?asset=&days=0&include=");
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-liquidity?asset=&days=0&include=")
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 |
|---|---|---|---|---|
| 18 h ago | Expected HTTP 402, got 401 | 401 | 91 ms | - |
| 4 days ago | Expected HTTP 402, got 401 | 401 | 225 ms | - |
| 7 days ago | Expected HTTP 402, got 401 | 401 | 79 ms | - |
| 7 days ago | Expected HTTP 402, got 401 | 401 | 157 ms | - |
| 8 days ago | Expected HTTP 402, got 401 | 401 | 104 ms | - |
Show 10 older checks
| 8 days ago | Expected HTTP 402, got 401 | 401 | 299 ms | - |
| 8 days ago | Expected HTTP 402, got 401 | 401 | 80 ms | - |
| 8 days ago | Expected HTTP 402, got 401 | 401 | 51 ms | - |
| 8 days ago | Expected HTTP 402, got 401 | 401 | 78 ms | - |
| 9 days ago | Expected HTTP 402, got 401 | 401 | 45 ms | - |
| 9 days ago | Expected HTTP 402, got 401 | 401 | 107 ms | - |
| 9 days ago | Expected HTTP 402, got 401 | 401 | 91 ms | - |
| 9 days ago | Expected HTTP 402, got 401 | 401 | 115 ms | - |
| 9 days ago | Expected HTTP 402, got 401 | 401 | 75 ms | - |
| 10 days ago | Expected HTTP 402, got 401 | 401 | 66 ms | - |