PropLine Player Props & Sports Betting Odds API
55
AI ReadinessFoundational (C)55/100
Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey35 EndpointsREST
For Agents
Pull player prop lines, game odds, line movement, closing lines, +EV and best-line comparisons across books, and grade placed bets on closing line value with PropLine.
Use for: Get tonight's NFL player prop lines from FanDuel and DraftKings, Find the best line for this event's player points market, Check whether my bet beat the closing line, Show me how the line moved on this game today
Not supported: Does not place bets, hold account balances, or process deposits. Use for reading odds, props, line history, and betting analytics only.
The PropLine API returns player prop lines and game odds from sportsbooks, DFS providers, prediction markets, and betting exchanges, keyed by sport and event. Beyond current odds it serves historical line movement, opening and closing lines, cross-book +EV with de-vigged fair prices, best-line lookups, and market-implied player projections. It also grades placed bets against the closing line, prices same-game parlays at a book's own correlated odds, resolves props against box-score stats, and exports resolved props and odds history in bulk. Responses follow the-odds-api format, and authenticated responses carry daily quota headers such as X-Daily-Remaining.
Install Jentic One Beta
Connect the PropLine Player Props & Sports Betting Odds API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PropLine Player Props & Sports Betting Odds API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprop-line.com%2Fprop-line" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprop-line.com%2Fprop-line" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PropLine Player Props & Sports Betting Odds API.
List current odds for a sport or a single event, filtered by markets, bookmakers, and period such as q1 or h1
Find the best available line for an event's markets across bookmakers
Compute cross-book +EV for an event using de-vigged fair prices, or calculate EV for a price you supply
Read historical odds, line movement and steam, and opening and closing lines for an event
Grade placed bets against the closing line and return clv_pct and ev_vs_close_pct
Price a same-game parlay at a bookmaker's own correlated odds from a list of legs
Search players and read their prop history, trends, and game logs by market
Use Cases
Patterns agents use PropLine Player Props & Sports Betting Odds API for, with concrete tasks.
★ Agent-Driven Line Shopping
An AI agent connected through Jentic takes a bet a user is considering, pulls the best available line for that event's market across bookmakers, and computes +EV against the de-vigged fair price. It reports which book pays the most and whether the price has positive expected value, so the user sees the comparison without opening several sportsbook apps.
For event abc123 in americanfootball_nfl, get the best line on the player_pass_yds market and the event EV with devig, and report the top-paying bookmaker
Closing Line Value Tracking
A bettor wants an honest read on whether they have an edge. They post the bets they placed to the CLV grading operation, which returns each bet's closing line, the de-vigged closing fair probability, clv_pct, ev_vs_close_pct, and the graded result once the game settles. The operation is stateless, so nothing about the bets is stored by PropLine.
Grade three placed NFL bets against the closing line with devig and summarize the average ev_vs_close_pct
Prop Model Backtesting
A modeler backtests a player prop model by exporting resolved props and odds history for a sport and date range, then comparing predictions to outcomes. Market hit rates, a resolution summary, and a sportsbook accuracy report give baseline numbers to beat, and the coverage history operation shows when each book's odds history starts.
Export resolved props for sport baseball_mlb with since 2026-10-01 and read the sportsbook accuracy report for the same sport
Same-Game Parlay Pricing
Correlated parlay legs are priced differently by every book. The PropLine API prices a same-game parlay at a bookmaker's own correlated odds from a list of legs, or quotes every supported book at once with bookmaker set to all and names the best_bookmaker, so a user can see who charges the smallest correlation tax.
Price a same-game parlay for event abc123 in americanfootball_nfl with two legs and bookmaker all, and report the best_bookmaker
Key Endpoints
35 endpoints — the propline api returns player prop lines and game odds from sportsbooks, dfs providers, prediction markets, and betting exchanges, keyed by sport and event.
METHOD
PATH
DESCRIPTION
GET
/v1/sports
List sports
GET
/v1/sports/{sport_key}/odds
List odds for a sport
GET
/v1/sports/{sport_key}/events/{event_id}/odds
Get odds for one event
GET
/v1/sports/{sport_key}/events/{event_id}/best-line
Get the best line across books
GET
/v1/sports/{sport_key}/events/{event_id}/ev
Get cross-book +EV for an event
GET
/v1/sports/{sport_key}/events/{event_id}/odds/closing
Get opening and closing lines
POST
/v1/clv/grade
Grade placed bets against the closing line
POST
/v1/sports/{sport_key}/events/{event_id}/sgp
Price a same-game parlay
GET
/v1/sports
List sports
GET
/v1/sports/{sport_key}/odds
List odds for a sport
GET
/v1/sports/{sport_key}/events/{event_id}/odds
Get odds for one event
GET
/v1/sports/{sport_key}/events/{event_id}/best-line
Get the best line across books
GET
/v1/sports/{sport_key}/events/{event_id}/ev
Get cross-book +EV for an event
GET
/v1/sports/{sport_key}/events/{event_id}/odds/closing
Get opening and closing lines
POST
/v1/clv/grade
Grade placed bets against the closing line
POST
/v1/sports/{sport_key}/events/{event_id}/sgp
Price a same-game parlay
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PropLine — Player Props & Sports Betting Odds API
- Foundational (C)55/100
68
Foundational Compliance63
Developer Experience & Jentic Compatibility41
AI-Readiness & Agent Experience94
Agent Usability33
Security83
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
68
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
46%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
41
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
33%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
80%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
33
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
33%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
83
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
83%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PropLine by hand means choosing between the `X-API-Key` header and the apiKey query parameter, reading the X-Daily-Remaining quota headers, and honoring Retry-After on 429 responses. Through Jentic you install once, import PropLine from the API Directory, store the key once, and your agent calls it.
Permission scoping
PropLine puts the sport key and event id in the URL path (/v1/sports/{sport_key}/events/{event_id}/...), so a rule can pin your agent to one sport, or one event, and the operations you pick. You choose the operations it may call, so quota-heavy bulk exports are not included unless you add them.
Credential isolation
Your PropLine API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find the best line for a game' or 'grade my bets on closing line value', and Jentic returns the matching PropLine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PropLine Player Props & Sports Betting Odds API through Jentic.
What authentication does the PropLine API use?
The PropLine API authenticates with an API key, which its OpenAPI spec lets you send either in the `X-API-Key` header (scheme APIKeyHeader) or as the apiKey query parameter (scheme APIKeyQuery). Two operations, the export sample and the per-book data freshness report, need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, never entering the agent's context.
What are the rate limits for the PropLine API?
The OpenAPI spec does not state a fixed numeric limit, but it documents that authenticated responses carry daily quota headers (X-Daily-Limit, X-Daily-Used, X-Daily-Remaining, X-Daily-Reset) plus standard RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers, and that 429 responses include Retry-After. Check https://prop-line.com for the quota on your plan.
Can I check closing line value on my bets with the PropLine API?
Yes. Post the bets you placed to the CLV grading operation and each comes back with its closing line, the de-vigged closing fair probability, clv_pct, ev_vs_close_pct, and the graded result once the game settles. The operation is stateless, so the bets are not stored.
Is there a PropLine MCP server?
You don't need an MCP server to give your agent PropLine. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so the odds, EV, and player history surface is reachable without loading every tool definition into the agent's context.
Can I limit what my agent is allowed to do with the PropLine API?
Yes. For example, write a rule that allows only the event odds and best-line operations under /v1/sports/americanfootball_nfl, so the agent can compare NFL prices and nothing else, with bulk exports and CLV grading left out. Every call it makes is logged.
How do I find the best line for an event with the PropLine API through Jentic?
Import the PropLine API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'find the best line for a game'. Jentic returns the best-line operation for an event with its input schema, including the sport_key and event_id path parameters and the markets and bookmakers filters. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is the PropLine API compatible with the-odds-api?
Its OpenAPI spec states that responses are the-odds-api compatible for drop-in migration, so code that reads sports, events, and odds in that format can switch with minimal changes. PropLine adds operations beyond that shape, such as CLV grading, same-game parlay pricing, and player prop history.
GET STARTED