REST API · MCP Server · Multi-Channel Alerts

Code. Agents. Alerts. One source of truth.

REST for your code, MCP for your AI assistants, alerts to your inbox — same scored options dataset, no drift.

Three ways in — same options dataset REST · MCP · Alerts
REST API 200 OK 100 req/min
GET /api/v1/uoa?symbol=NVDA&min_score=85
{ "data": [{ "symbol": "NVDA", "strike": 950, "type": "C", "score": 96, "premium": 2350000, "tag": "sweep" }] }
MCP tool call Cursor / Claude / ChatGPT conversational
tools/call · uoa_lookup
{ "symbol": "NVDA", "min_score": 85 } → "NVDA $950C, sweep, 96/100 unusual, $2.35M premium"
Alert rule → SMS + Slack fan-out
WHEN unusual_score >= 90 AND symbol IN watchlist:mega-caps
THEN notify(sms, slack#flow-critical) WITH payload(full_event)
100/min
API rate limit
80+
Historical metrics
MCP
For Cursor / Claude / ChatGPT
6
Alert channels
Three integration surfaces

Three ways in. One source of truth.

Python, AI assistant, or just an alert when something unusual fires — same dataset, three doors in.

REST API

80+ metrics, JSON over HTTPS, standard auth

AGENT MODEL GET 200 { }
  • 80+ derived metrics, JSON over HTTPS
  • 100 req/min on the Vega plan (higher on request)
  • Same scoring you see in the UI — no separate "API model"
MCP Server

Wire Cursor, Claude, or ChatGPT into options data

AGENT MODEL MCP TOOLS ASSISTANT
  • Drop-in Cursor / Claude / ChatGPT configuration
  • Same auth and rate limit as the REST API
  • Tools cover flow, chains, signals, smart money, and historical analytics
Multi-Channel Alerts

Email, SMS, push, Slack, Discord, webhook — your call

AI agents and ML models triggering alerts across five delivery channels AGENT MODEL RULE score >= 90 Email SMS Slack Discord { } Webhook
  • 6 channels: email, SMS, push, Slack, Discord, custom webhook
  • Build rules on any metric the platform exposes
  • Route critical to SMS, notable to Slack, info to email
No drift between your code, your agent, and your alerts. Free to explore. Vega unlocks production rates.
Get started
Why this matters

Most options vendors give you one channel. We give you three.

Four design choices that separate this from a basic data feed.

REST for your code

JSON over HTTPS, 100 req/min on Vega. Access chains, Greeks, 80+ derived metrics, and historical analytics.

MCP for your AI assistants

Drop the MCP server into Cursor, Claude, or ChatGPT and let the assistant query options data in plain English.

Alerts where you work

Rules on any metric, fanned out to email, SMS, Slack, Discord, push, or your own webhook.

One dataset. Zero drift.

API, MCP, alerts, and workstation read from the same scored archive. What you query matches what you see.

Optionomics API vs vendor data feed + custom integration

A raw OPRA feed is not an integration.

A dozen vendors will sell you ticks. None ship with an MCP server and a 6-channel alert engine.

What you actually need
Optionomics
Vendor feed + DIY
REST API with 80+ scored / derived metrics
Partial
MCP Server for Cursor / Claude / ChatGPT integration
Unusual Score, AI Signals, Smart Money flags over JSON
Multi-channel alert delivery (email, SMS, Slack, Discord, push, webhook)
Partial
Same dataset across UI, API, MCP, and alerts
15+ years of historical chains queryable via API
Partial
Cost
Skip the integration project. Start with the API. Free plan to test endpoints. Vega plan for production.
Get started
For every trading style

Pick the workflow built for how you trade

FAQ

API & Integrations — Frequently Asked Questions

Everything we get asked about the API, MCP, and alert delivery.

The REST API and MCP server are included from the Vega plan. You can test endpoints on the free plan with a lower rate limit. Higher request rates are available on request.

MCP (Model Context Protocol) is an open standard for connecting AI assistants to data sources. With our MCP server configured in Cursor, Claude, or ChatGPT, the assistant can query live options chains, historical data, AI Signals, and Smart Money flags conversationally — without copy-paste or manual context.

Anything that needs scored options data: trading bots, research notebooks, custom dashboards, Discord bots, PDF reports, internal alerting at a fund. Access chains, Greeks, 80+ derived metrics, historical analytics, AI Signals, and Smart Money.

Build a rule from any metric we expose — minimum Unusual Score, watchlist + sweep size, AI Signal conviction, gamma exposure threshold — and route matching events to one or more channels. Each channel is independent so you can send critical-tier prints to SMS and lower-tier ones to Slack.

Email, SMS, mobile push, Slack (via incoming webhook), Discord (via webhook), and arbitrary HTTPS webhooks for your own systems. Webhook payloads include the full scored event so you can route or transform downstream.

Requests over the limit get a standard 429 response with retry guidance. The default Vega-plan limit is 100 req/min; contact us if you need a higher tier for production workloads.
Where to next

Explore the rest of the platform

Ready when you are

Wire it in. In one afternoon.

Free to test the API and MCP. Gamma unlocks alert workflows; Vega unlocks production API and MCP rates.

Cancel anytime Month-to-month Vega plan unlocks the API and MCP at production rates