- API
- Volatility API
Volatility API
Implied volatility,
as an endpoint.
IV rank, IV percentile, the 52-week range, the vol cone, the term structure and the premium over realized. Each one is a GET that returns the number the terminal draws.
A real response
This is what
comes back.
Captured from the live endpoint on 2026-09-07, lists cut to a few rows so it fits on a page. The shape is exactly what your code receives.
{
"current_iv": 34.43,
"data_source": "iv_rank_1y",
"historical_data_points": 252,
"is_full_year": true,
"iv30d": 33.05,
"iv_basis": "vendor_ivrank_series",
"iv_max_52w": 48.38,
"iv_mean": 38.53,
"iv_median": 38.39,
"iv_min_52w": 32.01,
"iv_percentile": 12.0,
"iv_percentile_1m": 66.67,
"iv_percentile_1y": 12,
"iv_percentile_source": "cores_ivPctile1y",
"iv_rank": 14.79,
"iv_rank_1m": 54.08,
"iv_rank_1y": 14.79,
"iv_state": "VERY_LOW",
"iv_std": 3.31,
"iv_stdv_from_mean": -1.49,
"iv_units": "percentage_points",
"lookback_days": 252,
"ticker": "NVDA",
"timestamp": "2026-09-07T16:50:49.691068"
}Every response is wrapped as {"success": true, "data": {...}}. Errors use the same envelope with an error string and a status code that means what it says.
Call it three ways. Same token, same JSON.
curl -H "Authorization: Bearer avmcp_YOUR_TOKEN" \
"https://apexvol.com/api/mcp/data/iv-rank/NVDA"import requests
r = requests.get("https://apexvol.com/api/mcp/data/iv-rank/NVDA",
headers={"Authorization": "Bearer avmcp_YOUR_TOKEN"})
d = r.json()["data"]
print(d["iv_rank"], d["iv_percentile"], d["iv_state"])
What is NVDA's IV rank right now, and how does its term structure look?
The assistant calls get_iv_rank and answers from the JSON above.More prompts for this family in the prompt library. Set the server up in Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, Windsurf or Gemini CLI.
Field by field
What each
number means.
iv_rank- Where today's IV sits between the 52-week low (0) and high (100).
iv_percentile- The share of the last year's days that closed with IV below today's.
current_iv- The IV the rank was computed from, in percentage points.
iv30d- The platform's 30-day constant-maturity IV, the basis for the VRP endpoints.
iv_min_52w, iv_max_52w- The bounds the rank is measured against.
iv_state- A label from VERY_LOW to VERY_HIGH so a caller can branch without thresholds.
iv_stdv_from_mean- How many standard deviations today's IV is from its one-year mean.
iv_basis, iv_units- Which series the numbers come from and their units. Every volatility endpoint carries both.
The family
12 endpoints,
one prefix.
All under https://apexvol.com/api/mcp/data. Parameters are bounded and the docs say the bounds; out-of-range values are clamped or rejected, never silently changed. The reference has every response field.
| Method | Path | Parameters | Returns |
|---|---|---|---|
GET | /iv-rank/{ticker} | lookback_days 20 to 1260, default 252 | IV rank and percentile with the 52-week range, mean and standard deviation, and the series they were built on. |
GET | /volatility-cone/{ticker} | periods, CSV of tenors in days | Realized-vol cone per tenor against the chain-interpolated implied vol at the same tenor. |
GET | /term-structure/{ticker} | num_expirations 1 to 20 | At-the-money IV by expiration, so contango and inversion are a single array. |
GET | /vrp/{ticker} | lookback_days 5 to 252 | Volatility risk premium: 30-day implied minus realized over the lookback, in percentage points. |
GET | /vrp/{ticker}/timeseries | lookback_days, hv_period | IV versus HV through time, for charts and regressions. |
GET | /vrp/{ticker}/expirations | max_expirations 1 to 30 | Where on the curve the premium sits, expiration by expiration. |
GET | /skew/{ticker} | view analysis, history or curvature | Put and call skew, curvature and regime bands. |
GET | /hv-regimes/{ticker} | view dashboard, signals, decomposition or ex_earnings | Realized-vol windows, the HV term structure and regime crossovers. |
GET | /iv-opportunities/{ticker} | none | Mean-reversion setups in the IV series. |
GET | /relative-value/{ticker} | days 20 to 1000 | IV percentile against SPY and the sector, with a ratio mean-reversion signal. |
GET | /monies/{ticker} | surface implied, forecast or comparison | The smoothed implied surface and the forecast surface at standard moneyness points. |
GET | /vix | none | VIX level, change and term-structure state. |
The same data, in plain English
7 MCP tools
wrap this family.
Connect the ApexVol MCP server and an assistant can call these by name. One URL, a sign-in, no token to paste.
- get_iv_rank
- get_volatility_cone
- get_volatility_risk_premium
- get_term_structure
- find_iv_opportunities
- get_vix_snapshot
- get_monies_surface
Set it up in:
What people build
Three things
this is for.
Access
- Auth
- Bearer token, prefix
avmcp_, created under Account, then API Access. Shown once, hashed at rest, rotates in one click. - Limits
- 60 requests a minute and 1,000 an hour per token, with a 10,000-request monthly budget per account. Every response carries the remaining counts in headers.
- Plans
- Included with every paid plan from $55 a month. Each endpoint follows the tier of its web feature; Pro unlocks the full surface.
- Spec
- OpenAPI 3.1 at /docs/api/openapi.json and the whole reference as one Markdown file at /docs/api/apexvol-api.md.
Questions
Asked before
the first call.
What is the difference between iv_rank and iv_percentile in the response?
iv_rank places today's IV between the 52-week low and high on a 0 to 100 scale. iv_percentile is the share of trading days in the lookback that closed with IV below today's level. A single spike can push the rank down for a year while barely moving the percentile, which is why both are returned.
Which IV series is the rank built on?
The response says so: iv_basis names the series and data_source names the lookback. The rank uses the vendor's IV-rank series, and iv30d is the 30-day constant-maturity IV the VRP endpoints use. The two can differ by a point or two, and the fields are labelled so a caller never has to guess.
How fresh is the data?
Live during US market hours, from the same feed the ApexVol terminal reads. Each response carries a timestamp. The historical arrays behind the rank and the cone are refreshed daily after the close.
What units are volatility numbers in?
Percentage points throughout: an IV of 34.43 means 34.43 percent annualized. Where a field is decimal instead (the chain's per-contract IV), the response says iv_units: decimal next to it.
Included with
every paid plan.
From $55 a month, tier-matched: your token queries the data your plan includes and Pro unlocks the full surface.
Real market data, not a sandbox. See it live on AAPL.