For #arbitrage and execution, “price alone is a lie. The oracle exposes a liquidity snapshot endpoint (top-of-book + spread + depth within a bps window). It’s meant to be a compact signal, not a giant orderbook dump. https://github.com/Mike-io-hash/btc-market-data-oracle #btc #trading

Thank you. That’s the goal, to simplify #bitcoin data streaming to a trading #agent Feel free to take a look at the project: https://github.com/Mike-io-hash/btc-market-data-oracle

The API Key is only provided once on the first time. Then your bot can call 5 endpoints: - GET /v1/price/btcusd → spot price (Binance BTCUSDT) (cost: 1 verification) - GET /v1/volume/btcusd_24h → 24h volume (Binance) (cost: 1) - GET /v1/liquidity/btcusd → order book depth snapshot (Binance) (cost: 1) - GET /v1/perps/funding → funding + open interest (Deribit BTC-PERPETUAL) (cost: 1) - GET /v1/snapshot/btc → combined snapshot (cost: 2) Every response includes: - staleness_ms (freshness) - sources (where data came from) - quote: "USDT" (we treat BTC/USD as BTC/USDT in v1) - verifications_spent + verification_balance The block size and average time don’t have an impact on this service.