Sports odds and player props.
One API key.

GetOdds is being built as one access layer for independent sports-data APIs: PrizePicks API, Underdog API, DraftKings API and FanDuel API. The intended experience is one account, one key and a consistent format. This page previews that unified platform; the existing source services operate separately today.

The current product scope covers PrizePicks, Underdog, DraftKings, DraftKings Pick6 and FanDuel. Availability differs by source, sport and market. Prediction markets are not included in this launch scope.

Yes. The existing PrizePicks API service exposes player projections and related records. The explorer on this page contains real records captured from its public sample endpoint. Visit prizepicksapi.com for current access, documentation and coverage.

The unified connection is intended to expose Underdog player-market data through the same access layer. It must retain source-specific line variants and rules. The Underdog source is not connected to the explorer on this prototype; it is not being represented as a live feed here.

No. Sportsbook markets and Pick6 player selections have different pricing and settlement structures. They may share player and event identities, but a normalized record must preserve the source product, market type, selection and original rules.

That is a core use case for the unified platform. A valid comparison needs the same event, market, period, selection and settlement conditions, with source observation times visible. The cross-source comparison on this page is illustrative, not a live odds comparison service.

It is a common structure for fields such as source, player, event, market, period, line and observation time. It reduces integration work while preserving details that differ between sources. A common schema does not make every market directly equivalent.

Coverage is source-specific. The captured PrizePicks API snapshot includes league counts and sample records for NBA, NFL and NHL. Those figures describe that source at capture time, not guaranteed unified coverage. A published source-by-source coverage table is required before the unified service launches.

No. The detailed explorer uses a captured PrizePicks API snapshot from 6 November 2026 and shows original observation times. Other example lines are labeled illustrative. Use the linked source service to inspect its current data.

Freshness depends on the source and market. The intended response format includes observation timestamps so callers can assess record age. This prototype does not establish an update-frequency guarantee or latency SLA for the unified service.

The schema is intended to distinguish market periods and event state, but pregame and in-play availability must be verified per source. Do not infer in-play coverage from a player prop appearing in a sample response.

Recorded line history is part of the intended platform. The existing PrizePicks API source already supplies recorded changes, examples of which appear in the explorer. Unified retention, historical start dates and source coverage have not been established by this prototype.

Outcomes are part of the intended data model, but grading requires source-specific settlement rules, result provenance and handling of voids or corrections. This page does not demonstrate a unified grading endpoint or promise outcome coverage for every source.

The existing source APIs can be called over HTTP from Python, JavaScript or other languages. The unified API is planned to use the same straightforward request-and-response model. The response preview here is a schema concept; it is not a production endpoint.

A shared MCP connection is planned so compatible AI agents can discover and call the same data tools. The agent illustration shows that intended workflow. It does not mean an operational GetOdds MCP server is available from this prototype.

Existing keys continue to belong to the services that issued them. A GetOdds key migration has not been implemented here. Existing customers should follow their source service’s current authentication documentation until a verified migration path is published.

The intended model is one credit balance across sources. Unified prices, included usage and the cost of individual operations have not been published in this prototype. Existing services keep their current plans and billing; no shared subscription is created here.

The unified API needs documented pagination, request limits and retry behavior before production use. No GetOdds limits are established by the sample page. For an existing source integration, use that source’s current pagination and rate-limit documentation.

The explorer lets you inspect and copy an individual captured record as JSON. Broader export formats and production download limits need to be verified for each source and the unified platform. Copying a sample does not create an API account or grant historical access.

GetOdds and the API services shown here are independent developer products. Platform names identify the data sources and do not imply an official partnership, endorsement or ownership by those platforms.

Use an existing source service and its current documentation while the unified platform is being developed. The PrizePicks API link on this page leads to an existing service. The GetOdds platform preview itself does not issue keys, accept payments or provision an account.