BlockBeats API Skill

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

Base URL: https://api-pro.theblockbeats.info Auth: All requests require Header api-key: $BLOCKBEATS_API_KEY Response format: {"status": 0, "message": "", "data": {...}} — status 0 = success

Scenario 1: Market Overview

Triggers: How's the market today, market overview, daily summary, market conditions

Execute the following four requests in parallel:

# 1. Market sentiment index
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=en"

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

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

Output format:

📊 Market Overview · [Today's date]

Sentiment Index: [value] → [<20 potential buy zone / 20-80 neutral / >80 potential sell zone]
BTC ETF: Today net inflow [value] million USD, cumulative [value] million
On-chain Volume: Today [value] (vs yesterday [↑/↓][change%])
Key News:
  · [Title 1] [time]
  · [Title 2] [time]
  · [Title 3] [time]

Interpretation rules:

• Sentiment < 20 → Alert user to potential opportunities
• Sentiment > 80 → Warn about sell-off risk
• ETF positive inflow 3 days in a row → Institutional accumulation signal
• ETF net inflow > 500M/day → Strong buy signal
• Rising on-chain volume → Increasing on-chain activity and market heat

Scenario 2: Capital Flow Analysis

Triggers: Where is capital flowing, on-chain trends, which tokens are being bought, stablecoins, smart money

Execute in parallel:

# 1. Top 10 tokens by on-chain net inflow (default solana; replace network param for Base/ETH)
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 inflow
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/btc_etf"

Select network parameter based on user intent: solana (default) / base / ethereum

Output format:

💰 Capital Flow Analysis

On-chain Trending ([chain]):
  1. [token] Net inflow $[value]  Market cap $[value]
  2. ...

Stablecoins: USDT [↑/↓] USDC [↑/↓] (expansion/contraction signal)
Institutional: ETF today [inflow/outflow] [value] million USD

Interpretation rules:

• Stablecoin market cap expanding → More capital in market, stronger buy potential
• Stablecoin market cap shrinking → Capital exiting, caution advised

Scenario 3: Macro Environment Assessment

Triggers: Macro environment, is it a good time to enter, liquidity, US Treasuries, dollar, M2, big picture

Execute in parallel:

# 1. Global M2 supply
curl -s -H "api-key: $BLOCKBEATS_API_KEY" \
  "https://api-pro.theblockbeats.info/v1/data/m2_supply" \
  -G --data-urlencode "type=1Y"

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

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

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

Output format:

🌐 Macro Environment Assessment

Global M2: [latest value] YoY [↑/↓][change%] → [expansionary/contractionary]
US Treasury Yield (10Y): [latest value]% → [rising/falling trend]
Dollar Index (DXY): [latest value] → [strong/weak]
Compliant Exchange Assets: $[value] → [inflow/outflow trend]

Overall: [bullish/neutral/bearish] for crypto market

Interpretation rules:

• M2 YoY > 5% → Loose liquidity, favorable for risk assets
• M2 YoY < 0% → Liquidity tightening, caution
• DXY rising → Strong dollar, crypto under pressure
• DXY falling → Weak dollar, crypto benefits
• Rising Treasury yield → Higher risk-free rate, capital returning to bonds
• Rising compliant exchange assets → Growing institutional allocation appetite

Scenario 4: Derivatives Market Analysis

Triggers: Futures market, long/short positioning, open interest, Binance Bybit OI, leverage risk

Execute in parallel:

# 1. Major derivatives platform 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 Analysis

Platform OI:
  Binance [value]  Bybit [value]  Hyperliquid [value]

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

Bitfinex BTC Longs: [value] → [increasing/decreasing] (leveraged long sentiment [strong/weak])

Interpretation rules:

• Bitfinex longs persistently increasing → Large players bullish, market confidence growing
• Bitfinex longs dropping sharply → Watch for long liquidation cascade

Scenario 5: Keyword Search

Triggers: search [keyword], find [keyword], [keyword] news, what's happening with [keyword]

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=en"

Response fields: title, abstract, content (plain text), type (0=article, 1=newsflash), time_cn (relative time), img_url, url; pagination object: total, page, size, total_pages; size max 100

Scenario 6: Newsflash & Article Lists

Select the appropriate newsflash category or article endpoint based on user intent. Default returns 10 items; use size param to adjust.

Newsflash category triggers and endpoints:

Article category triggers and endpoints:

Request example (AI newsflash):

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

Output format:

📰 [Category Name] · Latest [N] items

1. [Title] [time_cn]
   [abstract, if available]

2. [Title] [time_cn]
   [abstract, if available]
...

Notes:

• content field is HTML; strip tags and display plain text only
• Article endpoints do NOT have a url field; use link for the article page URL

Single Endpoint Reference

Newsflash Endpoints (all 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=en"

Article Endpoints

RSS Endpoints

RSS endpoints return XML format. Use when user requests RSS feed or wants to subscribe to updates.

Data Endpoints

Time Dimension Mapping

Intent Mapping

Data Refresh Frequency

Error Handling

Notes

• content field is HTML; strip tags and display plain text only
• create_time field format: Y-m-d H:i:s
• Numeric fields (price/vol etc.) are strings; format as numbers when displaying
• When running parallel requests, a failure on one endpoint must not block display of others