A quant-grade data feed for perpetual-futures funding — normalized across major CEX and DEX venues, with cross-venue spread and oracle-family flags surfaced explicitly so your backtest doesn't fool itself.
Funding rates alone are a noisy primitive. This API adds the joins that matter for systematic carry: per-symbol cross-venue spread, next-settlement estimates, recent sign flips, volume-weighted spreads, and the oracle-family disclosure that tells you when two venues share a price source (so any 'arb' between them is illusory).
The endpoints below are live on api.usenami.io. Prices are per call in USDC, settled on Base via x402 — no signup, no API key, no monthly minimum. Full spec at /.well-known/x402.json.
Often used alongside (same API, same pricing model):
Typical quant workflow — pull the spread + oracle map, filter same-family pairs, rank what's left. The free endpoints (/v1/health, /v1/venues/list, /v1/venues/health, and the preview routes) return without payment so you can validate connectivity before any USDC moves.
# 1. cross-venue spread (long-side / short-side / bps)
curl -X POST <x402-pay> https://api.usenami.io/v1/perp/funding-spread
# 2. oracle family map — drop same-family pairs from the universe
curl -X POST <x402-pay> https://api.usenami.io/v1/perp/oracle-families
# python sketch
spread = pay("/v1/perp/funding-spread")
families = pay("/v1/perp/oracle-families")
same_fam = {(p["a"], p["b"]) for p in families["pairs"]}
clean = [s for s in spread if (s["long"], s["short"]) not in same_fam]
ranked = sorted(clean, key=lambda s: -s["spread_bps"])[:20]The honest disclaimer: We surface what we have. Some venues don't publish next-settle funding estimates — those rows return null, not an interpolated guess. Stale-data flags are in the /v1/venues/health endpoint. If a number looks weird, /v1/health is the first place to check.
Read the full API reference, try a request from the in-browser sandbox, or wire it into a Claude / Cursor / ElizaOS agent via our MCP server.