AAgentReeve

Bitcoin market intelligence that agents can buy one request at a time.

Seven exchange venues, derivatives, the mempool and up to two years of retained history behind one JSON endpoint. Every value carries its source, timestamp and freshness. Pay $0.02 per call with x402. No account, no API key, no monthly bill.

Observational data, not advice. Payments settle in USDC on Base. Paid routes return 503 until the operator enables payments.

Live free preview loading
Spot index—median of fresh spot venues
Futures index—median of fresh perp marks
Basis—futures vs spot, bps
Venue spread—max/min across venues, bps
Fresh sources—
GET /api/v1/btc/preview

What you get for two cents

One call, seven venues

Coinbase, Kraken, Binance spot and futures, OKX, Bybit and Hyperliquid, normalised into one payload with a freshness-restricted median index. You stop maintaining seven clients and seven rate limits.

Provenance in every row

Source, event time, receipt time, provenance class and licensing status travel with each observation. Stale venues are named and excluded from the index, never silently back-filled.

Depth and flow, not just last price

Top-of-book spread, ten-level depth imbalance, microprice and one-second taker buy/sell volume from the Binance perpetual stream. Funding, open interest and options IV on the derivatives route.

History you can audit

Minute, hour and day buckets recorded at ingest time with sample counts and gap counters. Retained fourteen days granular, ninety days by minute and two years by hour, counted from when this deployment started recording. Up to five thousand rows per call.

How a paid request works

  1. Your agent calls a paid route.GET /api/v1/btc/market
  2. The server answers 402 with x402 payment requirements.HTTP/1.1 402 · PAYMENT-REQUIRED: {scheme: exact, price: $0.02, USDC, Base}
  3. An x402 client signs the payment and retries the same request.GET /api/v1/btc/market · PAYMENT-SIGNATURE: …
  4. You receive the data and a settlement receipt. The server records the on-chain transaction hash.HTTP/1.1 200 · PAYMENT-RESPONSE: {success: true, transaction: 0x…}

No pre-funding, no API key to leak, no invoice. The charge is the price shown in the catalog at the moment of the call. Nothing is charged for a 402, a 429 or a 5xx.

Catalog and prices

Prices are read live from /api/discovery, the same document the payment middleware uses. A route is marked unavailable when its data sources are not configured on this deployment, so you are never charged for an empty answer.

RouteWhat it returnsPriceStatus
Loading catalog

Three ways to connect

# Free, no payment
curl -s https://agentreeve.com/api/v1/btc/preview | jq

# Paid: shows the 402 challenge when payments are enabled
curl -si https://agentreeve.com/api/v1/btc/market | head -20

What this is not