Skip to main content

Quant Data API: Options Flow, Gamma Exposure & Dark Pool Data

Get programmatic access to real-time options flow, gamma exposure (GEX), and dark pool data. Generate your API key and connect via REST or MCP in minutes.

Written by Andrew Hiesinger

Quant Data API: Options Flow, Gamma Exposure & Dark Pool Data

Generate your API key and connect it to Claude, ChatGPT, or Cursor via MCP (no code required), or call the REST API directly.

tl;dr: The Quant Data API gives programmatic access to the same exchange-licensed options flow, Greek exposure, and equity data behind every Quant Data dashboard. This guide covers three steps: generating an API key, connecting it to Claude or ChatGPT via the MCP server (no code required), and sending your first REST request for direct integration.

Quick Links

What the Quant Data API gives you

The API is a single interface to 30+ endpoints covering options flow, Greek exposure, dark-pool activity, IV surfaces, open interest, and equity price data. Every endpoint uses the same shape: a POST request with a JSON body and a Bearer token. The lookback window spans more than 365 days; you get 240 requests per minute, and all data is exchange-licensed through OPRA.

There are two ways to use it.

  • Through an AI assistant (MCP). Connect the API to Claude, ChatGPT, Cursor, or any MCP-compatible client. Ask market questions in plain English. The model picks the right endpoint, builds the query, and returns the answer. No code, no JSON, no query building.

  • Through code (REST). Call the endpoints directly with curl, Python, or any HTTP client. You get structured JSON back and full control over processing.

Both paths use the same API key and draw from the same quota. This guide covers both, so pick the one that fits.

Who this is for: Quant and algo traders, fintech developers, trading-bot builders, and AI builders who want programmatic access to options flow, gamma exposure (GEX), and dark pool data through code (REST) or natural language (MCP). If you've been inferring dealer positioning from candles, this is the data behind it.

Step 1: Generate your API key

This step is the same regardless of how you'll use the API. You'll need an active API subscription to get started. MCP clients create their own key automatically when you connect, while REST requests authenticate with the key you generate here.

  1. Pick an API plan. Head to quantdata.us/pricing and subscribe to an API plan. Any active subscription can generate a key immediately.

    Quant Data API pricing page showing the available API subscription plans

  2. Create your key. Open the API keys page in your settings and click Create API key.

    Quant Data settings API keys page with the Create API key button

  3. Copy it immediately. The full key is displayed only once. Keys are 35 characters long and start with qd_. If you lose it, generate a new one.

    Newly generated Quant Data API key shown once, starting with qd_

  4. Store your key like a password. Put it in a password manager or environment variable. Never paste it into a public repo or shared doc.

Path A: Connect to Claude, ChatGPT, or Cursor (no code)

This is the fastest path to querying your data. You'll connect the API to an AI assistant using MCP (Model Context Protocol), an open standard that lets LLMs call external tools. Once connected, every Quant Data endpoint becomes a tool the model can use when you ask a question.

The MCP server URL is the same for every client:

https://api.quantdata.us/mcp

No installation, no local server. It's hosted on the same domain as the REST API.

Claude Desktop

  1. Click Customize and then Connectors.

    Claude Desktop Customize menu opening the Connectors settings

  2. Claude Desktop Connectors sidebar with the Add custom connector option

  3. Click Connectors in the sidebar. Then click the + icon and select Add custom connector.

    Adding the Quant Data MCP server URL as a custom connector in Claude Desktop

  4. Fill out the custom connector fields with these entries. Name: Quant Data. Remote MCP Server URL: https://api.quantdata.us/mcp

    Authorizing the Quant Data MCP connection in Claude Desktop

  5. Then connect to Quant Data. This will prompt you to authorize the action with your Quant Data account.

    Claude Desktop connectors list confirming Quant Data is connected

  6. Verify. Click the plus symbol and hover over connectors to confirm you're connected to Quant Data.

ChatGPT

MCP connectors in ChatGPT require Developer Mode. Developer Mode is only available on Plus, Pro, Business, Enterprise, or Education plans.

Enabling Developer Mode in ChatGPT Advanced settings to add an MCP connector

  1. Enable Developer Mode. Open Settings → Apps → Advanced settings and toggle on Developer Mode.

    Creating the Quant Data MCP connector app in ChatGPT with the server URL

  2. Click the back arrow once, then click Create app. Fill out the name with Quant Data and the Connection with https://api.quantdata.us/mcp. Then click "I understand and want to continue." This is a standard warning for all custom MCP servers. Quant Data's server is hosted on the same domain as the REST API and only uses your existing API key. With ChatGPT's OAuth feature this works automatically, with no further setup required.

    Selecting Quant Data from the More menu in ChatGPT

  3. To use Quant Data, click the plus button, hover over More, and select Quant Data.

Cursor

Open Cursor Settings → MCP, add a new server, and paste this into ~/.cursor/mcp.json:

{
  "mcpServers": {
    "quantdata": {
      "url": "https://api.quantdata.us/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Restart Cursor to load the tools.

Claude Code (terminal)

One command, no config file:

claude mcp add --transport http -s user quantdata \
  https://api.quantdata.us/mcp \
  --header "Authorization: Bearer <YOUR_API_KEY>"

Other clients

VS Code (Copilot Chat), Windsurf, Cline, Gemini CLI, and Goose all support MCP. Config snippets for each are in the MCP server documentation.

Ask your first question

With the connection live, try a real market question.

Quant Data API returning gamma exposure and dark pool data in a chat reply

A few prompts to try:

  • "What's the net call vs put drift on AAPL today?"

  • "Show me the biggest options flow gainers from yesterday."

  • "What does the IV rank look like for TSLA over the past 30 days?"

  • "Are there any unusual dark pool prints in QQQ?"

  • "What does the Gamma Exposure (GEX) environment look like today?

The model reads the Quant Data tool catalogue, picks the right endpoint, fills in the parameters, and returns the answer. You don't need to know which endpoint to call or how to structure the request. The model handles that.

Tip for better results: Name the specific concept you're after. "Net call drift on SPX" maps to a tool faster than "what's happening with SPX options." Anchoring a time window ("during today's session," "over the last five trading days") also helps the model build the right query on the first try. More tips in the MCP docs.

Path B: Code with your data (REST API)

If you're building dashboards, alerts, or backtests, the REST API gives you structured JSON and full control. Every endpoint is a POST with a JSON body. No query strings, no path parameters.

Here's the simplest possible request. It calls Gainers / Losers with an empty body, which defaults to the latest trading session:

curl -X POST https://api.quantdata.us/v1/options/tool/gainers-losers \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{}'

The response is a JSON object keyed by ticker:

{
  "data": {
    "AAPL": {
      "bearishPremium": 4821330.50,
      "bullishPremium": 6128974.25,
      "premium": 11402108.75,
      "premiumRatio": 0.787,
      "tradeCount": 18472,
      "volume": 41208
    }
  }
}

Premium values are in USD. premiumRatio is bearish/bullish. Below 1 means more bullish flow. To narrow it down, add a filter or filterExpression to the request body:

curl -X POST https://api.quantdata.us/v1/options/tool/net-drift \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "sessionDate": "2026-06-06",
    "filter": { "ticker": "NVDA" }
  }'

The Quickstart guide walks through filtering, response structure, and the filter expression DSL in detail. The full endpoint reference covers all 30 endpoints with request/response examples.

Python

import requests
import os

API_KEY = os.environ["QD_API_KEY"]
url = "https://api.quantdata.us/v1/options/tool/net-drift"

resp = requests.post(
    url,
    headers={
        "Authorization": f"Bearer {API_KEY}",
        "Content-Type": "application/json",
    },
    json={
        "filter": {"ticker": "AAPL"},
    },
)

data = resp.json()
for ts, bucket in data["data"].items():
    print(f"{ts}: net call ${bucket['netCallPremium']:,.0f}")

FAQ

Do MCP tool calls count against my rate limit?
Yes. One MCP tool call = one REST request against your 240/min quota. You can mix MCP and REST on the same key.

Can I use the same key for MCP and REST?
Yes. One key, one quota, one subscription.

What happens if I hit the rate limit?
A 429 response with a Retry-After header. The MCP server surfaces the same error so the model can back off and retry.

Which ChatGPT plans support MCP?
Plus, Pro, Business, Enterprise, and Education. Free does not have Developer Mode.

Is the MCP server hosted?
Yes. Nothing to install, nothing to run locally. Your client connects to the same domain as the REST API.

What data does the API cover?
US options flow, Greek exposure (GEX, VEX, DEX, CHEX), dark-pool prints, open interest, IV surfaces, equity OHLC, exchange notifications, and ticker-tagged news. All exchange-licensed with 365+ day lookback.

Start building with the Quant Data API.
​Get your API key · Read the docs · Join the community

Did this answer your question?