Docs & manual

Three ways in: SQL, backtest, MCP. Everything runs on our side — you get results, not files. Below: the full path from first click to daily work, then the reference.

The full path, step by step

1. Evaluate for free. No card, no crypto, no promises: register with your email — a magic link arrives, no password to invent. The free plan gives one full hour of every stream (2026-08-18 12:00–13:00 UTC), SQL queries and backtest minutes — enough to check the data quality and the engine with your own hands. That trial is our refund policy: you know exactly what you buy before you pay.
2. Look around. Open the console, run a snippet from the library (candles from ticks, VWAP, CVD). Every stream has its own page with schema and live depth window — start at gold_trades_BTCUSDT.
3. Run your first backtest. On /backtest press «New», insert the example strategy, pick a window and symbols, hit Run. The report shows FARM vs buy-and-hold, per-regime breakdown and every trade. Failed run? The report shows the exact error line — fixing costs nothing, rejected runs do not burn minutes.
4. Connect your AI agent (optional, and honestly the best part): account → AI/MCP tab → copy the ready config for Claude/Cursor. Your agent gets catalog, SQL and the backtester as tools — it researches, you read reports. See MCP below.
5. Upgrade when the free window is tight. In account press «Upgrade» on a plan — an invoice opens with the exact USDT amount. Payment is USDT TRC20 on our own gateway's checkout page; see Paying in USDT.
6. Work daily. Quotas reset at UTC midnight; usage bars live in your account. Renewal adds 30 days to the later of «now» and your expiry — remaining days never burn. After expiry: 5 days of grace, then a soft drop to free. Your strategies and history stay.
7. Ask through tickets. Support is built in, with an SLA per plan — every question leaves a trail, nothing gets lost in a chat.

Paying in USDT (TRC20)

1. Press «Upgrade» in your account — the invoice shows the exact amount and opens our gateway's checkout page.
2. Send the exact amount in USDT on the TRON network (TRC20) — not ERC20, not BEP20. Any TRC20-capable wallet or exchange withdrawal works.
3. After network confirmation (typically 1–2 minutes) the gateway detects the payment and your plan activates automatically — no screenshots, no «contact admin».

Sent a wrong amount or the wrong network? Open a ticket with the transaction hash immediately — we see the chain and will sort out what is sortable. USDT transfers are irreversible, so double-check before sending. Full policy: Terms §4–5.

Quickstart (API)

No key yet? Download one free hour of SOL/USDT (L2 diffs, top of book, trades, 2026-08-18 12:00–13:00 UTC) and rebuild the order book yourself with the notebook — the same check our nightly job runs.

1. Register — a magic link, no password.
2. Create an API key in your account. It is shown once.
3. Ask the catalog:

   curl -H "X-API-Key: crk_…" https://data.cruscy.com/v1/catalog

SQL console

One statement per request, read-only, 30-second budget. The virtual column day selects files, so always constrain it:

SELECT time_bucket('1 min', ts) AS m,
       last(price) AS close,
       sum(qty)   AS vol
FROM gold_trades_ETHUSDT
WHERE day = '2026-08-10'
GROUP BY 1 ORDER BY 1

Free plan: one demo hour (2026-08-18 12:00–13:00 UTC; use day = '2026-08-18'). Paid plans: the window of your plan. day BETWEEN is not supported — use day IN (…).

Data dictionary

Column types come from the files themselves (every stream page shows them); the meaning of each column is on the stream page and in /v1/schema/<stream>. The conventions below hold for every stream — read them once, they save a wrong backtest.

Dictionary version 3. Every day is verified two ways before it is served: the order book is rebuilt from the diffs and compared with the independently recorded top of book, and the trade tape is compared trade-by-trade with Binance's public archive. Results per day: /status.

Strategy contract

The backtest runner calls analyze on every minute of the tape. Return None when there is no signal:

class Strategy:
    def analyze(self, symbol, data):
        if data.get("rsi") and data["rsi"] < 30:
            return {"side": "BUY", "size_pct": 50,
                    "custom_tp": data["price"] * 1.006,
                    "custom_sl": data["price"] * 0.996}
        return None

data['ladder'] is absent on purpose: the level ladder and smart exits are live-bot machinery and are not part of backtest contract v1. Your exits are your own custom_tp / custom_sl / hold. That is a deliberate decision: you are testing YOUR logic, not borrowing ours.

Allowed imports: numpy, pandas, math, statistics, collections. Anything else is rejected by the linter BEFORE the queue, so it costs you no minutes. Code runs in an isolated process with no network and no access to platform files.

How results are scored

FARM is measured IN COINS against buy-and-hold: 1.0 means you matched the hold, above means you beat it. A strategy that never trades sits in cash and honestly shows first_px/last_px — not 1.0.

MCP for AI agents

{"mcpServers": {"cruscy-data": {
  "url": "https://data-mcp.cruscy.com",
  "headers": {"Authorization": "Bearer crk_…"}}}}

Tools: catalog, stream schema, SQL query, backtest submit and report.

How a day becomes final

All times UTC. A day is sold as final only after the last step.

Until finalized_at is set, treat the day as provisional: data is complete and queryable, but the exchange cross-check has not run yet.

Limits and errors

Every error comes back in one envelope:

{"error": {"code": "daily_limit", "message": "…", "hint": "…"}}

Rejected requests do not burn your daily quota — only served ones do.