Binance Event Contract Full Data Fetcher

1. Scenario Definition

• Trigger Timing: Auto-run every minute after Agent startup; also supports manual trigger via /binance-fetch-data; runs 24/7, aligned with Binance 7×24 trading hours
• Core Intent: Provide 100% accurate, delay-free Binance official native data for the 3-tier resonance strategy; reject all third-party data sources
• Context: Targets only BTCUSDT & ETHUSDT pairs; covers only 10min/30min/60min Event Contract cycles; provides underlying data support for signal calculation, ICT recognition, and risk control

2. Goal Setting

Complete Binance official API data fetch within 1 second per minute; output standardized BTC/ETH full-dimension data with 100% accuracy; price data fully matches Binance Event Contract settlement spot index price; provide error-free data source for strategy signal calculation.

3. Execution Rules

3.1 Data Source Rule

• MUST connect ONLY to Binance Official REST API & WebSocket API
• MUST call https://api.binance.com (or appropriate endpoint)
• PROHIBITED: Calling any third-party data platform (Huobi, OKX, etc.)

3.2 Fixed Fetch Pairs

• BTCUSDT (primary)
• ETHUSDT (secondary)

3.3 Mandatory Fetch Data Dimensions

K-line Data:

• Cycles: 1min / 10min / 30min / 1h / 4h
• Fields: open, high, low, close, volume, turnover
• Fetch latest 200 K-lines per cycle for indicator calculation

Liquidity Data:

• BTC/ETH spot order book top 10 bid/ask depth
• Calculate total bid/ask amount
• Verify if total bid or ask ≥ 500,000 USDT

Market Data:

• Latest spot index price (Binance Event Contract settlement anchor)
• 24h price change
• Bid-ask spread

Contract Rule Data:

• Current available expiration cycles (10min/30min/1h)
• Single trade limit (5-250 USDT)
• Daily loss limit rules

3.4 Running Rule

• Auto-start cron task at Agent startup
• Run at second 0 of every minute
• Auto-cache data after fetch
• Sync to all related Skills for call

3.5 Data Verification Rule

• Auto-verify data integrity after each fetch
• Auto-retry 3 times if interface timeout or data missing
• Trigger exception alert if retry failed
• Use previous valid cached data as fallback
• No impact on strategy running if cache available

4. Example Output