Resource Manifest — AI Quantitative Trading Competition

Everything a participant receives or needs to access for the competition.

---

1. Competition Account

Each participant receives a dedicated account. Log in at https://www.liquiditytech.com/ (Phase II Mainnet / Track B RapidX) or https://uat.liquiditytech.com/ (Phase I Sandbox) and generate your API credentials under Profile → API Management → Generate.

API Key permissions:

Phase II Onboarding: During the preparation phase, teams provide their deposit address to the Organizing Committee, who will fund the account with 1,000 USDT initial capital on their behalf.

Account Restrictions: Once the main competition begins, self-service deposits and withdrawals are disabled — the deposit API is banned. Transfers between Binance and OKX within RapidX are permitted, as all teams trade exclusively on RapidX. This applies to both Track A and Track B.

Treat your credentials as production secrets — never commit, log, or share them.

---

2. Service Endpoints

See 03-advanced-api.md for authentication, signature algorithm, and full endpoint reference.

The competition REST/WS hosts resolve to the official production API. Use https://api.ltp-contest.com throughout.

For programmatic access, see Leaderboard API.

Market Data WebSocket Rate Limits

Authenticate with your competition API Key to reach the higher limits. Limits are counted by trading pair, not by channel — subscribing to BBO + TICKER + TRADE for the same symbol counts as 1 pair.

News Feed WebSocket Connection Limits

Reconnection note: subscription state is not preserved on the server. After a reconnect, you must re-send the subscribe message for all channels.

---

3. npm Packages

See 01-quickstart.md §Step 1 for install and registry troubleshooting.

Run rapidx --version after install to confirm the version.

If npm maps @liquiditytech to a custom registry, point it to the official registry first:

npm config set @liquiditytech:registry https://registry.npmjs.org/
npm install -g @liquiditytech/rapidx-cli@latest

---

4. Skills

See 01-quickstart.md §Step 3 Path A for per-agent-host install commands (Claude Code, Codex, Cursor, OpenClaw, Hermes).

---

5. CLI & MCP Tool Catalogue

See 02-cli-mcp-reference.md for full input/output specs, the preview-then-submit pattern, and automation mode.

All CLI commands use the format rapidx <domain> <action> --input '<json>' --json.
All MCP tools use the rapidx/ prefix.

Discovery & Diagnostics

Market Data

Portfolio

Orders (preview required for all writes)

Transactions

Positions (preview required for writes)

Algo Orders (preview required for writes)

Automation Sessions

Trade Utilities

Full input/output specifications: 02-cli-mcp-reference.md.

---

6. Symbol Universe

Track A — Tradable Pairs Whitelist (Phase I)

Glossary: PERP = perpetual futures (a derivative that tracks an asset price with no expiry). USDT-margined = margin and PnL are settled in USDT (not the underlying asset).

• 50 pairs, USDT-margined Binance perpetuals, format: BINANCE_PERP_{BASE}_USDT
• Fixed for the competition period; not dynamically adjusted by market cap
• Selection criteria: Binance USDT perp ✓ | System whitelist ✓ | Listed ≥ 6 months (CoinGecko) ✓

Check symbol rules before trading: minimum notional, lot size, tick size, and contract size vary by symbol. Run rapidx market get-symbol-info --input '{"symbol":"..."}' --json before sizing any order.

Phase II Scope Expansion: In Phase II, tradable instruments remain limited to perpetual swaps (Perpetual Swaps), but the range expands from Binance-only to either Binance or OKX perpetual contracts. Maximum opening leverage is relaxed to ≤ 5x (Phase I: ≤ 2x).

Rate Limits

---

7. Documentation

---

8. Verification

Use the built-in CLI self-check — no extra dependencies required:

rapidx auth check
rapidx self-check --read-only --json

Each check reports PASS / EXPECTED_ERROR / FAIL / NOT_VERIFIED.

For an end-to-end live trade test (submits a real post-only order then cancels):

rapidx trade verify-live --input '{
  "symbol": "BINANCE_PERP_BTC_USDT",
  "side": "BUY",
  "maxNotional": "10",
  "clientOrderId": "verify-live-001",
  "explicitUserConsent": true,
  "acceptedRiskText": "I authorize a real verification order for BINANCE_PERP_BTC_USDT BUY maxNotional 10 with cancel cleanup."
}' --json

---

9. Competition Structure & Schedule

Schedule & Timeline

Track A: Logic Frontier

Track A runs in two phases. Phase I scores do NOT carry over to Phase II. Phase II resets all teams' NAV; LTP allocates 1,000 USDT live seed capital per team. The top 30 teams from Phase I advance.

Phase II — Mainnet Duel Finals

• Tradable instruments: Binance OR OKX perpetual swaps (Phase I was Binance only)
• Leverage limit: max 5x (Phase I: 2x)
• Elimination trigger: Equity < 800 USDT → forced liquidation + immediate elimination
• Scoring: ROI (20%) + PnL (25%) + Sharpe Ratio (40%) + MDD (15%) + AI Agent Reference Metrics (AI-Adjusted PnL, AI Engagement)
• Core evaluation: institutional-grade trading performance + Reasoning Log logical quality

Track B: Liquidity Pro

Account Restrictions (applies to all Track B participants): Once the main competition begins, self-service deposits and withdrawals are disabled — the deposit API is banned. Transfers between Binance and OKX within RapidX are permitted, as all teams trade exclusively on RapidX. See §1 for the Phase II onboarding funding flow.

For quant hedge funds and professional trading teams. Focus: HFT execution quality, multi-factor alpha discovery, ML/DL alpha capture in deep liquidity.

• Scoring: Sharpe Ratio (45%) + PnL (30%) + Scaling Capacity (10%) + MDD (15%)
• Strategy-agnostic; unified leaderboard (arbitrage, trend-following, CTA, HFT, market-making, AI Agent-driven)

Participation Paths

• Asset classes: Spot, Perpetual Futures, Delivery Futures, Options, OTC. Profits from low-liquidity or abnormal-volatility assets are excluded from the final score.
• Capital efficiency (Path B): unified account, shared margin across CEX/DEX/OTC/traditional exchanges, cross-market settlement.

Scaling Effect Tiers (Track B)

Fee Policy

• Clearing Fee Minimum Charge: waived for all teams.
• Track A: VIP 5-level trading fees.

---

10. Scoring Methodology

Sharpe Ratio

• Sampling: daily snapshots (not hourly)
• daily_return[d] = NAV[UTC 23:00] / NAV[UTC 00:00] − 1
• Only fully completed days are counted; the current in-progress day is excluded
• Recalculated at 00:00 UTC daily; NULL until ≥ 2 complete days
• Formula: Sharpe = AVERAGE(daily_returns) / STDEV(daily_returns) × √365
• Risk-free rate: 0; annualization: √365 (calendar days)
• Sharpe may be negative even when PnL/ROI is positive (inactive/loss days drag the average)

Cross-Team Normalization

• The leaderboard displays the raw Sharpe
• Composite ranking: Z-Score → CDF percentile within the eligible pool (non-eliminated teams), then weighted
• Track A composite = 0.40 × S(Sharpe) + 0.25 × S(PnL) + 0.20 × S(ROI) + 0.15 × MDD Tier Score

Elimination Recomputation

• Forward-only from the elimination point, NOT retroactive
• An eliminated team's pre-elimination scoring data remains valid; subsequent performance is excluded from the eligible pool
• Remaining teams are recomputed against the reduced pool

MDD (Max Drawdown)

• Formula: MAX((running_peak[t] − nav[t]) / running_peak[t]) across all t
• 24 hourly snapshots/day (00:00–23:00 UTC)
• Monotonically non-decreasing — does not recover even if NAV bounces back
• The system uses minute/tick-level equity internally; ~0.05% deviation from the hourly calculation is expected

---

11. Leaderboard

• URL: https://arena.liquiditytech.com/leaderboard
• Note: some statistics require a full completed trading day (T+1) to compute accurately; early data may still be catching up

Track A columns

Track B columns

---

12. AI API & Token Usage (Track A)

• LLM Model: MiniMax M3
• Daily budget: $10 USD per team per day; unused tokens expire at end of day with no rollover; the next day re-issues $10
• Cache TTL: 5 minutes — use caching to control cost

Pricing Table

Compliance Rules

• Teams must exclusively use the Organizer-provided AI API throughout the competition. Third-party or self-hosted AI APIs in the trading decision chain are prohibited → immediate disqualification + invalidation of all results.
• Compliance review covers ALL usage levels (no de minimis threshold; negligible-but-nonzero usage is also reviewed).
• AI must be the primary decision driver — processing unstructured info (news, policy, social sentiment) and producing substantiated trading decisions. Using AI merely as a pre-trade gate check or logger does NOT qualify.
• Development tools (Cursor / ChatGPT / GitHub Copilot) for coding/debugging are NOT restricted.

Query AI Usage

GET https://ai.ltp-contest.com/key/info
Authorization: Bearer <your-ai-api-key>

Returns the cumulative USD spend for the current AI API Key.

# Check AI usage before running agent
curl -s https://ai.ltp-contest.com/key/info \
  -H "Authorization: Bearer <your-ai-api-key>"

Best practice: after validating your strategy logic, run your MCP-based agent as a background scheduled script rather than interactively. This avoids redundant token usage from repeated manual invocations.

---

13. Reasoning Log (Track A)

• Submit after Track A Phase I ends; covers every order/trade operation (place, cancel, open, close) with the Agent's full reasoning, decision basis, and result
• Submission deadline: Aug 24, 23:59 (GMT+8) — send to [email protected]
• Failure to submit may affect your team's final eligibility to advance to the next stage
• Historical gaps: submit as-is and note the gap (state when complete model reasoning was introduced; prior ops relied on rule-based logic) — do NOT retroactively reconstruct
• Exchange-triggered exits (TPSL auto-fill): reasoning is required for the placement decision, NOT for the auto-execution
• Granularity: same-strategy batch trades may share one reasoning record; AI must continuously participate as the decision/explanatory agent throughout the competition — not a one-time intervention

---

14. Support

For competition support, reach out via:

• Telegram: Liquidity Arena #1
• Email: (contact the organizing team)

---

15. Safety & Compliance Reminders

1. No real assets at risk (Phase I) — Phase I runs on the competition simulation environment with virtual capital.
2. Elimination threshold — Elimination is triggered when Equity < 800 USDT.
3. Agent uptime ≥ 90% — uptime below 90% results in disqualification; 90–95% incurs graduated score penalties.
4. Preview before every write — all writes require preview; the preview never submits a real order.
5. LTP_API_HOST is required — missing host returns RCORE01003.
6. State confirmation after every write — call rapidx order query or rapidx position query. No blind retries.
7. Secrets never leak — keys are masked in all CLI/MCP output, logs, and reports.