The entry point for agents landing on CRYPTYX
The entry point for agents landing on CRYPTYX. Returns the full signal registry (every atomic and composite signal, all versions) with class, horizon, geometry, parameters, 30-day trigger stats, three-axis health grades, walk-forward IS/OOS — plus a meta.serv…
by cryptyx.ai · discovered, not yet claimed by its owner · updated 2026-10-08
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
The entry point for agents landing on CRYPTYX. Returns the full signal registry (every atomic and composite signal, all versions) with class, horizon, geometry, parameters, 30-day trigger stats, three-axis health grades, walk-forward IS/OOS — plus a meta.service block (universe + walk-forward + macro-regime + OKX/Kraken/Coinbase venues), a meta.by_class strategy-family breakdown, a meta.next recommended 5-step flow, and per-signal _actions with direct URLs to explain / backtest / fork / simulate. One call answers "what is CRYPTYX, what can I buy, and what should I call next". Signal evaluations run across the CRYPTYX 200+ tracked digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.
Tags: crypto · trading · signals · intelligence · agents · bazaar
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/29750.jsonfor the price and payment options. - Pay. Call
GET https://cryptyx.ai/api/signals/catalog. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Calls (30d)
- 12 · 5 unique payers (third-party data from the public x402 Bazaar)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x0cD2c9724F185a029101b4AEACf3F114415c394f | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x0cD2c9724F185a029101b4AEACf3F114415c394f",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://cryptyx.ai/api/signals/catalog"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://cryptyx.ai/api/signals/catalog");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://cryptyx.ai/api/signals/catalog")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- cryptyx.ai
- Endpoint
- https://cryptyx.ai/api/signals/catalog
- Machine-readable
/resources/29750.json