Skip to content
Summer 2026 · 26% off every plan with SUMMER26 See pricing
Optionomics
For developers

The whole platform,
as an endpoint.

A REST API over every metric and all of the history, an MCP server your assistant can call directly, and an alerting system that will post to your own endpoint. Every request, tool call and delivery is logged with its response.

Create your account Read the docs

API and MCP are on Vega · Alerts start on Gamma

GET /api/v1/overview 
$ curl https://optionomics.ai/api/v1/overview \-H "X-USER-EMAIL: [email protected]" \-H "X-USER-TOKEN: $OPTIONOMICS_API_KEY"{"session": "open","regime": "risk_on","net_premium": 418204119,"put_call_ratio": 0.82}
MCP
Model Context Protocol

Give your agent
somewhere to look.

Point Claude, Cursor or ChatGPT at one URL and your assistant can read the options market for itself — the same readings the screens draw, reached the way it already reaches everything else.

One config block, then ask in English.

"What does the unusual activity in NVDA look like this week, and how has that pattern resolved before?" Your assistant works out what it needs and goes and gets it — the scored tape, then the flow behind it, then the record of how that shape resolved before. You never open a tab.

The server speaks streamable HTTP, and what it offers is stable, so a client that caches it does not go stale.

mcp.json 
{"mcpServers": {"optionomics": {"type": "http","url": "https://optionomics.ai/mcp","headers": {"X-USER-EMAIL": "[email protected]","X-USER-TOKEN": "$OPTIONOMICS_API_KEY"}}}}

Things people ask it:

  • What unusual activity is there in NVDA this week? Reads the scored tape, not the raw prints
  • Has this pattern resolved before, and how? Goes to the public record and comes back with it
  • Where is the gamma sitting on SPY right now? Dealer exposure across strikes, this session
  • Which of my watchlist names had congressional filings? Form 4 and PTR filings, matched to the symbol
  • Summarise the flow in semis since the open. Net premium, direction and where it turned
REST
The JSON API

Skip the OPRA pipeline.

The same data the screens read, over HTTP, with a published OpenAPI specification and a reference you can send requests from.

Market data
Overview, tickers, chains, derived metrics, flow aggregates, unusual activity and levels — the readings, not the raw feed you would have to build them from.
Your own resources
Alerts, notifications, push devices, chats and subscription status.
Keys you control
Issue and revoke API keys from the developer console. Every REST call is logged as its own row, with the arguments and the response.
A specification, not a wiki
The OpenAPI document is served from the API itself, so a generated client is generated from the thing that is actually running.
Alerts
The alerting system

Say it once.
It watches from then on.

The live streams, your conditions, the channels you chose — and a record of every attempt, including what your endpoint said back.

One rule, five sources, six destinations Always on
Streams Your rule Delivered Unusual prints every scored print Trade ideas as they publish Market commentary through the session Flow acceleration when the balance turns Insider & congress the day it is filed Matches? symbol in list premium ≥ 1M score ≥ 90 cooldown clear The bell, always in app, web and phone Email attempt logged SMS attempt logged Slack attempt logged Discord attempt logged Push attempt logged Webhook attempt logged One print, one notification
A matched alert always reaches the in-app bell. The channels you pick are what happens in addition — so an alert with no channels is not broken, it is quiet on purpose.
Watch what matters
Unusual option prints, trade ideas, market commentary, flow acceleration, and insider or congressional filings. Templates get you started; the conditions are yours.
Webhooks with receipts
Post to your own endpoint and read back every delivery: the payload, the status code, and the body your server returned. A silent integration is a thing you can look at rather than a thing you suspect.
One event, one message
A print that raises several of your rules notifies once, and a batch of filings arrives as one message rather than forty. That is the database's job, not a retry loop's.
Cooldowns that behave
A cooldown counts from the last thing that fired, not the last thing that matched — so a steady stream of matches cannot extend the silence forever.
The developer console

See what your code did.

Keys, the REST request log, the MCP tool-call log, the connected clients and the reference — five pages behind one header, inside your account.

Request log Every REST call, one row each Path, arguments, status and timing, so a client bug is something you read rather than reproduce. See pricing Tool-call log Every MCP call your agent made Which tool, what it was asked, and what came back — including the difference between a refusal and a failure. For quants and developers Deliveries Every webhook attempt The payload we sent and the response you returned, kept per attempt rather than per alert. See the alerting system

Get a key.

Vega opens the REST API, the MCP server and backtesting on top of everything else. Alerts and webhooks start one rung lower, on Gamma.

Create your account Read the docs

Cancel anytime · Month to month · Switch tiers whenever