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

A REST API and an MCP server.

A REST API over every reading and all of the history. A server your AI assistant can drive by itself. Alerts that post to your own endpoint. And a log of every request and every call, with what came back.

Create your account Read the docs

The API and MCP server 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}
30
REST endpoints, in 6 groups
23
MCP tools your assistant can call
6
Channels an alert can arrive on
15+ yrs
Of history behind every one

Counted from the reference, the MCP registry and the alert channels themselves, rather than typed into this page. Read the API reference

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 our own screens draw, reached the way it already reaches everything else.

One block of settings, then just ask.

"Is anything unusual happening in NVDA this week, and how has that turned out before?" Your assistant works out what it needs and goes and gets it — the scored trades, then the money behind them, then the record of how that shape resolved the last few times. You never open a tab.

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

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:

  • Is anything unusual happening in NVDA this week? Reads the trades we have already scored, not the raw list
  • Has this happened before, and what happened next? Goes to the public record and comes back with it
  • Are traders betting up or down on Apple today? Where the money went, and when it turned
  • Did anyone in Congress trade anything on my watchlist? Insider and congressional filings, matched to the stock
  • What moved the chip stocks since the open? The whole sector, summarised in a paragraph
REST
The JSON API

Do not build the data pipeline.

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

Market data
The market overview, individual stocks, every contract, the computed readings, where the money went, the unusual trades and the price levels — the finished readings, not the raw feed you would have to build them out of.
Your own account
Your alerts, your notifications, your registered phones, your chats and your 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 page
The OpenAPI document is served by the API itself, so a generated client is generated from the thing that is actually running rather than from a description of it somebody updated last year.
Alerts
The alerting system

Say it once.
It watches from then on.

The things we watch, the conditions you set, the places you chose to be told — and a record of every attempt, including what your own endpoint said back.

One rule, five things watched, six places to be told 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
Anything that matches always reaches the bell in the app. The channels you pick are what happens as well — so an alert with no channels is not broken, it is quiet on purpose.
Watch what matters
Unusual trades, new trade ideas, the daily write-ups, sudden shifts in where the money is going, 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: what we sent, the status code, and the body your server returned. An integration that has gone quiet is something you look at rather than something you suspect.
One event, one message
A trade that trips several of your rules notifies you once, and a batch of forty filings arrives as one message rather than forty. That is the database's job, not a retry loop's.
Quiet periods that behave
A quiet period counts from the last thing that actually reached you, not the last thing that matched — so a steady stream of matches cannot keep extending the silence forever.
The developer console

See what your code did.

Your keys, the request log, the log of what your assistant asked for, the clients that are connected, and the reference — five pages behind one header, inside your account.

Request log Every REST call, one row each The path, the arguments, the status and the timing — so a bug in your client is something you read rather than something you reproduce. See pricing Tool-call log Everything your assistant asked for Which tool, what it was asked, and what came back — including the difference between being refused and failing. For quants and developers Deliveries Every webhook attempt What we sent and what your server said back, kept per attempt rather than per alert. See the alerting system

Get a key.

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

Create your account Read the docs

Cancel anytime · Month to month · Switch tiers whenever