Skip to main content
The Vol Radar API gives you the same data as the Vol Radar app, as JSON: the Radar’s signals for energy and environmental markets, how rare each move was against the market’s own history, what followed earlier moves of the same kind, and the daily grid of every market and metric. It is read-only and end of day. It is in closed beta.
Vol Radar describes what options markets are pricing and what happened after similar days in the past. It is descriptive, never a forecast, and nothing in it is investment advice. Structures and their statistics show ways to express your own view, with placeholder costs.

Base URL

Interactive docs, generated from the API itself, are at https://allasso.app/vol-radar-api/docs. Every endpoint is described in the API reference group of this section. Its request samples show Authorization: <api-key>: send the header as Authorization: Key <your-key>.

Authentication

Every request needs an API key in the Authorization header, as Key <your-key>:
  1. Log in to allasso.app with your Allasso account.
  2. Open your profile, then API Keys, and create a key.
  3. Send it with every request: Authorization: Key <your-key>.
The key carries your access: a request without a key gets 401, and a key whose account has no access to the closed beta is refused too. Keep the key secret; you can delete it and create a new one at any time.

Your first calls

1

Check the data is current

/v1/status returns the last day of data per market and the run you are reading.
2

List the day's notable signals

/v1/signals?date=…&tier=notable returns the signals active on that day, with their status that day.
3

Open one signal

/v1/signals/{id} returns its opening evidence and lifecycle; /outcomes and /structures add what followed earlier cases like it.
A trimmed response:

Every response carries run

Keep run_id with anything you store: it tells you exactly which data produced it.

What you can do

Signals, outcomes and structures

What a signal is, its statuses and ids, point in time, earlier cases and structures.

Keep a local copy up to date

Pull only what changed with changed_since, handle withdrawn signals, and use ETags.

Errors, paging and limits

Status codes, paging, dates without data, and what may still change in the beta.

Markets and market ids

The markets the API covers and the id to use for each.

Use it from Claude (MCP)

The same data as tools for Claude and other MCP clients, at /mcp.

Data timing

The data is refreshed each business morning (UTC) with the previous session’s settlements. Until the new run arrives, every endpoint keeps answering from the previous one: check run.data_to rather than the clock.
Last modified on November 4, 2026