Start here

From a CRYPTYX card to your stack

Every CRYPTYX card, from the daily print to single-asset reads, is generated from the same endpoints you can call. Nothing on a card is hand-written. If a number is on the card, your systems can poll it, backtest it, or hand it to an agent.

What's on a card, and where it comes from

Readings are z-scores against each asset's own rolling history, with the daily anchor at the UTC close. Evidence is walk-forward backtested; samples below the publication floor are flagged. See methodology.

Path 1 · Pay per call with x402 (no account, works today)

Built for agents and quick evaluation. Pay fractions of a cent per call in USDC on Base. There's no signup and no key. The client caps total spend.

# Unpaid requests return HTTP 402 with machine-readable payment requirements
curl -i "https://cryptyx.ai/api/v1/harness/snapshot?scope=asset:SOL"

npm install @cryptyx/x402-client viem

// read-setups.ts — needs a Base wallet holding a few USDC
import { Cryptyx } from '@cryptyx/x402-client';

const cx = new Cryptyx({
  wallet: process.env.WALLET_PRIVATE_KEY as `0x${string}`,
  network: 'base',
  maxSpend: 1.0, // hard USD ceiling for this client
});

const snapshot = await cx.get('/api/v1/harness/snapshot', { scope: 'asset:SOL' });
const nearFire = await cx.get('/api/v1/harness/watchlist', { limit: 10 });
console.log(snapshot, nearFire, `spent $${cx.spent.toFixed(3)}`);

Full pricing and the payment flow: x402 payments.

Path 2 · API key (self-serve, free 30-day trial)

For desks wiring CRYPTYX into dashboards, risk systems or research notebooks. Sign up, start the free 30-day Pro trial, then create a key on your account page. Pro keys get 60 requests a minute plus the remote MCP server; Institutional gets 300. For higher limits or a desk agreement, email enterprise@cryptyx.ai.

export CRYPTYX_API_KEY="cx_your_key"

curl -s "https://cryptyx.ai/api/v1/harness/snapshot?scope=asset:SOL" \
  -H "Authorization: Bearer $CRYPTYX_API_KEY"

curl -s "https://cryptyx.ai/api/v1/tape/landscape?scope=asset:SOL" \
  -H "Authorization: Bearer $CRYPTYX_API_KEY"

Every endpoint, parameter and response shape: API reference.

Path 3 · Give it to your agent (MCP)

Connect Claude, ChatGPT or your own agent to the remote MCP server and ask in plain English, e.g. “what are SOL's most extreme readings and which setups are closest to firing?” Authenticate with an API key or OAuth.

{
  "mcpServers": {
    "cryptyx": {
      "url": "https://mcp.cryptyx.ai/api/mcp",
      "headers": { "Authorization": "Bearer cx_your_key" }
    }
  }
}

Client-by-client setup and the tool list: MCP server.

For information only. Not investment advice.