← Platform/API & Webhooks
    For Desks · Quants · Builders

    Plug our signal into your stack.

    REST, WebSocket and historical replay for every alert SpotX produces. Ship signal infrastructure in a sprint instead of a year — same stream our own dashboard runs on.

    < 1 sprintTo integrate
    18 moReplay window
    1,000/sReq limit · Desk
    v1Stable schema
    curl
    $ curl https://api.spotx.io/v1/signals \ -H "Authorization: Bearer $TOKEN" \ -G --data-urlencode "chain=solana" \ --data-urlencode "min_score=80"
    // 200 OK · 142ms
    01 · Build vs buy

    Ship signal infrastructure in a sprint, not a year.

    Wallet labeling, cluster detection and a multi-chain ingest pipeline is a 12–18 month project for a four-engineer team. By the time you ship v1, the smart-money landscape has moved twice.

    We do the data and modeling. You do the differentiated layer — the part your traders, PMs or customers actually care about.

    Build it yourself
    12–18 months
    • Multi-chain ingest
    • Wallet labeling pipeline
    • Cluster detection model
    • Score calibration
    • Replay infrastructure
    • Provenance & audit log
    4 engineers · stale on day 1
    Use SpotX API
    A sprint
    • REST + WebSocket
    • Same stream as our dashboard
    • 18-month historical replay
    • Stable /v1/ schema
    • On-chain provenance per event
    • Audit-ready event log
    Ship the differentiated layer
    02 · The surface

    Three vectors. One contract.

    Same data, three ways to consume it. Pick the one that fits the workload — or use all three.

    REST
    Read everything

    Idempotent, paginated reads of every signal, cluster, wallet and label. Best for backfills, scheduled jobs and research.

    WebSocket
    Live push

    Every event streamed the moment it's scored. Filter by chain, severity, asset or wallet. Same connection our dashboard uses.

    Replay
    Time-travel

    Every signal we've ever produced is addressable by timestamp. Backtest the exact stream a live subscriber would have seen.

    API surface · three vectorsREST · WS · Replay
    SpotX CoreSIGNAL · LABEL · CLUSTERRESTGET /v1/signalsRequest / responseWebSocketWSS /v1/streamPush streamReplayGET /v1/historyHistorical backtest
    03 · The schema

    One object you can reason about in one sitting.

    Stable schema
    Versioned at /v1/. Breaking changes ship under /v2/ with a 6-month overlap.
    Idempotency keys
    Every event has a stable ID. Safe to replay, dedupe and reconcile.
    Full provenance
    Every signal includes the on-chain hashes that produced it. Verify independently.
    Audit log
    Desk-tier accounts get a tamper-evident log of every API read for compliance review.
    GET /v1/signals · 200 OK
    {
      "id": "sig_01HXM7Z9K...",
      "type": "cluster",
      "chain": "solana",
      "asset": { "symbol": "WIF", "mint": "EKpQGSJ..." },
      "score": 94,
      "severity": "high",
      "detected_at": "2026-04-21T03:42:54Z",
      "delivered_at": "2026-04-21T03:43:08Z",
      "wallets": [
        { "id": "w_a3f9", "score": 92, "notional_usd": 18400 },
        { "id": "w_b21c", "score": 87, "notional_usd": 22100 },
        { "id": "w_c7e0", "score": 81, "notional_usd": 31800 }
      ],
      "reasoning": ["tight_window:54s", "graph_link:bridge_base"],
      "provenance": { "tx_hashes": [...], "block_heights": [...] }
    }
    04 · Worked example

    Subscribe in five lines. Trade in twenty.

    That's a complete production subscriber. Add reconnection, your own risk checks and an idempotency cache around sig.id — and you have a signal-driven execution loop with the same latency profile as our own dashboard.

    subscriber.ts
    import WebSocket from "ws";
    
    const ws = new WebSocket("wss://api.spotx.io/v1/stream", {
      headers: { Authorization: `Bearer ${process.env.SPOTX_TOKEN}` },
    });
    
    ws.on("open", () => {
      ws.send(JSON.stringify({
        subscribe: { chain: "solana", min_score: 85, types: ["cluster"] }
      }));
    });
    
    ws.on("message", (raw) => {
      const sig = JSON.parse(raw.toString());
      myExecutor.consider(sig);
    });
    05 · What you can build

    Four shapes teams ship first.

    Execution bots

    Wire scored alerts directly into your trading stack, each carrying the triggering transaction hash.

    Internal dashboards

    Build the trader/PM view your team actually wants — on top of our labels and clusters.

    Research notebooks

    Backtest strategies against the real, replayable signal history. No look-ahead bias.

    Monitoring & risk

    Alert when a tracked wallet, asset or cluster behaves outside your fund's risk envelope.

    Included in

    Included in Pro and Desk.

    Pro includes REST and WebSocket with 100 req/s and 30-day replay. Desk lifts limits to 1,000 req/s, 18-month replay, dedicated channel and an SLA-backed uptime credit.