QVeris
OPTIONS DATA CONTRACT

Free Options Data API: Coverage & Limits

Separate reference data, delayed quotes, account access, and real-time entitlement before comparing providers.

Free Options Data API: Coverage & Limits

TL;DR

Best reference-data start

Massive includes contract-reference endpoints in its free options plan, while richer price and analytics endpoints depend on tier.

Best broker-linked start

Alpaca and Tradier are practical when market data is tied to a brokerage workflow and account entitlements.

Hardest field to get free

Reliable historical quotes and complete real-time NBBO are more difficult than current contract lists or previous-day bars.

Core decision

Write down whether you need a contract catalog, a chain snapshot, tick quotes, Greeks, open interest, or backtest history.

Read an option chain as a data model

contract

Underlying, expiration, strike, call/put, multiplier, exercise style.

quote

Bid, ask, sizes, venue, event time, and quote condition.

trade

Price, size, exchange, condition, and sequence.

greeks

Model, inputs, calculation time, and whether values are vendor-derived.

open_interest

As-of date and publication lag.

corporate_action

Adjustment history for splits, mergers, and special distributions.

What “free” and “real-time” mean for this API

Free options data is unusually easy to misunderstand because an option chain combines reference data, market data, and derived analytics. A free endpoint may list every active contract but provide no current bid or ask. Another may show delayed quotes but omit Greeks, open interest, or historical snapshots.

For US listed options, OPRA licensing and display rules matter. A website that manually displays delayed quotes is not automatically an API source, and exchange pages can prohibit automated extraction. Use documented APIs and verify the plan's market-data rights rather than scraping a quote table.

The useful unit of comparison is therefore a complete strategy input. A covered-call screener needs expirations, strikes, bid/ask, open interest, volume, underlying price, and a consistent timestamp. A volatility backtest needs point-in-time chains and must avoid using today's contract metadata or Greeks in past dates.

Free access is not one thing

Access layerOften availableUsually restricted
ReferenceContracts, expirations, strikesComplete history and adjustments
Delayed market dataDisplayed delayed quotesAutomated extraction or redistribution
Broker contextQuotes for an authenticated accountUse outside account terms
Real-time OPRASometimes trial accessProduction entitlement and display rights

The fields that decide whether the data is usable

Reference contracts

Underlying, expiration, strike, call/put, multiplier, style, and listing status describe the instrument but not its market value.

Quotes and trades

Bid/ask NBBO, sizes, last trade, conditions, and timestamps are distinct. A last trade can be stale in an illiquid contract.

Derived analytics

Greeks and implied volatility depend on the pricing model, interest rate, dividend assumptions, underlying price, and timestamp.

Point-in-time history

A backtest needs contracts, quotes, corporate actions, and underlying values as they were known then—not a reconstructed current chain.

Provider comparison: access, fields, and limits

ProviderFree entryUseful fieldsMain caveat
MassiveOptions BasicContracts and selected reference/market endpoints by planReal-time, snapshots, and history vary by tier
AlpacaFree market-data planUS option contracts and indicative dataReal-time OPRA is a paid entitlement
TradierDeveloper/brokerage accessChains, expirations, quotes, Greeks in brokerage contextEntitlements and use depend on account context
Cboe delayed pagesManual web displayDelayed quote viewingAutomated extraction is explicitly prohibited
Free tiers, prices, limits, and licenses change. Treat this as a decision framework and verify current official terms before production use.

Provider comparison

ProviderEntry pointStrengthCaveat
MassiveOptions API plansReference, snapshots, market endpointsHistory and real time depend on plan
AlpacaMarket data planUS option contracts and application accessReal-time OPRA needs entitlement
TradierBroker/developer accountChains, quotes, GreeksRights depend on account context
Cboe delayed pagesManual web displayDelayed quote viewingAutomated extraction is restricted

Provider-by-provider notes: where the free tier stops

Massive: start with contract reference

Massive makes the free-versus-paid boundary visible at endpoint level. Contract discovery and selected reference operations can support symbol lookup and chain construction, while snapshots, complete quotes, deeper history, and real-time analytics vary by tier. Test the exact endpoint matrix instead of assuming the Free plan unlocks every field shown in the documentation.

Alpaca: useful inside a brokerage workflow

Alpaca is practical when the same application uses paper trading, stock data, and option contract discovery. Its free plan can support prototypes and indicative workflows, but official OPRA real-time coverage belongs to a higher entitlement. That distinction matters for spread-sensitive screens and any interface that presents current bid and ask values.

Tradier: chains in account context

Tradier exposes options-oriented endpoints in a brokerage ecosystem, which can reduce the gap between research and order workflows. Developers should confirm whether quotes are delayed or real-time for the account, which Greeks are provider-computed, and whether the intended use is personal, internal, or customer-facing.

Cboe pages are references, not a scraping API

Cboe's delayed quote interface is valuable for manual validation, but the page explicitly prohibits automated extraction. This is an important architectural lesson: public visibility is not API permission. Use it as a human reference and obtain a documented data product for automation.

A practical decision path

  1. 01

    List exact fields

    Write down contracts, quotes, trades, Greeks, history, and timestamps separately.

  2. 02

    Confirm entitlement

    Ask whether the application displays, redistributes, or only analyzes data.

  3. 03

    Test one chain

    Use a liquid symbol and inspect missing strikes, stale quotes, and crossed markets.

  4. 04

    Record provenance

    Keep vendor, feed, model inputs, and event time with every derived result.

Which option fits your workload?

Contract search tool

Reference endpoints may be enough when users only filter by underlying, expiration, strike, type, or exercise style.

Covered-call screener

Require synchronized underlying price, bid/ask, volume, open interest, IV, Greeks, and timestamps. A contract list alone cannot rank executable opportunities.

Historical volatility research

Choose point-in-time chains and quotes with adjustment history. Reconstructing history from current contracts creates survivorship and look-ahead errors.

Customer-facing options product

Confirm OPRA display, professional-user classification, derived analytics, caching, and redistribution before UI work begins.

A practical evaluation and implementation playbook

Define a canonical contract key

Normalize OCC symbols, expirations, strikes, type, and multiplier while retaining the provider's native identifier.

Reject stale chains

Record the timestamp for the underlying, quote, trade, Greeks, and open interest independently. Do not label a mixed-age response real-time.

Test corporate actions

Splits, special dividends, adjusted contracts, symbol changes, and non-standard deliverables expose weak normalization quickly.

Archive raw inputs

Store the provider payload and entitlement context before calculating screens or Greeks, so results can be reproduced.

Common mistakes that make a free API expensive

Calling contract lists an options chain

A usable chain also needs synchronized market and analytics fields.

Using last trade as fair value

Illiquid contracts can retain old trades while the current market has moved.

Comparing provider Greeks directly

Different assumptions can produce different values even from the same quote.

Scraping delayed quote pages

A visible webpage may expressly forbid automated extraction and does not grant redistribution rights.

Inspect option-data capability contracts

QVeris can expose candidate inputs and outputs before an agent calls an option-data capability. Continue with FMP option-data provider details, then confirm the calling contract in the QVeris REST API reference.

FAQ

Can I get real-time options data for free?

Sometimes in limited or brokerage-linked contexts. Complete OPRA quotes, broad streaming, commercial display, and historical tick data commonly require paid rights.

What fields should an options chain include?

At minimum: contract identity, bid/ask and sizes, last trade, volume, open interest, underlying price, IV, Greeks, and timestamps for each data family.

Are free Greeks reliable?

They can be useful for screening, but reliability depends on quote freshness and model assumptions. Record the source and avoid treating them as universal truth.

What is best for backtesting?

Point-in-time historical chains and quotes with corporate-action handling matter more than a convenient current-chain endpoint.

Provider and entitlement references