BlockBeats API Skill

Query crypto newsflashes, articles, search, and on-chain/market datasets via the BlockBeats Pro API.

Get an API key (follow these steps; no manual user setup needed)

If BLOCKBEATS_API_KEY is missing or empty, you MUST only use the environment file ~/.openclaw/.1m-trade/.env to store/read it. Do NOT read or touch any other files.

1. Check ~/.openclaw/.1m-trade/.env for BLOCKBEATS_API_KEY.
2. If BLOCKBEATS_API_KEY is missing or empty:
   • Run exactly this curl to fetch a free API key:

     curl --request GET --url "https://api-pro.theblockbeats.info/v1/api-key/free"
     

   • Parse the response and extract data.api_key as BLOCKBEATS_API_KEY.
   • In ~/.openclaw/.1m-trade/.env, ONLY update the BLOCKBEATS_API_KEY entry:
     • If the key already exists, replace only that line's value.
     • If the key does not exist, append a new line: BLOCKBEATS_API_KEY=<api_key>
   • Keep all other existing env lines unchanged (do NOT overwrite the whole file).
   • Do not print the API key in chat/logs.
3. For the sections below, use BLOCKBEATS_API_KEY as the value for the request header api-key: $BLOCKBEATS_API_KEY.

Request format

Base URL: https://api-pro.theblockbeats.info Auth: all requests must include the header api-key: $BLOCKBEATS_API_KEY Response: {"status": 0, "message": "", "data": {...}} — status == 0 means success

Scenario 1: Market snapshot

Triggers: "how is the market today", "market snapshot", "daily overview", etc.

Run the following 4 requests in parallel:

# 1) Bottom/top indicator (sentiment)
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/bottom_top_indicator"

# 2) Important newsflashes (latest 5)
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/newsflash/important" \
  -G --data-urlencode "size=5" --data-urlencode "lang=cn"

# 3) BTC ETF net flow
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/btc_etf"

# 4) Daily on-chain tx volume
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/daily_tx"

Output format:

📊 Market Snapshot · [Today]

Sentiment indicator: [value] → [<20 potential buy zone / 20–80 neutral / >80 potential sell zone]
BTC ETF: net flow today [value] USD (M), cumulative [value] USD (M)
On-chain tx volume: [value] (vs yesterday [↑/↓][%])
Important news:
  · [title 1] [time]
  · [title 2] [time]
  · [title 3] [time]

Interpretation rules:

• Indicator < 20 → highlight potential opportunities
• Indicator > 80 → highlight potential sell risk
• ETF positive net flow for 3 consecutive days → institutional accumulation signal
• ETF net flow > 500M/day → strong buy signal
• Rising tx volume → higher on-chain activity / market heat

Scenario 2: Fund flow analysis

Triggers: "where is money flowing", "on-chain hotspots", "stablecoins", "smart money", etc.

Run in parallel:

# 1) Top 10 net inflow tokens (default: solana; use Base/ETH if mentioned)
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/top10_netflow" \
  -G --data-urlencode "network=solana"

# 2) Stablecoin market cap
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/stablecoin_marketcap"

# 3) BTC ETF net flow
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/btc_etf"

network values: solana (default) / base / ethereum

Output format:

💰 Fund Flow Analysis

On-chain trending ([network]):
  1. [token] net inflow $[value]  mcap $[value]
  2. ...

Stablecoins: USDT [↑/↓] USDC [↑/↓] (expansion / contraction)
Institutional: ETF today [in/out] [value] USD (M)

Interpretation rules:

• Stablecoin expansion → more sidelined capital, stronger bid potential
• Stablecoin contraction → capital leaving, be cautious

Scenario 3: Macro environment

Triggers: "macro", "liquidity", "US rates", "USD", "is it a good entry", etc.

Run in parallel:

# 1) US 10Y yield
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/us10y" \
  -G --data-urlencode "type=1M"

# 2) DXY
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/dxy" \
  -G --data-urlencode "type=1M"

# 3) Compliant exchanges total assets
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/compliant_total"

Output format:

🌐 Macro Environment

US 10Y yield: [value]% → [up/down]
DXY: [value] → [strong/weak]
Compliant exchanges assets: $[value] → [inflow/outflow]

Overall: [bullish/neutral/bearish] for crypto

Interpretation rules:

• Rising DXY → stronger USD, crypto headwind
• Falling DXY → weaker USD, crypto tailwind
• Rising yields → higher risk-free rate, capital rotates to bonds
• Rising compliant exchange assets → stronger institutional allocation

Scenario 4: Derivatives market

Triggers: "derivatives", "open interest", "Binance/Bybit", "leverage risk", etc.

Run in parallel:

# 1) Major venues comparison
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/contract" \
  -G --data-urlencode "dataType=1D"

# 2) Exchange snapshot
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/exchanges" \
  -G --data-urlencode "size=10"

# 3) Bitfinex BTC long positions
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/bitfinex_long" \
  -G --data-urlencode "symbol=btc" --data-urlencode "type=1D"

Output format:

⚡ Derivatives Market

Major venues OI:
  Binance [value]  Bybit [value]  Hyperliquid [value]

Exchange ranking (by volume):
  1. [name] volume $[value]  OI $[value]
  2. ...

Bitfinex BTC longs: [value] → [up/down] (leveraged long sentiment [strong/weak])

Interpretation rules:

• Rising Bitfinex longs → whales leaning long, stronger confidence
• Sharp drop → watch for long unwinds / downside risk

Scenario 5: Keyword search

Triggers: "search [keyword]", "find [keyword]", "[keyword] news", etc.

curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/search" \
  -G --data-urlencode "name=[keyword]" --data-urlencode "size=10" --data-urlencode "lang=cn"

Returned fields: title, abstract, content (plain text), type (0=article, 1=newsflash), time_cn (relative time), url

Single-endpoint reference

Newsflash endpoints (support page/size/lang)

curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/newsflash/[type]" \
  -G --data-urlencode "page=1" --data-urlencode "size=10" --data-urlencode "lang=cn"

Article endpoints (support page/size/lang)

Data endpoints

Timeframe auto-mapping

Intent mapping

Data refresh frequency

Error handling

Notes

• content may contain HTML; strip tags and display plain text
• create_time is a string in Y-m-d H:i:s
• Numeric fields (price/vol, etc.) are strings; you may format them as numbers
• When querying in parallel, one failed endpoint should not block the others