Skip to content
Eden Engine

Crypto Perpetual Funding Rate History (by Exchange & Pair)

omnial/exchange-funding-history

Given a trading pair and an exchange, returns a time series of historical perpetual futures funding rate records for that pair -- the raw rate plus its 1-hour, 8-hour, and annualized normalizations at each interval -- up to 500 records per call.

activeper callv1
Provider
Web & Business Data Network
Category
derivatives
Provider price
$0.00819 per call
Latency p50 / p95
— / —
Success rate
Verified

Provider list price; Omnial MCP charges provider cost plus a platform markup on top.

Contract

input_schema.json
{
  "type": "object",
  "required": [
    "pair"
  ],
  "properties": {
    "from": {
      "type": "string",
      "minLength": 1,
      "description": "Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD, ISO8601). Not all exchanges support historical queries; some only return recent data regardless of this value. Example: 2026-03-01."
    },
    "pair": {
      "type": "string",
      "minLength": 1,
      "description": "Trading pair (e.g. BTC/USDT). Example: BTC/USDT."
    },
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 500,
      "minimum": 1,
      "description": "Max number of records. For longer history, paginate using the last returned timestamp as the next from value. Example: 100. Defaults to 100."
    },
    "exchange": {
      "enum": [
        "binance",
        "okx",
        "bybit",
        "bitget",
        "gate",
        "htx",
        "mexc",
        "bitfinex",
        "bitmex",
        "hyperliquid"
      ],
      "type": "string",
      "default": "binance",
      "description": "Exchange identifier. Note: hyperliquid uses USDC-settled perps (e.g. BTC/USDC:USDC); pass USDC-quoted pairs when querying hyperliquid. Example: binance. Defaults to \"binance\"."
    }
  },
  "additionalProperties": false
}
output_schema.json
{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "Present only on a rejected call, e.g. an unrecognized pair. Observed value: 'HTTP_400'."
    },
    "data": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "pair": {
            "type": "string",
            "description": "The trading pair as the exchange itself denotes it -- observed WITHOUT a ':USDC' settlement suffix even when the request pair included one (requesting 'BTC/USDC:USDC' on hyperliquid returned pair 'BTC/USDC')."
          },
          "exchange": {
            "type": "string",
            "description": "Echoes the requested exchange, e.g. 'binance', 'hyperliquid'."
          },
          "timestamp": {
            "type": "integer",
            "description": "Unix seconds marking the funding interval."
          },
          "funding_rate": {
            "type": "number",
            "description": "The rate for this interval. Observed negative on some intervals (e.g. -0.0000015)."
          },
          "funding_rate_1h": {
            "type": "number",
            "description": "funding_rate normalized to a 1-hour rate."
          },
          "funding_rate_8h": {
            "type": "number",
            "description": "funding_rate normalized to an 8-hour rate."
          },
          "funding_rate_raw": {
            "type": "number",
            "description": "Identical to funding_rate on every record observed in both fixtures; kept as its own field since the vendor returns it separately."
          },
          "funding_interval_hours": {
            "type": "integer",
            "description": "How often this exchange pays funding. Observed 8 for binance, 1 for hyperliquid -- not the same across exchanges."
          },
          "funding_rate_annualized": {
            "type": "number",
            "description": "funding_rate compounded to a yearly rate."
          }
        },
        "additionalProperties": false
      },
      "description": "One entry per funding interval. Present only on a successful call."
    },
    "meta": {
      "type": "object",
      "properties": {
        "cached": {
          "type": "boolean",
          "description": "Whether this response was served from the provider's cache. Observed false on both real successful fixtures."
        }
      },
      "description": "Present only on a successful call.",
      "additionalProperties": false
    },
    "message": {
      "type": "string",
      "description": "Human-readable detail accompanying `code`. Observed value: 'Invalid input: HTTP 400'."
    }
  },
  "description": "The funding history response, as returned at routing.responseResultPath ($.output). A successful call returns `data`/`meta`; a rejected pair/exchange combination returns `code`/`message` instead -- the two shapes do not overlap.",
  "additionalProperties": false
}

Pricing

Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.

Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.

ChargeRate
Per call
Flat, regardless of what comes back
$0.00819
Cost basis
Not recorded

This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.

Updated
Sep 8, 2026