Summary Querying crypto news, newsflashes, articles, search, and on-chain market data (ETF flows, stablecoin supply, derivatives OI, M2, DXY, Bitfinex long positions, and more). Requires BLOCKBEATS_API_KEY.
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 .
Check ~/.openclaw/.1m-trade/.env for BLOCKBEATS_API_KEY.
If BLOCKBEATS_API_KEY is missing or empty:
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 successScenario 1: Market snapshot
Triggers
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"
📊 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]
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.
# 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
💰 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)
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.
# 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"
🌐 Macro Environment
US 10Y yield: [value]% → [up/down]
DXY: [value] → [strong/weak]
Compliant exchanges assets: $[value] → [inflow/outflow]
Overall: [bullish/neutral/bearish] for crypto
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.
# 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"
⚡ 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])
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) Endpoint URL All newsflashes GET /v1/newsflashImportant newsflashes GET /v1/newsflash/importantOriginal newsflashes GET /v1/newsflash/originalFirst-release newsflashes GET /v1/newsflash/firstOn-chain newsflashes GET /v1/newsflash/onchainFinancing newsflashes GET /v1/newsflash/financingPrediction-market newsflashes GET /v1/newsflash/predictionMeme newsflashes GET /v1/newsflash/memeAI newsflashes GET /v1/newsflash/ai
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) Endpoint URL All articles GET /v1/articleImportant articles GET /v1/article/importantOriginal articles GET /v1/article/original
Data endpoints Endpoint URL Key params BTC ETF net flow GET /v1/data/btc_etfN/A Daily on-chain tx volume GET /v1/data/daily_txN/A IBIT/FBTC net flow GET /v1/data/ibit_fbtcN/A Stablecoin market cap GET /v1/data/stablecoin_marketcapN/A Compliant exchanges total assets GET /v1/data/compliant_totalN/A US 10Y yield GET /v1/data/us10ytype=1D/1W/1MDXY GET /v1/data/dxytype=1D/1W/1MGlobal M2 supply GET /v1/data/m2_supplytype=3M/6M/1Y/3YBitfinex BTC longs GET /v1/data/bitfinex_longsymbol=btc type=1D/1W/1M/h24Major derivatives venues data GET /v1/data/contractdataType=1D/1W/1M/3M/6M/12MBottom/top indicator GET /v1/data/bottom_top_indicatorN/A Top-10 net inflow GET /v1/data/top10_netflownetwork=solana/base/ethereumDerivatives exchanges snapshot GET /v1/data/exchangesname page size
Timeframe auto-mapping User says Param today / latest / real-time type=1D or size=5this week / recent type=1Wthis month / last month type=1Mthis year / long-term type=1Y or type=3Ylast 24h (bitfinex_long only) type=h24
Intent mapping User intent Scenario / endpoint how is the market today / daily overview Scenario 1: Market snapshot fund flows / on-chain hotspots / smart money Scenario 2: Fund flow analysis macro / M2 / yields / good entry? Scenario 3: Macro environment derivatives / open interest / leverage risk Scenario 4: Derivatives market search [keyword] Scenario 5: Keyword search latest newsflashes / list newsflashes GET /v1/newsflashimportant newsflashes GET /v1/newsflash/importantoriginal newsflashes GET /v1/newsflash/originalfirst-release newsflashes GET /v1/newsflash/firston-chain newsflashes GET /v1/newsflash/onchainfinancing newsflashes / financing news GET /v1/newsflash/financingprediction markets / Polymarket GET /v1/newsflash/predictionmeme news GET /v1/newsflash/memeAI news GET /v1/newsflash/aiarticle list GET /v1/articleimportant articles GET /v1/article/importantoriginal articles GET /v1/article/originalBTC ETF net flow GET /v1/data/btc_etfIBIT FBTC GET /v1/data/ibit_fbtcstablecoin market cap / USDT USDC GET /v1/data/stablecoin_marketcapDXY GET /v1/data/dxyBitfinex longs / leverage positioning GET /v1/data/bitfinex_longbottom/top indicator / sentiment GET /v1/data/bottom_top_indicatortop net inflow tokens / on-chain trending GET /v1/data/top10_netflowderivatives exchanges ranking GET /v1/data/exchangeson-chain tx volume / activity GET /v1/data/daily_txcompliant exchange assets / custody GET /v1/data/compliant_total
Data refresh frequency Endpoint type Refresh cadence newsflashes / articles / search real-time top10_netflow near real-time btc_etf / ibit_fbtc / daily_tx daily (T+1) stablecoin_marketcap / compliant_total daily bottom_top_indicator daily us10y / dxy intraday (minute-level) m2_supply monthly exchanges / contract daily bitfinex_long daily (h24 is near real-time)
Error handling Error Handling BLOCKBEATS_API_KEY missingPrompt to set BLOCKBEATS_API_KEY (see the key-fetch section above) HTTP 401 API key invalid/expired HTTP 403 Plan does not allow access to the endpoint status != 0Show the message field Timeout Suggest retry; do not block other parallel requests data empty arrayExplain likely causes (non-trading day, delay, no data for asset)
Notes
content may contain HTML; strip tags and display plain textcreate_time is a string in Y-m-d H:i:sNumeric fields (price/vol, etc.) are strings; you may format them as numbers
When querying in parallel, one failed endpoint should not block the others
