Exchanges
Supported spot exchanges and transfer networks
Supported crypto exchanges depend on stable data access, explainable fees, and route-state visibility. Market data availability does not mean every asset, common network, or transfer direction is available.
No auto-trading, no custody, and no profitability promise.
spot exchange data sourcesCoverage surface
Observe spot books, depth, and route state across supported exchanges without connecting an exchange account or providing API keys.
MEXCGateLBankHTXBitgetBitMartBybitKuCoinXT
- spot exchange data sources
- 9+
- first-round order-book depth preview
- depth5
Coverage surface
20-minute trial alert preview
Public trial · shows up to 3 alerts from the last 20 minutes, delayed by at least 5 minutes. It demonstrates the format, not live market data or final profit.
| Symbol | Buy | Sell | Est. value | Spread | Delay | Route |
|---|---|---|---|---|---|---|
| ABC/USDT | MEXC | Gate | 8.25 U | 42 bps | 5m delayed | Open |
| TKN/USDT | Bitget | KuCoin | 6.80 U | 35 bps | 8m delayed | Review |
| XYZ/USDT | HTX | BitMart | 5.40 U | 29 bps | 13m delayed | Cooling |
9+
Coverage surface
Observe spot books, depth, and route state across supported exchanges without connecting an exchange account or providing API keys.
- 01MEXC
- 02Gate
- 03LBank
- 04HTX
- 05Bitget
- 06BitMart
- 07Bybit
- 08KuCoin
- 09XT
Coverage principles
Priority goes to spot exchanges with relatively stable order books, usable APIs, explainable fee assumptions, and route-state checks.
Route status
Alerts should show deposit, withdrawal, network status, and known restrictions where available. Disabled or cooling routes must not be treated as available because a snapshot is missing.
Limitations
API limits, exchange maintenance, abnormal order books, network congestion, and paused deposits or withdrawals can all affect alert quality. Users should recheck exchange pages before trading.
Cross-exchange spot opportunity alerts
Route status
Alerts should show deposit, withdrawal, network status, and known restrictions where available. Disabled or cooling routes must not be treated as available because a snapshot is missing.