Blave Quant Skill

Four capabilities: Blave market alpha data, BitMart trading (futures & spot), OKX trading, Bybit 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.

examples/hyperliquid-copy-trading.md

examples/blave-alpha-screening.md

examples/backtest-holder-concentration.md

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=...

blave_secret_key=...

Auth headers:

api-key: $blave_api_key

secret-key: $blave_secret_key

Base URL:

https://api.blave.org

Limits

429

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

Endpoints

GET /alpha_table

— All symbols, latest alpha, no params

Each symbol contains indicator fields plus:

statistics

up_prob

exp_value

avg_up_return

avg_down_return

return_ratio

is_data_sufficient

price

{"-": 70000}

price_change

{"15min": ..., "1h": ..., "24h": ...}

market_cap

{"-": 1234567890}

market_cap_percentile

{"-": 85.3}

funding_rate

{"binance": -0.01, ...}

oi_imbalance

{"-": 0.12}

statistics.up_prob

= probability of upward move in 24h.

statistics.exp_value

= expected return. Use these to screen coins.

fields

note

""

GET /kline

— OHLCV candles

symbol

period

5min

15min

1h

4h

8h

1d

start_date

end_date

[{time, open, high, low, close}]

period

{number}{unit}

min

h

d

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

start_date

end_date

GET /market_direction/get_alpha

— 市場方向 Market Direction (BTC only, no symbol param)

period

start_date

end_date

{data: {alpha, timestamp}}

GET /market_sentiment/get_alpha

— 市場情緒 Market Sentiment

symbol

period

start_date

end_date

{data: {alpha, timestamp, stat}}

GET /capital_shortage/get_alpha

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

period

start_date

end_date

{data: {alpha, timestamp, stat}}

GET /holder_concentration/get_alpha

— 籌碼集中度 Holder Concentration (higher = more concentrated)

symbol

period

start_date

end_date

{data: {alpha, timestamp, stat}}

GET /taker_intensity/get_alpha

— 多空力道 Taker Intensity (positive = buying, negative = selling)

symbol

period

timeframe

15min

1h

4h

8h

24h

3d

start_date

end_date

GET /whale_hunter/get_alpha

— 巨鯨警報 Whale Hunter

symbol

period

timeframe

score_type

score_oi

score_volume

start_date

end_date

GET /squeeze_momentum/get_alpha

— 擠壓動能 Squeeze Momentum (period fixed to

1d

)

symbol

start_date

end_date

scolor

GET /blave_top_trader/get_exposure

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

period

start_date

end_date

{data: {alpha, timestamp}}

GET /sector_rotation/get_history_data

— 板塊輪動 Sector Rotation, no params

All

get_alpha

stat

up_prob

exp_value

avg_up_return

avg_down_return

return_ratio

is_data_sufficient

Each indicator also has a

get_symbols

Screener

GET /screener/get_saved_conditions

— List user's saved screener conditions

No params. Returns

{data: {<condition_id>: {filters: [...], ...}}}

GET /screener/get_saved_condition_result

— Run a saved screener condition

condition_id

{data: [<symbols matching filters>]}

Returns 400 if

condition_id

Hyperliquid Top Trader Tracking

GET /hyperliquid/leaderboard

— Hyperliquid top 100 traders

sort_by

accountValue

week

month

allTime

Returns top 100 traders with

ethAddress

accountValue

windowPerformances

displayName

GET /hyperliquid/traders

— Blave-curated trader list

No params. Returns dict of

{address: {name: {en, zh}, description: {en, zh}}}

GET /hyperliquid/trader_position

— Trader's current positions

address

{perp, spot, abstraction, net_equity, trader_name, description}

• perp.assetPositions

  — perpetual positions with

  coin

  ,

  szi

  ,

  entryPx

  ,

  unrealizedPnl

  ,

  token_id

• spot.balances

  — spot token balances

• net_equity

  — total account value (USD) Cached 15 s.

GET /hyperliquid/trader_history

— Trader's fill history

address

{coin, px, sz, dir, closedPnl, time, token_id}

• dir

  : trade direction (Open Long / Close Long / etc.)

• closedPnl

  : realized PnL for closed trades

• time

  : Unix timestamp (seconds) Cached 60 s.

GET /hyperliquid/trader_performance

— Trader's PnL chart

address

{chart: {timestamp: [...], pnl: [...]}}

GET /hyperliquid/trader_open_order

— Trader's open orders

address

{coin, sz, px, side, token_id, ...}

GET /hyperliquid/top_trader_position

— Aggregated top trader positions

No params. Aggregates long/short positions across top 100 leaderboard traders →

{long: [{coin, position, ...}], short: [...]}

GET /hyperliquid/top_trader_exposure_history

— Historical top trader net exposure

symbol

period

start_date

end_date

{data: {...}}

GET /hyperliquid/bucket_stats

— Profit/loss stats by account size bucket

No params. Returns trader stats grouped by account value:

• Buckets:

  lt_100

  ,

  100_to_1k

  ,

  1k_to_10k

  ,

  10k_to_100k

  ,

  100k_to_1M

  ,

  gt_1M

  ,

  top_traders

• Each bucket:

  {stats: {count, profit_ratio, loss_ratio}, positions: {long, short}, long_exposure, short_exposure, net_exposure}

• Returns

  {"status": "warming_up"}

  with HTTP 202 while cache is being built (retry after a few seconds). Cached ~5 min.

Python examples:

references/blave-api.md

Indicator interpretation guide:

references/blave-indicator-guide.md

PART 2: BitMart Futures Trading

Base URL:

https://api-cloud-v2.bitmart.com

BTCUSDT

code == 1000

53 endpoints — full details in

references/bitmart-api-reference.md

Authentication

Credentials (from

.env

BITMART_API_KEY

BITMART_API_SECRET

BITMART_API_MEMO

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

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

X-BM-KEY

X-BM-KEY

X-BM-SIGN

X-BM-TIMESTAMP

Signature:

HMAC-SHA256(secret, "{timestamp}#{memo}#{body}")

""

Always include

X-BM-BROKER-ID: BlaveData666666

IP Whitelist: Use public IP (

curl https://checkip.amazonaws.com

10.x

172.x

192.168.x

Signature Python implementation and common mistakes:

references/bitmart-signature.md

Operation Flow

Step 0: Credential Check

Verify

BITMART_API_KEY

BITMART_API_SECRET

BITMART_API_MEMO

Step 1.1: Query Positions (READ)

GET /contract/private/position-v2

current_amount != "0"

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

1. Call

   GET /contract/private/position-v2?symbol=<SYMBOL>

2. If

   current_amount

   non-zero → inherit

   leverage

   and

   open_type

   , do NOT override
3. 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

Step 1.6: TP/SL on Existing Position

POST /contract/private/submit-tp-sl-order

type

"take_profit"

"stop_loss"

side

3

2

trigger_price

executive_price

"0"

price_type

1

2

plan_category

2

Step 2: Execute

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

submit-order rules:

"market"

"limit"

"market"

"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

2

3

4

Mode:

1

2

3

4

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

Error Handling

references/bitmart-signature.md

Spot ↔ Futures Transfer

Present summary → ask "CONFIRM" → execute.

Endpoint:

POST https://api-cloud-v2.bitmart.com/account/v1/transfer-contract

currency

USDT

amount

type

"spot_to_contract"

"contract_to_spot"

Rate limit: 1 req/2sec. ⚠️

/spot/v1/transfer-contract

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

• references/bitmart-signature.md

  — Python signature implementation

• references/bitmart-open-position.md

  /

  bitmart-close-position.md

  /

  bitmart-plan-order.md

  /

  bitmart-tp-sl.md

PART 3: BitMart Spot Trading

Base URL:

https://api-cloud.bitmart.com

BTC_USDT

code == 1000

34 endpoints — full details in

references/bitmart-spot-api-reference.md

Authentication

Same signature method as Futures. Credentials from

.env

BITMART_API_KEY

BITMART_API_SECRET

BITMART_API_MEMO

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

Always include

X-BM-BROKER-ID: BlaveData666666

IP Whitelist: Use public IP (

curl https://checkip.amazonaws.com

Signature Python implementation:

references/bitmart-signature.md

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

buy

market

notional

buy

limit

size

price

sell

market

size

sell

limit

size

price

Market buy uses

notional

, NOT

size

.

Step 3: Verify

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

Order Reference

Side:

buy

sell

limit

market

limit_maker

ioc

Status:

new

partially_filled

filled

canceled

partially_canceled

Timestamps: ms — always convert to local time.

Error Handling

references/bitmart-signature.md

Security

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

References

• references/bitmart-spot-api-reference.md

  — 34 endpoints

• references/bitmart-signature.md

  — Python signature implementation

• references/bitmart-spot-authentication.md

  /

  bitmart-spot-scenarios.md

PART 4: OKX Trading

Base URL:

https://www.okx.com

BTC-USDT

BTC-USDT-SWAP

"code": "0"

Full details in

references/okx-api-reference.md

Authentication

Credentials (from

.env

OKX_API_KEY

OKX_SECRET_KEY

OKX_PASSPHRASE

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 =

  ""

Headers:

OK-ACCESS-KEY

OK-ACCESS-SIGN

OK-ACCESS-TIMESTAMP

OK-ACCESS-PASSPHRASE

User-Agent: Mozilla/5.0

User-Agent

403 Error code 1010

Broker code:

"tag": "96ee7de3fd4bBCDE"

tag

Operation Flow

Step 0: Credential Check

Verify

OKX_API_KEY

OKX_SECRET_KEY

OKX_PASSPHRASE

Step 1: Pre-Trade Check (Swap only)

GET /api/v5/account/positions?instId=<SYMBOL>-SWAP

tdMode

Step 2: Execute

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

Step 3: Verify

After order →

GET /api/v5/trade/order

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

https://api.bytick.com

https://api-testnet.bybit.com

Spot:

BTCUSDT

BTCUSDT

"retCode": 0

Authentication

Credentials (from

.env

BYBIT_API_KEY

BYBIT_API_SECRET

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

  {timestamp}{apiKey}{recvWindow}{queryString}

• POST: sign

  {timestamp}{apiKey}{recvWindow}{jsonBody}

  — use compact JSON (no spaces, no newlines)

Headers (all authenticated requests):

X-BAPI-API-KEY: $BYBIT_API_KEY
X-BAPI-TIMESTAMP: <unix ms>
X-BAPI-SIGN: <hmac signature>
X-BAPI-RECV-WINDOW: 5000
referer: Ue001036
Content-Type: application/json   (POST only)

referer: Ue001036

Operation Flow

Step 0: Credential Check

Verify

BYBIT_API_KEY

BYBIT_API_SECRET

Step 1: Pre-Trade Check

GET /v5/position/list?category=linear&symbol=<SYMBOL>

Step 2: Execute

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

Step 3: Verify

After order →

GET /v5/order/realtime

GET /v5/position/list

Key Endpoints

/v5/market/instruments-info

/v5/market/tickers

/v5/account/wallet-balance

/v5/order/create

/v5/order/cancel

/v5/order/realtime

/v5/position/list

/v5/position/set-leverage

/v5/position/set-tpsl

/v5/order/history

Security

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

PART 6: Unsupported Exchanges

For any exchange not in Parts 2–5: follow the same workflow — credential check → present summary → ask "CONFIRM" → execute → verify. Never call exchange APIs directly. Inform the user this exchange is not officially supported.