Model Context Protocol & Developer Access

Options Flow API for Developers & AI Agents

Query recent options-flow alerts and contract prints through Pineify MCP. Compare market and sector snapshots, retaining observation times, missing values and result limits.

Connect and verify

Connect Flow Data Directly to Your AI Stack

Use a client that supports remote Streamable HTTP and Bearer authentication. Add the endpoint, initialize the connection, and inspect tools/list before making a call. The configuration example is client-dependent; the JSON body is for an already initialized client, not a standalone HTTP command.

  • Keep the token in your client secret settings, outside shared code.
  • Use camelCase arguments exactly as the discovered schema defines.
  • Inspect structuredContent, partial, warnings and snapshot times.
  • Treat null fields and unavailable components as missing evidence.
{
  "mcpServers": {
    "pineify": {
      "url": "https://agents.pineify.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PINEIFY_API_TOKEN"
      }
    }
  }
}

Available Options Flow MCP Tools

Four read-only tools for distinct research tasks. Results are bounded snapshots, not an unfiltered exchange tape.

find-options-flow-alertsMCP tool

Find a bounded set of recent alerts for up to ten US symbols. Sentiment is a derived label, not participant identity or a price forecast.

Key Parameters:

symbols (up to 10)optionType: any | call | putminPremiumUsd (optional)sweepsOnly (default false)limit: 1–50 (default 20)
get-option-contract-flowMCP tool

Use an exact contractId returned by the alert tool to inspect recent prints, NBBO fields and available Greeks with source-print provenance. Missing values remain null.

Key Parameters:

contractId (required, returned ID)marketDate: YYYY-MM-DD (optional)side: any | ask | bid | midminPremiumUsd (default 0)limit: 1–50 (default 20)
get-market-tideMCP tool

Get one market-date snapshot or bounded intraday series plus top-impact symbols. This tool does not return sector detail.

Key Parameters:

detail: summary | seriesmarketDate (optional)granularity: 1m | 5motmOnly (default false)pointLimit: 1–390 (series only)
get-sector-flow-snapshotMCP tool

Compare eleven latest sector ETF contract snapshots. An optional selected-sector series covers constituent options; these are different scopes and can have different observation dates.

Key Parameters:

detail: summary | seriessector (required for series)marketDate (selected series only)granularity: 1m | 5mpointLimit: 1–390 (series only)

Choose the right query and inspect its limits

Use the returned schema and provenance to decide whether the data answers your question. These tools do not place orders.

CapabilityReturned scopeInput / output detailInterpretation limit
Recent flow alertsObserved alert records and derived sentimentsymbols, optionType, premium, DTE and flagsCheck partial, warnings and page.truncated; no continuation cursor.
Contract printsExact returned contractIdRecent prints; nullable Greeks and NBBODo not invent an O: prefix or assume every Greek is present.
Market tideOne date; summary or bounded seriespointLimit only with detail=seriesObserved flow is not a forecast or a complete options tape.
Sector snapshotLatest sector ETF contract flowOptional constituent-options tide for one sectormarketDate does not date-filter the eleven latest ETF rows.
AccessExpert or above; Bearer authenticationMCP initialization, discovery and tool callsRate limits and service availability apply; check current plan terms.

References: MCP Streamable HTTP transport, TradingView data request scope, and Pineify MCP setup. Tool names and arguments were checked against the current Pineify schemas on October 21, 2026.

Frequently Asked Questions

Answers to common questions about options flow APIs, MCP integration, and data formats.

Connect a research client to Pineify MCP

Check authentication and plan access, discover the current schemas, then query a small result set and inspect its provenance.