본문으로 건너뛰기

Strategies

Reference playbooks for crypto arbitrage and signal-driven trading strategies, paired with the DataMaxi+ endpoints that power them.

Each page is structured the same way: what it is, when it works, data you need, API recipe (cURL / Python / Go / TypeScript), risks & caveats, and further reading. Treat them as starting points, not turn-key bots. Real execution requires fee modeling, slippage analysis, and exchange-specific quirks that no public dataset can fully capture.

Strategy catalog

StrategyTypeDifficultyCapital requiredRisk profileRequired venue access
Kimchi PremiumCross-border arbHardHigh ($50k+)Settlement, regulatory, KRW liquidityKorean exchange (Upbit/Bithumb) + global CEX
Funding Rate ArbitrageDelta-neutral carryMediumMedium ($10k+)Funding regime flips, liquidation, basis blowoutOne CEX with spot + perp
Listing ArbitrageEvent-drivenHardMediumLatency, listing dump, withdrawal freezeKorean exchange + global CEX with the token already listed
CEX-CEX Spread (Premium)Spot price gapEasy-MediumLow-Medium ($5k+)Withdrawal fees, transfer time, network congestionTwo CEXs supporting the same asset/network
CEX-DEX ArbitrageCross-venue arbHardMedium-HighGas, MEV, bridge risk, oracle lagCEX + DEX wallet + bridges
Trend SignalsSentiment / leading indicatorMediumAnySignal decay, false positives, regime changeAny execution venue

How to choose

  • Capital constrained, low ops complexity ▸ start with CEX-CEX Spread on a single network you already understand.
  • You want yield, not directional betsFunding Rate Arbitrage. Delta-neutral, fewer surprises if you size risk properly.
  • You have KRW on a Korean exchangeKimchi Premium and Listing Arbitrage are uniquely accessible — and uniquely hard to size up.
  • You want alpha that isn't price-derivedTrend Signals. Combine with another strategy as a filter.
  • You can run infra and stomach MEVCEX-DEX Arbitrage.

Conventions used in every playbook

  • Base URL: https://api.datamaxiplus.com
  • Auth header: X-DTMX-APIKEY: $YOUR_API_KEY
  • All data-api endpoints are GET with query parameters; no request bodies.
  • Snippets use the four canonical languages: cURL, Python (requests), Go (net/http), TypeScript (axios).