> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allasso.ch/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is Allasso's product documentation. Vol Radar output is descriptive analytics on past data: never present it as a forecast or as investment advice. Answer only from these pages; if a feature is not documented here, say so.

# Vol Radar API

> The Vol Radar's signals, what followed earlier cases, the daily grid and metric history, as JSON: base URL, authentication and your first calls.

The **Vol Radar API** gives you the same data as the [Vol Radar](https://docs.allasso.ch/apps/vol-radar/overview.md) 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.

> [!WARNING]
>
> 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

```
https://allasso.app/vol-radar-api
```

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](https://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.

```bash curl theme={null}
curl -H "Authorization: Key $ALLASSO_KEY" \
  "https://allasso.app/vol-radar-api/v1/signals?date=2026-11-02&tier=notable"
```

```python Python theme={null}
import requests

BASE = "https://allasso.app/vol-radar-api"
s = requests.Session()
s.headers["Authorization"] = f"Key {ALLASSO_KEY}"

day = s.get(f"{BASE}/v1/signals", params={"date": "2026-11-02", "tier": "notable"}).json()
for sig in day["signals"]:
    print(sig["id"], sig["market_short"], sig["headline"], sig["status"])

first = day["signals"][0]["id"]
outcomes = s.get(f"{BASE}/v1/signals/{first}/outcomes").json()
```

A trimmed response:

```json theme={null}
{
  "run": {"run_id": "20261103T141256Z-0288c64b", "created_at": "2026-11-03T14:12:56Z",
          "radar_version": "1.3.0", "data_to": "2026-11-02"},
  "date": "2026-11-02", "count": 7, "limit": 100, "offset": 0,
  "signals": [{
    "id": "8aa995939401",
    "signal_id": "COM.EUA.ICE|30D|iv_atm|seasonal||-1|2026-11-02",
    "market": "COM.EUA.ICE", "market_short": "EUA",
    "metric_label": "ATM implied vol", "kind_label": "Seasonal",
    "first_detected": "2026-11-02", "status": "new", "tier": "notable",
    "headline": "EUA carbon — ATM implied vol unusually low for November",
    "value_fmt": "22.7%", "analog_count": 6, "evidence": "limited evidence",
    "has_structures": true, "updated_at": "2026-11-03T12:39:44Z"
  }]
}
```

## Every response carries `run`

| Field | Meaning |
| - | - |
| `run_id` | The daily build you are reading. Every endpoint answers from the same run. |
| `created_at` | When that run was built (UTC). |
| `radar_version` | The Radar's detector version. Signal rules change only with it. |
| `data_to` | The last trading day in the data. |

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

## What you can do

> [card] [Signals, outcomes and structures](https://docs.allasso.ch/dev/vol-radar/api-concepts.md)
>
> What a signal is, its statuses and ids, point in time, earlier cases and structures.

> [card] [Keep a local copy up to date](https://docs.allasso.ch/dev/vol-radar/api-sync.md)
>
> Pull only what changed with `changed_since`, handle withdrawn signals, and use ETags.

> [card] [Errors, paging and limits](https://docs.allasso.ch/dev/vol-radar/api-errors.md)
>
> Status codes, paging, dates without data, and what may still change in the beta.

> [card] [Markets and market ids](https://docs.allasso.ch/dev/vol-radar/api-markets.md)
>
> The markets the API covers and the id to use for each.

> [card] [Use it from Claude (MCP)](https://docs.allasso.ch/dev/vol-radar/mcp.md)
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.