Blave Quant Skill

Five capabilities: Blave market alpha data, BitMart trading, OKX trading, Bybit trading, BingX trading.

Examples

Workflow templates for common use cases. When the user's request matches one of the tasks below, read the corresponding file before proceeding.

File	When to read
INLINECODE0	User wants to find traders to follow / copy trade on Hyperliquid
INLINECODE1

User wants to screen or find high-conviction / small-cap tokens |
| examples/backtest-holder-concentration.md | User wants to backtest a strategy using Blave alpha signals |

Output Rule — Chart Auto-Send

Whenever you generate a chart or visualization, send it through the user's notification channel (e.g., Telegram) if and only if the user has explicitly configured one in their environment. Only send to the channel the user themselves set up — never infer or guess an endpoint. If no channel is configured, display the chart inline as usual.

PART 1: Blave Market Data

Setup

No API key or 401/403 → guide user to:

- Subscribe: https://blave.org/landing/en/pricing — $629/year, 14-day free trial
Create key: https://blave.org/landing/en/api?tab=blave

Add to .env: blave_api_key=... and INLINECODE5

Auth headers: api-key: $blave_api_key | INLINECODE7

Base URL: https://api.blave.org | Support: info@blave.org | Discord

Limits

Item	Value
Rate limit	100 req / 5 min — `429` if exceeded, resets after 5 min
Data update

Usage Guidelines

- Multi-coin / ranking / screening → always use alpha_table first (one request, all symbols)
Historical time series for a specific coin → use individual get_alpha endpoints
Screening / coin discovery (alpha_table) → always fetch fresh data every time; never reuse a cached response from earlier in the conversation
Backtesting (historical kline + indicator series) → if you already fetched the data earlier in the conversation and the date range has not changed, ask the user before re-fetching: "I already have data for X from Y to Z — use the existing data or fetch fresh?"

Endpoints

`GET /alpha_table` — All symbols, latest alpha, no params

Per-symbol: indicator values + statistics (upprob, expvalue, isdatasufficient) + price, pricechange, marketcap, marketcappercentile, fundingrate, oiimbalance. "" = insufficient data. → Full field reference: references/blave-api.md

`GET /kline` — OHLCV candles

INLINECODE17✓, period✓ (5min/15min/1h/4h/8h/1d), start_date, end_date
→ [{time, open, high, low, close}] — time is Unix UTC+0

period format: {number}{unit} — unit: min / h / d. Examples: 15min, 1h, 4h, 1d, 7d, 30d.

Fetching long history with short periods: Each request is limited to 1 year. For short periods (e.g. 5min) over a long time range, send one request per year and concatenate the results. Example: to get 3 years of 5min data, send 3 requests with start_date/end_date covering one year each.

`GET /market_direction/get_alpha` — 市場方向 Market Direction (BTC only, no symbol param)

INLINECODE43✓, start_date, end_date → INLINECODE46

`GET /market_sentiment/get_alpha` — 市場情緒 Market Sentiment

INLINECODE48✓, period✓, start_date, end_date → INLINECODE52

`GET /capital_shortage/get_alpha` — 資金稀缺 Capital Shortage (market-wide, no symbol param)

INLINECODE54✓, start_date, end_date → INLINECODE57

`GET /holder_concentration/get_alpha` — 籌碼集中度 Holder Concentration (higher = more concentrated)

INLINECODE59✓, period✓, start_date, end_date → INLINECODE63

`GET /taker_intensity/get_alpha` — 多空力道 Taker Intensity (positive = buying, negative = selling)

INLINECODE65✓, period✓, timeframe (15min/1h/4h/8h/24h/3d), start_date, INLINECODE75

`GET /whale_hunter/get_alpha` — 巨鯨警報 Whale Hunter

INLINECODE77✓, period✓, timeframe, score_type (score_oi/score_volume), start_date, INLINECODE84

`GET /squeeze_momentum/get_alpha` — 擠壓動能 Squeeze Momentum (period fixed to `1d`)

INLINECODE87✓, start_date, end_date → includes scolor (momentum direction label)

`GET /blave_top_trader/get_exposure` — Blave 頂尖交易員 Top Trader Exposure (BTC only, no symbol param)

INLINECODE92✓, start_date, end_date → INLINECODE95

`GET /sector_rotation/get_history_data` — 板塊輪動 Sector Rotation, no params

All get_alpha responses include stat: up_prob, exp_value, avg_up_return, avg_down_return, return_ratio, INLINECODE104

Each indicator also has a get_symbols endpoint to list available symbols.

Screener

`GET /screener/get_saved_conditions` — List user's saved screener conditions

No params. Returns {data: {<condition_id>: {filters: [...], ...}}} — a map of condition IDs to their filter configs.

`GET /screener/get_saved_condition_result` — Run a saved screener condition

INLINECODE109✓ (integer) → INLINECODE110

Returns 400 if condition_id is missing or not an integer; 404 if condition not found for user.

Hyperliquid Top Trader Tracking

Full response formats: INLINECODE112

Endpoint	Params	Cache
INLINECODE113	INLINECODE114 (accountValue/week/month/allTime)	5 min
INLINECODE115

— | — | | GET /hyperliquid/trader_position | address✓ → perp positions, spot balances, net_equity | 15 s | | GET /hyperliquid/trader_history | address✓ → fills with closedPnl, dir | 60 s | | GET /hyperliquid/trader_performance | address✓ → {chart: {timestamp, pnl}} cumulative PnL | 60 s | | GET /hyperliquid/trader_open_order | address✓ → open orders | 60 s | | GET /hyperliquid/top_trader_position | — → aggregated long/short across top 100 | 5 min | | GET /hyperliquid/top_trader_exposure_history | symbol✓, period✓, dates | — | | GET /hyperliquid/bucket_stats | — → stats by account size bucket; 202 while warming up | ~5 min |

TradingView Signal Stream (SSE)

Receive TradingView alerts in real time via Server-Sent Events.

Endpoint: INLINECODE130

Event format: data: {"id": "1712054400000-0", ...alert_fields}

- id — pass as last_id on reconnect to resume without losing signals
Default (last_id=$) — only new signals; omit on first connect
INLINECODE135 sent every 15 s — ignore
Buffer: last 1000 messages in Redis — short disconnections lose no data

Full Python example with reconnect loop: references/tradingview-stream.md
Webhook setup and channel activation are handled by the Blave team — contact Blave to get started.

Python examples: references/blave-api.md
Indicator interpretation: INLINECODE138

PART 2: BitMart Futures Trading

Base URL: https://api-cloud-v2.bitmart.com | Symbol: BTCUSDT (no underscore) | Success: INLINECODE141

53 endpoints — full details in INLINECODE142

Authentication

Credentials (from .env): BITMART_API_KEY, BITMART_API_SECRET, INLINECODE146

No BitMart account? Register at https://www.bitmart.com/invite/cMEArf

Verify credentials before any private call. If missing — STOP.

Level	Endpoints	Headers
NONE	Public market data	—
KEYED

Signature: HMAC-SHA256(secret, "{timestamp}#{memo}#{body}") — GET body = INLINECODE152

Always include X-BM-BROKER-ID: BlaveData666666 on ALL requests.

IP Whitelist: Use public IP (curl https://checkip.amazonaws.com), not private IP (10.x, 172.x, 192.168.x).

Signature Python implementation and common mistakes: INLINECODE158

Operation Flow

Step 0: Credential Check

Verify BITMART_API_KEY, BITMART_API_SECRET, BITMART_API_MEMO. If missing — STOP.

Step 1.1: Query Positions (READ)

INLINECODE162 (KEYED, no signature needed)
Filter current_amount != "0" → display symbol, positionside, currentamount, entryprice, leverage, opentype, liquidationprice, unrealizedpnl

Step 1.5: Pre-Trade Check (MANDATORY before open/leverage)

1. Call INLINECODE164
If current_amount non-zero → inherit leverage and open_type, do NOT override
If user wants different values → STOP, warn to close position first

Step 1.55: Pre-Mode-Switch Check

Confirm no positions (Step 1.5) AND no open orders (GET /contract/private/get-open-orders). If either exists → STOP.

Step 1.6: TP/SL on Existing Position

INLINECODE169 — submit TP and SL as two separate calls

Param	Value
INLINECODE170	INLINECODE171 or INLINECODE172
INLINECODE173

Step 2: Execute

- READ → call, parse, display
WRITE → present summary → ask "CONFIRM" → execute

submit-order rules:

Scenario	Send	Omit
Open, market	symbol, side, type:`"market"`, size, leverage, opentype	price
Open, limit

Step 3: Verify

- After open: position-v2 → report entry price, size, leverage, liquidation price
After close: position-v2 → report realized PnL
After order: GET /contract/private/order → confirm status

Order Reference

Side: 1 Open Long / 2 Close Short / 3 Close Long / 4 Open Short

Mode: 1 GTC / 2 FOK / 3 IOC / 4 Maker Only

Timestamps: ms — always convert to local time for display.

Error Handling

Code	Action
30005	Wrong signature → see INLINECODE199
30007

Spot ↔ Futures Transfer

Present summary → ask "CONFIRM" → execute.

Endpoint: POST https://api-cloud-v2.bitmart.com/account/v1/transfer-contract (SIGNED)

Param	Value
INLINECODE201	INLINECODE202 only
INLINECODE203

transfer amount |
| type | "spot_to_contract" or "contract_to_spot" |

Rate limit: 1 req/2sec. ⚠️ /spot/v1/transfer-contract does NOT exist.

Security

- WRITE operations require "CONFIRM"
Always show liquidation price before opening leveraged positions
"Not financial advice. Futures trading carries significant risk of loss."

References

- references/bitmart-api-reference.md — 53 endpoints
INLINECODE209 — Python signature implementation
INLINECODE210 / bitmart-close-position.md / bitmart-plan-order.md / INLINECODE213

PART 3: BitMart Spot Trading

Base URL: https://api-cloud.bitmart.com | Symbol: BTC_USDT (underscore) | Success: INLINECODE216

34 endpoints — full details in INLINECODE217

Authentication

Same signature method as Futures. Credentials from .env: BITMART_API_KEY, BITMART_API_SECRET, INLINECODE221

No BitMart account? Register at https://www.bitmart.com/invite/cMEArf

Always include X-BM-BROKER-ID: BlaveData666666 on ALL requests.

IP Whitelist: Use public IP (curl https://checkip.amazonaws.com), not private IP.

Signature Python implementation: INLINECODE224

Operation Flow

Step 0: Credential Check

Verify credentials. If missing — STOP.

Step 1: Identify Intent

- READ: market data, balance, order history
WRITE: submit/cancel orders, withdraw
TRANSFER: spot ↔ futures → see Part 2 Spot ↔ Futures Transfer

Step 2: Execute Orders

- READ → call, parse, display
WRITE → present summary → ask "CONFIRM" → execute

Endpoint: POST /spot/v2/submit_order

Scenario	side	type	Key param
Buy, market	INLINECODE226	INLINECODE227	INLINECODE228 (USDT to spend)
Buy, limit

Market buy uses notional, NOT size.

Step 3: Verify

After order → query order detail. After cancel → check open orders.

Order Reference

Side: buy / sell | Type: limit / market / limit_maker / INLINECODE247

Status: new / partially_filled / filled / canceled / INLINECODE252

Timestamps: ms — always convert to local time.

Error Handling

Code	Action
30005	Wrong signature → see INLINECODE253
30007

Security

- WRITE operations require "CONFIRM"
"Not financial advice. Spot trading carries risk of loss."

References

- references/bitmart-spot-api-reference.md — 34 endpoints
INLINECODE255 — Python signature implementation
INLINECODE256 / INLINECODE257

PART 4: OKX Trading

Base URL: https://www.okx.com | Spot: BTC-USDT | Swap: BTC-USDT-SWAP | Success: INLINECODE261

Full details in INLINECODE262

Authentication

Credentials (from .env): OKX_API_KEY, OKX_SECRET_KEY, INLINECODE266

No OKX account? Register at https://okx.com/join/58510434

Verify credentials before any private call. If missing — STOP.

Signature: Base64(HMAC-SHA256(secret, timestamp + METHOD + requestPath + body))

- timestamp format: 2024-01-01T00:00:00.000Z (ISO 8601 ms UTC)
GET body = INLINECODE270

Headers: OK-ACCESS-KEY + OK-ACCESS-SIGN + OK-ACCESS-TIMESTAMP + OK-ACCESS-PASSPHRASE + INLINECODE275

User-Agent is required on ALL OKX requests. Omitting it returns 403 Error code 1010.

Broker code: "tag": "96ee7de3fd4bBCDE" — MANDATORY on every POST that creates or modifies an order. No exceptions. If you write a POST body and forget tag, stop and add it before sending.

Operation Flow

Step 0: Credential Check

Verify OKX_API_KEY, OKX_SECRET_KEY, OKX_PASSPHRASE. If missing — STOP.

Step 1: Pre-Trade Check (Swap only)

GET /api/v5/account/positions?instId=<SYMBOL>-SWAP → if position exists, inherit tdMode and leverage.

Step 2: Execute

- READ → call, parse, display
WRITE → present summary → ask "CONFIRM" → execute

Step 3: Verify

After order → GET /api/v5/trade/order → confirm status. After close → GET /api/v5/account/positions.

Security

- WRITE operations require "CONFIRM"
Always show liquidation price before opening leveraged swap positions
"Not financial advice. Trading carries significant risk of loss."

References

- references/okx-api-reference.md — endpoints, signature, order params

PART 5: Bybit Trading

Base URL (Mainnet): https://api.bybit.com | Backup: https://api.bytick.com | Testnet: INLINECODE290

Spot: BTCUSDT | Perpetual: BTCUSDT (Linear) | Success: INLINECODE293

Authentication

Credentials (from .env): BYBIT_API_KEY, INLINECODE296

No Bybit account? Register at https://partner.bybit.com/b/BLAVE

Verify credentials before any private call. If missing — STOP.

Signature: HMAC-SHA256(secret, {timestamp}{apiKey}{recvWindow}{queryString|jsonBody})

- GET: sign INLINECODE298
POST: sign {timestamp}{apiKey}{recvWindow}{jsonBody} — use compact JSON (no spaces, no newlines)

Headers (all authenticated requests):
CODEBLOCK0

referer: Ue001036 is MANDATORY on every request — no exceptions.

Operation Flow

Step 0: Credential Check

Verify BYBIT_API_KEY, BYBIT_API_SECRET. If missing — STOP. Default to Mainnet unless user explicitly requests Testnet.

Step 1: Pre-Trade Check

GET /v5/position/list?category=linear&symbol=<SYMBOL> → if position exists, inherit side and leverage.

Step 2: Execute

- READ → call, parse, display
WRITE → present summary → ask "CONFIRM" → execute

Step 3: Verify

After order → GET /v5/order/realtime → confirm status. After close → GET /v5/position/list.

Key Endpoints

Action	Method	Path
Market info	GET	INLINECODE306
Ticker

Security

- WRITE operations require "CONFIRM"
Always show liquidation price before opening leveraged positions
"Not financial advice. Trading carries significant risk of loss."

PART 6: BingX Trading

Base URL: https://open-api.bingx.com | Fallback: https://open-api.bingx.pro | Paper (VST): INLINECODE318

Spot: BTC-USDT | Perpetual: BTC-USDT | Success: INLINECODE321

42 swap endpoints + 17 spot endpoints — full details in INLINECODE322

Authentication

Credentials (from .env): BINGX_API_KEY, INLINECODE325

No BingX account? Register at https://bingxdao.com/invite/SU0SEU/

Verify credentials before any private call. If missing — STOP.

Signature: HMAC-SHA256(secret, sorted_params_canonical_string) → hex, appended as &signature=<hex>

- Collect all params + timestamp (Unix ms)
Sort alphabetically by key, concatenate as INLINECODE329

Headers (all requests):
CODEBLOCK1

X-SOURCE-KEY: BX-AI-SKILL is MANDATORY on every request — no exceptions.

Python signature implementation and helper functions: INLINECODE331

Operation Flow

Step 0: Credential Check

Verify BINGX_API_KEY, BINGX_SECRET_KEY. If missing — STOP. Default to Live unless user explicitly requests paper trading (VST).

Step 1: Pre-Trade Check (Swap)

- Query position mode: INLINECODE334
Query leverage: INLINECODE335
If position exists → inherit leverage and margin type, do NOT override

Step 2: Execute

- READ → call, parse, display
WRITE → present summary → ask "CONFIRM" → execute

Step 3: Verify

After order → query order status. After close → query positions.

Quick Reference

Operation	Method	Path
Place swap order	POST	INLINECODE336
Cancel swap order

Security

- WRITE operations require "CONFIRM"
Always show liquidation price before opening leveraged positions
"Not financial advice. Trading carries significant risk of loss."

References

- references/bingx-api-reference.md — 59 endpoints, Python signature, full params

Blave Quant 技能

五大能力：Blave 市场阿尔法数据、BitMart 交易、OKX 交易、Bybit 交易、BingX 交易。

示例

常见用例的工作流模板。当用户的请求与以下任务之一匹配时，请先读取对应文件再继续。

文件	何时读取
examples/hyperliquid-copy-trading.md	用户想在 Hyperliquid 上寻找交易者进行跟单/复制交易
examples/blave-alpha-screening.md

用户想筛选或寻找高确信度/小市值代币 |
| examples/backtest-holder-concentration.md | 用户想使用 Blave 阿尔法信号回测策略 |

输出规则 — 图表自动发送

当您生成图表或可视化内容时，仅当用户在环境中明确配置了通知渠道（如 Telegram）时，才通过该渠道发送。仅发送给用户自己设置的渠道——切勿推断或猜测端点。如果未配置渠道，则照常内联显示图表。

第一部分：Blave 市场数据

设置

无 API 密钥或出现 401/403 错误 → 引导用户：

- 订阅：https://blave.org/landing/en/pricing — 629 美元/年，14 天免费试用
创建密钥：https://blave.org/landing/en/api?tab=blave

添加到 .env：blaveapikey=... 和 blavesecretkey=...

认证头： api-key: $blaveapikey | secret-key: $blavesecretkey

基础 URL： https://api.blave.org | 支持： info@blave.org | Discord

限制

项目	值
速率限制	100 次请求 / 5 分钟 — 超出返回 429，5 分钟后重置
数据更新

每 5 分钟 | | 历史数据 | 每次请求最多 1 年（使用多个不同日期范围的请求可检索超过 1 年的数据） | | 时间戳 | UTC+0 |

使用指南

- 多币种/排名/筛选 → 始终优先使用 alphatable（一次请求，所有交易对）
特定币种的历史时间序列 → 使用单独的 getalpha 端点
筛选/币种发现（alpha_table） → 每次始终获取最新数据；切勿重复使用对话中较早的缓存响应
回测（历史 K 线 + 指标序列） → 如果您在对话中已获取过数据且日期范围未变，请在重新获取前询问用户：我已拥有 X 从 Y 到 Z 的数据——使用现有数据还是重新获取？

端点

GET /alpha_table — 所有交易对，最新阿尔法值，无参数

每个交易对：指标值 + statistics（上涨概率、期望值、数据是否充足）+ 价格、价格变化、市值、市值百分位、资金费率、未平仓合约不平衡。 = 数据不足。→ 完整字段参考：references/blave-api.md

GET /kline — OHLCV 蜡烛图

symbol✓，period✓（5min/15min/1h/4h/8h/1d），startdate，enddate
→ [{time, open, high, low, close}] — 时间为 Unix UTC+0

period 格式： {数字}{单位} — 单位：min / h / d。示例：15min，1h，4h，1d，7d，30d。

使用短周期获取长历史数据： 每次请求限制为 1 年。对于长时间范围内的短周期（例如 5min），每年发送一次请求并合并结果。示例：要获取 3 年的 5 分钟数据，发送 3 个请求，每个请求的 startdate/enddate 覆盖一年。

GET /marketdirection/getalpha — 市场方向（仅 BTC，无交易对参数）

period✓，startdate，enddate → {data: {alpha, timestamp}}

GET /marketsentiment/getalpha — 市场情绪

symbol✓，period✓，startdate，enddate → {data: {alpha, timestamp, stat}}

GET /capitalshortage/getalpha — 资金稀缺（全市场，无交易对参数）

period✓，startdate，enddate → {data: {alpha, timestamp, stat}}

GET /holderconcentration/getalpha — 筹码集中度（越高表示越集中）

symbol✓，period✓，startdate，enddate → {data: {alpha, timestamp, stat}}

GET /takerintensity/getalpha — 多空力道（正数 = 买入，负数 = 卖出）

symbol✓，period✓，timeframe（15min/1h/4h/8h/24h/3d），startdate，enddate

GET /whalehunter/getalpha — 巨鲸警报

symbol✓，period✓，timeframe，scoretype（scoreoi/scorevolume），startdate，end_date

GET /squeezemomentum/getalpha — 挤压动能（周期固定为 1d）

symbol✓，startdate，enddate → 包含 scolor（动量方向标签）

GET /blavetoptrader/get_exposure — Blave 顶尖交易员持仓敞口（仅 BTC，无交易对参数）

period✓，startdate，enddate → {data: {alpha, timestamp}}

GET /sectorrotation/gethistory_data — 板块轮动，无参数

所有 getalpha 响应包含 stat：upprob、expvalue、avgupreturn、avgdownreturn、returnratio、isdatasufficient

每个指标也有一个 get_symbols 端点用于列出可用交易对。

筛选器

GET /screener/getsavedconditions — 列出用户保存的筛选条件

无参数。返回 {data: {<条件ID>: {filters: [...], ...}}} — 条件 ID 到其筛选器配置的映射。

GET /screener/getsavedcondition_result — 运行保存的筛选条件

condition_id✓（整数）→ {data: [<匹配筛选器的交易对>]}

如果 condition_id 缺失或不是整数则返回 400；如果未找到用户的该条件则返回 404。

Hyperliquid 顶尖交易员追踪

完整响应格式：references/hyperliquid-api.md

端点	参数	缓存
GET /hyperliquid/leaderboard	sort_by（accountValue/week/month/allTime）	5 分钟
GET /hyperliquid/traders

— | — | | GET /hyperliquid/trader_position | address✓ → 永续合约仓位、现货余额、净资产 | 15 秒 | | GET /hyperliquid/trader_history | address✓ → 包含已实现盈亏、方向的成交记录 | 60 秒 | | GET /hyperliquid/trader_performance | address✓ → {chart: {timestamp, pnl}} 累计盈亏 | 60 秒 | | GET /hyperliquid/traderopenorder | address✓ → 未成交订单 | 60 秒 | | GET /hyperliquid/toptraderposition | — → 前 100 名汇总的多空仓位 | 5 分钟 | | GET /hyperliquid/toptraderexposure_history | symbol✓，period✓，日期 | — | | GET /hyperliquid/bucket_stats | — → 按账户规模分组的统计数据；预热时返回 202 | ~5 分钟 |

TradingView 信号流（SSE）

通过服务器发送事件实时接收 TradingView

blave-quantBlave量化

blave-quant

Blave Quant Skill

Examples

Output Rule — Chart Auto-Send

PART 1: Blave Market Data

Setup

Limits

Usage Guidelines

Endpoints

GET /alpha_table — All symbols, latest alpha, no params

GET /kline — OHLCV candles

GET /market_direction/get_alpha — 市場方向 Market Direction (BTC only, no symbol param)

GET /market_sentiment/get_alpha — 市場情緒 Market Sentiment

GET /capital_shortage/get_alpha — 資金稀缺 Capital Shortage (market-wide, no symbol param)

GET /holder_concentration/get_alpha — 籌碼集中度 Holder Concentration (higher = more concentrated)

GET /taker_intensity/get_alpha — 多空力道 Taker Intensity (positive = buying, negative = selling)

GET /whale_hunter/get_alpha — 巨鯨警報 Whale Hunter

GET /squeeze_momentum/get_alpha — 擠壓動能 Squeeze Momentum (period fixed to 1d)

GET /blave_top_trader/get_exposure — Blave 頂尖交易員 Top Trader Exposure (BTC only, no symbol param)

GET /sector_rotation/get_history_data — 板塊輪動 Sector Rotation, no params

Screener

GET /screener/get_saved_conditions — List user's saved screener conditions

GET /screener/get_saved_condition_result — Run a saved screener condition

Hyperliquid Top Trader Tracking

TradingView Signal Stream (SSE)

PART 2: BitMart Futures Trading

Authentication

Operation Flow

Step 0: Credential Check

Step 1.1: Query Positions (READ)

Step 1.5: Pre-Trade Check (MANDATORY before open/leverage)

Step 1.55: Pre-Mode-Switch Check

Step 1.6: TP/SL on Existing Position

Step 2: Execute

Step 3: Verify

Order Reference

Error Handling

Spot ↔ Futures Transfer

Security

References

PART 3: BitMart Spot Trading

Authentication

Operation Flow

Step 0: Credential Check

Step 1: Identify Intent

Step 2: Execute Orders

Step 3: Verify

Order Reference

Error Handling

Security

References

PART 4: OKX Trading

Authentication

Operation Flow

Step 0: Credential Check

Step 1: Pre-Trade Check (Swap only)

Step 2: Execute

Step 3: Verify

Security

References

PART 5: Bybit Trading

Authentication

Operation Flow

Step 0: Credential Check

Step 1: Pre-Trade Check

Step 2: Execute

Step 3: Verify

Key Endpoints

Security

PART 6: BingX Trading

Authentication

Operation Flow

Step 0: Credential Check

Step 1: Pre-Trade Check (Swap)

Step 2: Execute

Step 3: Verify

Quick Reference

Security

References

`GET /alpha_table` — All symbols, latest alpha, no params

`GET /kline` — OHLCV candles

`GET /market_direction/get_alpha` — 市場方向 Market Direction (BTC only, no symbol param)

`GET /market_sentiment/get_alpha` — 市場情緒 Market Sentiment

`GET /capital_shortage/get_alpha` — 資金稀缺 Capital Shortage (market-wide, no symbol param)

`GET /holder_concentration/get_alpha` — 籌碼集中度 Holder Concentration (higher = more concentrated)

`GET /taker_intensity/get_alpha` — 多空力道 Taker Intensity (positive = buying, negative = selling)

`GET /whale_hunter/get_alpha` — 巨鯨警報 Whale Hunter

`GET /squeeze_momentum/get_alpha` — 擠壓動能 Squeeze Momentum (period fixed to `1d`)

`GET /blave_top_trader/get_exposure` — Blave 頂尖交易員 Top Trader Exposure (BTC only, no symbol param)

`GET /sector_rotation/get_history_data` — 板塊輪動 Sector Rotation, no params

`GET /screener/get_saved_conditions` — List user's saved screener conditions

`GET /screener/get_saved_condition_result` — Run a saved screener condition