AI agents work best when they can understand historical market activity, not just where prices end up.
FinFeedAPI provides historical OHLCV and reference data across 40+ exchanges, with detailed Native IEX historical microstructure datasets including trades, Level 1 quotes, Level 2 price levels, Level 3 order book events, system events, and administrative messages.
This gives AI teams access to both broad historical price data and deeper exchange-level context for supported Native IEX workflows.
Most financial AI workflows start with price history. OHLCV is useful for understanding what happened to a stock, but it does not capture all the activity behind price formation.
Trades, quotes, liquidity changes, order flow, trade conditions, and exchange events provide additional context around how markets operate.
Without structured access to this information, AI agents may see the outcome of market activity without the exchange-level events that surrounded it.
A candle shows where a price opened, moved, and closed. It does not show the sequence of trades, quotes, and liquidity changes behind that movement.
Without historical depth and order-level events, agents cannot directly analyze how liquidity appeared, changed, or disappeared on an exchange.
Treating every trade as an identical print ignores odd lots, extended-hours activity, and other conditions that can affect analysis.
Session transitions, auctions, operational halts, and changes in trading status can provide important context around unusual market activity.
Models trained only on clean price series learn a simplified representation of historical activity rather than the exchange-level events that contributed to it.
An OHLCV candle can tell an agent that a stock moved from one price to another.
It cannot show everything that happened inside that movement.
For supported Native IEX data, an agent can investigate questions such as:
This is the difference between giving an AI agent historical prices and giving it deeper exchange-level context.
FinFeedAPI combines standardized historical stock data with detailed Native IEX microstructure datasets for workflows that require deeper market context.
The Stock API provides historical OHLCV and reference data through a standardized interface, plus Native IEX microstructure datasets such as trades, Level 1 quotes, Level 2 price-level updates, Level 3 order book events, system events, and administrative messages for supported symbols and dates. AI agents can move beyond the final candle and investigate the activity surrounding a price movement.
Native IEX Level 1, Level 2, and Level 3 data provide different views into exchange-level liquidity and order activity. Agents can analyze best bid and ask conditions, price-level depth, and individual order lifecycle events instead of relying only on price and volume proxies.
Native IEX historical trade data includes flags for conditions such as odd lots, extended hours, intermarket sweeps, trade breaks, trade-through exemptions, and single-price crosses. Agents can use these fields to distinguish different types of trading activity rather than treating every print identically.
Native IEX system events identify events such as start and end of messages, system hours, regular market hours, and session-state transitions. This helps agents place historical activity within the appropriate exchange session context.
Administrative messages provide additional information including trading status, auctions, operational halts, official prices, security directory information, retail liquidity indicators, and other symbol-level context. This can help explain periods that might otherwise look unusual when viewed only through price data.
Combining historical prices with supported Native IEX microstructure data opens the door to richer AI research and analysis workflows.
An agent can identify a movement in historical OHLCV and then inspect available Native IEX trades, quotes, order book activity, and exchange events around the same period.
Instead of stopping at what changed, the workflow can investigate what activity was observed around the change.
Agents can use Native IEX Level 1 and Level 2 data to examine bid and ask conditions, displayed size, spreads, and price-level depth.
This provides an exchange-level view of how displayed liquidity changed over time.
With Native IEX Level 3 data, agents can analyze individual order book events such as additions, modifications, deletions, executions, and book-clearing events.
This allows workflows to examine sequences of order activity instead of treating the book as a static snapshot.
Trade-condition flags help agents distinguish standard trades from odd lots, extended-hours activity, intermarket sweeps, trade breaks, single-price crosses, and other supported conditions.
Agents can use system events for session timing and state transitions, while administrative messages provide symbol-level context such as trading status, auctions, and operational halts.
An agent can start with OHLCV, identify a period of interest, inspect Native IEX trades and quotes, move deeper into Level 2 or Level 3 data, and check system or administrative events for additional context.
The result is a research workflow that moves between different layers of historical data instead of relying on a single price series.
FinFeedAPI provides broad historical price coverage alongside deeper Native IEX datasets for supported workflows.
| Data | What it gives the agent | Scope |
|---|---|---|
| OHLCV | Historical price and volume data | 40+ exchanges |
| Reference & Metadata | Exchange and symbol information | Broad Stock API coverage |
| Trades | Individual transactions and supported trade-condition flags | Native IEX |
| Level 1 | Best bid, best ask, and top-of-book size | Native IEX |
| Level 2 | Displayed liquidity across price levels | Native IEX |
| Level 3 | Individual order lifecycle events | Native IEX |
| System Events | System hours, regular market hours, start/end messages, and session-state transitions | Native IEX |
| Administrative Messages | Trading status, auctions, operational halts, official prices, security directory, retail liquidity indicators, and other symbol-level context | Native IEX |
This distinction lets teams use broad historical stock coverage for price-based workflows while going deeper into exchange-level microstructure where Native IEX data is available.
| What AI agents need | Price-only workflow | With FinFeedAPI |
|---|---|---|
| Historical price movement | OHLCV shows the aggregated result | Historical OHLCV across 40+ exchanges through a standardized interface |
| Trade-level context | Individual transactions may be unavailable | Native IEX trades provide individual transaction data and trade-condition flags |
| Liquidity signals | Liquidity may be approximated using volume or spread proxies | Native IEX Level 1 and Level 2 provide top-of-book and price-level liquidity data |
| Order flow | Individual order activity is invisible | Native IEX Level 3 exposes supported order lifecycle events |
| Trade conditions | Trades may be treated as identical prints | Native IEX trade flags identify odd lots, extended hours, sweeps, breaks, crosses, and other conditions |
| Session context | Market phases may need to be inferred | Native IEX system events provide system-hours and regular-market-hours context |
| Symbol-level events | Unusual periods may lack explanation | Native IEX administrative messages provide trading status, auction, halt, and other symbol-level context |
| Research depth | Analysis remains primarily price-based | Agents can combine broad historical price data with deeper Native IEX microstructure where supported |
FinFeedAPI provides multiple interfaces for working with historical stock data.
FinFeedAPI provides a hosted MCP server for historical stock data.
Supported MCP tools allow compatible AI applications and agents to discover exchanges and symbols, retrieve historical OHLCV, and access supported Native IEX historical resources.
This provides a structured way to connect tool-using AI workflows to FinFeedAPI without implying that every Stock API dataset is exposed through every MCP tool.
REST provides direct programmatic access to historical stock resources for applications, scripts, research systems, and backend workflows.
Use it when your application controls the retrieval logic and knows which historical resources it needs.
JSON-RPC provides a structured RPC interface for supported historical stock workflows.
This gives teams another integration option for incorporating FinFeedAPI data into automated applications and research infrastructure.
A price-based agent can identify that something happened.
A richer research workflow can investigate the historical activity around it.
By combining broad historical OHLCV with detailed Native IEX data where supported, FinFeedAPI gives AI teams more context for investigating these questions.
Start with historical stock prices. Go deeper when your workflow needs more context.
FinFeedAPI provides historical OHLCV and reference data across 40+ exchanges, plus detailed Native IEX trades, quotes, order book events, system events, and administrative messages for supported symbols and dates.
