Crypto funding rate API

What this is

A REST + x402 API that returns funding rates for every perpetual contract we track. One endpoint covers all venues; per-symbol and historical views are also available. The same data feeds our live screener at usenami.io/dashboard/funding — when you query the API you get exactly what the dashboard shows, normalized.

• Algo traders building cross-venue funding-arbitrage strategies (long the cheap side, short the expensive side, capture the spread).
• Analysts and newsletters that need a single source for funding-rate snapshots without scraping every venue individually.
• AI agents priced into per-call data via x402 — no account signup, no key rotation, on-chain settlement.
• Backtesters that need historical funding time-series with consistent timestamps across venues.

Endpoints

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):

Quickstart

x402 means the first request gets a 402 with payment requirements; your client signs a USDC transfer, retries, and gets the data. 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.

# free preview — validate the schema before paying anything
curl https://api.usenami.io/v1/preview/funding-current | jq

# paid endpoint via x402 (any x402-aware client, e.g. coinbase x402-fetch)
npx x402-fetch get https://api.usenami.io/v1/funding/current \
  --wallet <YOUR_BASE_WALLET>

# typical response (truncated)
{
  "symbol": "BTC-PERP",
  "venues": [
    { "venue": "binance",     "rate_8h_bps": 1.2,  "next_settle_at": "..." },
    { "venue": "hyperliquid", "rate_1h_bps": -4.0, "next_settle_at": "..." },
    { "venue": "okx",         "rate_8h_bps": 0.8,  "next_settle_at": "..." }
  ]
}

What you actually get

The honest disclaimer: Volume coverage and refresh cadence vary by venue. We list the source venues on /api-docs and surface any stale-data flags in the response — never silently. This is a small, builder-run API; we publish the spec at /.well-known/x402.json so you can verify the surface yourself.

FAQ