The intelligence layer for autonomous trading agents.

60 paid endpoints. USDC micropayments on Base. No account, no API key, no rate cards. Your agent signs a gasless ERC-3009 transfer, gets institutional-grade intelligence back, and the response tells it exactly what to call next.

The universe you're buying access to

Walk-forward validated. Macro-regime aware. Complementary to exchange execution toolkits — CRYPTYX is the brain, exchanges are the rails.

Where agents find CRYPTYX

The 5-step agent workflow

This is the recommended flow every response of /api/signals/catalog hints at via its meta.next block. Every step is $0.01–$0.10 — an agent can complete the full loop for under $0.20.

Signal strategy families

143 atomic signals grouped by factor class. Every catalog response returns this breakdown in meta.by_class so agents pick a strategy family instead of scanning 143 rows.

How the 402 flow works

Pricing

60 endpoints across 4 tiers. All prices in USD, settled in USDC on Base. Machine-readable at /.well-known/x402.

Quick start

The fastest path is Coinbase's Agentic Wallet CLI (awal). If you're building from scratch, the raw SDK snippet at the bottom shows the full 402-handshake explicitly.

# Install + sign in (one-time)
npx skills add coinbase/agentic-wallet-skills
npx awal auth login <your-email>

# Fund your wallet with USDC on Base
npx awal show

# Pay + query CRYPTYX in one command
npx awal x402 pay https://cryptyx.ai/api/signals/catalog

import { privateKeyToAccount } from 'viem/accounts';
import axios from 'axios';
import { wrapAxiosWithPaymentFromConfig } from '@x402/axios';
import { ExactEvmScheme } from '@x402/evm';

const account = privateKeyToAccount(process.env.WALLET_KEY as `0x${string}`);
const api = wrapAxiosWithPaymentFromConfig(
  axios.create(),
  { schemes: [{ network: 'eip155:*', client: new ExactEvmScheme(account) }] },
);

// Handshake + settle + fetch happens under the hood
const { data } = await api.get('https://cryptyx.ai/api/signals/catalog');

console.log(data.meta.service.tagline);   // "The intelligence layer for autonomous trading agents"
console.log(data.meta.by_class);          // { TR: 33, OB: 33, CORR: 21, ... }
console.log(data.meta.next.recommended_flow); // 5-step agent workflow
console.log(data.signals[0]._actions);    // { explain: "...", backtest: "...", fork_variant: "...", simulate_threshold: "..." }

curl -i https://cryptyx.ai/api/signals/catalog
# → HTTP 402 with payment-required header (base64-decode to see the full payload schema)

What you get back

Every response is structured so an agent can act without external docs. Here's the shape of GET /api/signals/catalog — the entry point.

{
  "ok": true,
  "count": 143,
  "meta": {
    "ic_context": "cross_sectional",
    "service": {
      "name": "CRYPTYX",
      "tagline": "The intelligence layer for autonomous trading agents",
      "universe": { "assets": 200, "metrics": 442, "signals_atomic": 143, "signals_composite": 9, "factor_classes": 8, "horizons": 8, "history_years": 5 },
      "walk_forward_validated": true,
      "macro_regime_aware": true,
      "execution_venues": ["OKX", "Kraken", "Coinbase"]
    },
    "by_class": {
      "TR":   { "count": 33, "one_liner": "Trend + momentum signals" },
      "OB":   { "count": 33, "one_liner": "Order book depth + imbalance" },
      "CORR": { "count": 21, "one_liner": "Cross-asset correlation regimes" },
      "OPT":  { "count": 17, "one_liner": "Options implied vol + skew" },
      "FUT":  { "count": 16, "one_liner": "Futures funding + open interest" },
      "EFF":  { "count": 16, "one_liner": "Price efficiency + reversal setups" },
      "VOL":  { "count": 13, "one_liner": "Volatility regime + compression" },
      "FLOW": { "count": 11, "one_liner": "Order flow + taker aggression" }
    },
    "next": {
      "recommended_flow": [
        "1) Pick 1-3 signals whose class + horizon match your hypothesis.",
        "2) GET /api/signals/top — the 10 highest-IC signals right now.",
        "3) GET /api/signals/explain?signal_id={id}&day={YYYY-MM-DD}&asset={SYMBOL}.",
        "4) POST /api/signals/backtest — validate over 5+ years.",
        "5) GET /api/v1/ai/trade-ideas — bundled starter pack for autonomous execution."
      ]
    }
  },
  "signals": [
    {
      "signal_id": "TR_MOMO_CONT_14D",
      "name": "Trend Momentum Continuation 14D",
      "class": "TR",
      "horizon": "14D",
      "health_grade": "A",
      "walk_forward": { "is_ic": 0.10, "oos_ic": 0.07, "reliability_grade": "green" },
      "_actions": {
        "explain": "GET /api/signals/explain?signal_id=TR_MOMO_CONT_14D&day={YYYY-MM-DD}&asset={SYMBOL}  ($0.01)",
        "backtest": "POST /api/signals/backtest  body={signal_id:'TR_MOMO_CONT_14D', from:'YYYY-MM-DD', to:'YYYY-MM-DD'}  ($0.05)"
      }
    }
    // ... 142 more
  ],
  "durationMs": 842
}

Every paid endpoint (55 of 56) returns a canonical _next.hints block with 3–5 targeted follow-up endpoints, each labelled with price and one-line reasoning. Every response is envelope-shaped — { ok, ..., _next } — so agents can rely on one contract across the entire surface.

Requirements

Execution — meet your agent where it lives

x402 is protocol-neutral. CRYPTYX is venue-neutral. Your agent pays for conviction on Base, then executes wherever it makes sense — the exchange with the best liquidity, the tightest spreads, the right regulatory posture, or the deepest agent-native rails. We ship five reference handshakes to make this concrete. Each shows the same three-step pattern: pay CRYPTYX → apply institutional gate → execute on the venue's API. Fork any of them.

Each file is a self-contained ~150-line reference implementation. The CRYPTYX side is identical across all five (SDK call + institutional gate); only the final placeOrder(...) differs. Adding a sixth venue is trivial — same pattern, swap the exchange adapter. If you're on a venue we haven't covered, use one of these as a template.