KR
Utilities · x402 · early usage

Implied volatility surface for BTC and ETH from Deribit options (public API, no auth)

Implied volatility surface for BTC and ETH from Deribit options (public API, no auth). Returns ATM IV (annualized %), IV rank and IV percentile from Kronos iv_history (daily cron), term structure (weekly/1m/3m ATM IV + contango/backwardation/flat shape label)…

by kronossignals.com · discovered, not yet claimed by its owner · updated 2026-10-07

30d calls9
30d payers1
MethodGET
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Implied volatility surface for BTC and ETH from Deribit options (public API, no auth). Returns ATM IV (annualized %), IV rank and IV percentile from Kronos iv_history (daily cron), term structure (weekly/1m/3m ATM IV + contango/backwardation/flat shape label), 25-delta risk reversal (BS-approximated strikes), 10-delta wing IVs, max-pain strike across top-5 expiries, and a vol-regime label. Falls back to OKX if Deribit is unreachable. $0.03 USDC via x402.

Tags: options · implied-volatility · iv · iv-rank · iv-percentile · bazaar

Call contract

Method
GET
Input
query parameters
Output
json
Last paid call
2026-10-07
Input example from Bazaar metadata
{}
Output example
{
  "as_of": "2026-01-01T00:00:00.000Z",
  "asset": "BTC-USD",
  "atm_iv": 42.8,
  "available": true,
  "data_source": "deribit",
  "disclaimer": "Options data from Deribit public API. Informational only.",
  "iv_history_days": 45,
  "iv_percentile": 61.2,
  "iv_rank": 58.3,
  "iv_rank_note": "Based on 45 trading days of ATM IV history.",
  "max_pain_strike": 60000,
  "skew_25d": 3.8,
  "skew_note": "25-delta risk reversal: put IV minus call IV at BS-approximated 25-delta strikes.",
  "term_structure": [
    {
      "atm_iv": 44.2,
      "days_to_expiry": 3,
      "expiry": "5JUL26",
      "label": "weekly"
    },
    {
      "atm_iv": 42.5,
      "days_to_expiry": 29,
      "expiry": "31JUL26",
      "label": "1m"
    },
    {
      "atm_iv": 40.1,
      "days_to_expiry": 85,
      "expiry": "25SEP26",
      "label": "3m"
    }
  ],
  "term_structure_shape": "contango",
  "underlying_price": 61200,
  "vol_regime": "normal",
  "vol_regime_note": "ATM IV 42.8%, term structure contango.",
  "wing_10d_call_iv": 38.5,
  "wing_10d_put_iv": 49.2
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/26717.json for the price and payment options.
  3. Pay. Call GET https://kronossignals.com/api/v1/options-iv/eth. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.03 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
9 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.030x36038e1d712c5e39f35952164ec58ec2b96caee7300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x36038e1d712c5e39f35952164ec58ec2b96caee7",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "30000",
    "amountUsd": 0.03,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {},
  "type": "string"
}

Examples

curl
curl "https://kronossignals.com/api/v1/options-iv/eth"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://kronossignals.com/api/v1/options-iv/eth");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://kronossignals.com/api/v1/options-iv/eth")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
kronossignals.com
Endpoint
https://kronossignals.com/api/v1/options-iv/eth
Machine-readable
/resources/26717.json