For Agents
Read DraftKings Pick6 lines, DFS salaries and slates, sportsbook odds and line history, ESPN box scores, and +EV and arbitrage comparisons from an independent data service.
Use for: Get the current Pick6 lines for NBA points props, Find sportsbook prices with positive expected value against the fair line, List all DFS slates for tonight's NFL games, Retrieve the line history for one Pick6 player prop
Not supported: Does not place bets, manage DraftKings accounts, enter DFS contests, or provide official DraftKings data. Use for reading captured Pick6, DFS, sportsbook, and ESPN stats data and comparisons only.
The draftkingsapi.com API collects DraftKings Pick6 lines and line history, DFS salaries, contests, and slates, and DraftKings Sportsbook moneylines, spreads, and totals, then serves them as JSON or CSV alongside ESPN box scores and game logs. It is an independent service, not affiliated with or endorsed by DraftKings. Analysis routes compare Pick6 lines with Sportsbook lines, rank sportsbook prices that beat the Novig fair probability, and find arbitrage and middles across DraftKings, FanDuel, and Novig. Every list route paginates with a cursor, retained rows are labeled with stale and age_seconds, and only a delivered 2xx response spends credits.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the draftkings 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.
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%2Fdraftkingsapi.com%2Fdraftkingsapi" | shStep 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%2Fdraftkingsapi.com%2Fdraftkingsapi" | 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.
What an agent can do with draftkings api.
Pull current DraftKings Pick6 lines and multipliers by sport, stat, or player, and the change history for one prop
List DFS sports, contests, slates, and player salaries for a slate_id
Read sportsbook moneylines, spreads, and totals for events, with line history for a market_id
Compare Pick6 lines against DraftKings Sportsbook lines and sort by line_gap
Rank sportsbook prices that beat the Novig fair probability, filtered by min_edge and market_type
Find arbitrage and middles across DraftKings, FanDuel, and Novig on the Developer plan and above
Pull ESPN game scores and player or team game logs by sport and season
Patterns agents use draftkings api for, with concrete tasks.
★ AI research agent for player props
A betting research agent asked about a player prop needs current lines and recent form side by side. Through Jentic the agent searches for 'compare Pick6 lines to sportsbook lines', loads the getCompare operation, and reads both lines with no-vig probabilities, then pulls ESPN player game logs for the same athlete. The bearer key is injected by Jentic at call time, and the agent answers with sourced numbers rather than guesses.
Call GET /api/v1/compare with sport 'NBA', stat 'Points', and min_gap 1.5, then fetch GET /api/v1/stats/player-games for each player's athlete_id in the current season and summarise the last five games
Expected-value and arbitrage screening
Bettors who price against an exchange want a ranked list of prices that pay more than the fair probability. GET /api/v1/ev compares DraftKings, FanDuel, and other sportsbook prices to the Novig fair probability, with ev_pct, Kelly sizing, and a confidence flag, filterable by market_type such as moneyline, spread, total, or player_prop. GET /api/v1/arbitrage returns two-leg arbitrage and middles, and on the Free plan answers 402 with an upgrade prompt.
Call GET /api/v1/ev with market_type 'player_prop', min_edge 2, and sort 'ev', then call GET /api/v1/arbitrage with type 'middles' and list the top five opportunities
DFS lineup preparation
Daily fantasy players build lineups around a slate's salaries and contests. The API lists DFS sports, contests, slates, and player salaries filterable by slate_id, team, and search, and GET /api/v1/dfs/changes returns lobby changes since a cursor so a lineup tool can pick up late salary or contest updates without refetching everything.
Call GET /api/v1/dfs/slates with sport 'NFL', pick the main slate_id, fetch GET /api/v1/dfs/players for that slate as CSV, and poll GET /api/v1/dfs/changes for updates
Line movement tracking
Line movement tells a modeller where money or news has hit a market. GET /api/v1/pick6/line-history returns the history of one Pick6 prop by pickable_id, GET /api/v1/sportsbook/line-history returns the history of one sportsbook player market by market_id, and GET /api/v1/history covers moneyline, spread, and total changes for events, each row labeled with capture time.
Call GET /api/v1/pick6/line-history with a pickable_id and stat 'Points' and chart each line and multiplier change over time
62 endpoints — the draftkingsapi.
METHOD
PATH
DESCRIPTION
/api/v1/pick6/projections
Current Pick6 lines and multipliers
/api/v1/dfs/players
DFS salaries by player
/api/v1/odds
Moneylines, spreads, and totals
/api/v1/compare
Pick6 lines vs Sportsbook lines
/api/v1/ev
+EV prices against Novig fair probability
/api/v1/arbitrage
Arbitrage and middles across books
/api/v1/stats/player-games
ESPN player game logs
/api/v1/credit-costs
Credit cost per endpoint
/api/v1/pick6/projections
Current Pick6 lines and multipliers
/api/v1/dfs/players
DFS salaries by player
/api/v1/odds
Moneylines, spreads, and totals
/api/v1/compare
Pick6 lines vs Sportsbook lines
/api/v1/ev
+EV prices against Novig fair probability
/api/v1/arbitrage
Arbitrage and middles across books
/api/v1/stats/player-games
ESPN player game logs
/api/v1/credit-costs
Credit cost per endpoint
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the draftkingsapi.com API by hand means handling a bearer key for data routes, a separate dashboard session cookie for webhooks, cursor pagination on every list, and credit accounting per started 100 rows. Through Jentic you install once, import it from the API Directory, store the bearer key once, and your agent calls it.
Permission scoping
The draftkingsapi.com API carries sport, slate, player, and market filters in query parameters, not the path, so rules bound which operations your agent may call, not which markets it reads. You choose the operations it may call, so account-changing ones like POST /api/v1/billing/cancel or POST /api/v1/onboarding are not included unless you add them.
Credential isolation
Your draftkingsapi.com API bearer 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 'get Pick6 lines' or 'find arbitrage bets', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using draftkings api through Jentic.
What authentication does the draftkingsapi.com API use?
The OpenAPI spec declares two schemes. The data routes use bearerAuth, an HTTP bearer key in the Authorization header. Webhook management under /api/account/webhooks uses sessionCookie, the __Secure-neon-auth.session_token cookie from the signed-in dashboard, and the spec notes bearer keys do not authenticate hook management. Several routes are keyless, including /api/v1/public/board, the /api/v1/demo samples, GET /api/v1/credit-costs, and the agent signup flow.
Is the draftkingsapi.com API affiliated with DraftKings?
No. The spec states it is independent and not affiliated with or endorsed by DraftKings. It captures Pick6, DFS, and Sportsbook data and labels each row with a capture time, and notes that the source's own update time is unknown for Pick6 rows.
What are the rate limits for the draftkingsapi.com API?
Per the spec's description, the monthly plans are Free at 100 credits per month and 20 requests per minute, Developer at 10,000 credits per month and 60 requests per minute, and Production at 50,000 credits per month and 120 requests per minute, with limits shared across an account's keys. Each page costs its endpoint's credits per started 100 rows, which GET /api/v1/credit-costs lists, and invalid queries and 304 responses cost nothing.
Is there a DraftKings data MCP server?
You don't need an MCP server to give your agent the draftkingsapi.com API. Jentic connects it directly from the API Directory: import it, store your bearer key once, and your agent calls the Pick6, DFS, or odds operations it needs, discovered on demand instead of preloaded into its context.
Can I limit what my agent is allowed to do with the draftkingsapi.com API?
Yes. For example, write a rule that allows only GET /api/v1/pick6/projections, GET /api/v1/compare, and GET /api/v1/stats/player-games, so the agent can research props but cannot cancel billing through POST /api/v1/billing/cancel or submit onboarding changes. Every call it makes is logged.
How do I find +EV prices through Jentic?
Add the draftkingsapi.com API to your Jentic One instance from the directory and store your bearer key. Your agent searches for 'find positive expected value bets', loads the getEv operation, and calls GET /api/v1/ev with filters such as market_type, min_edge, and sort. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I try the draftkingsapi.com API without a key?
Yes. The /api/v1/demo routes return keyless samples for Pick6, DFS, events, odds, history, and stats, and /api/v1/public/board, /api/v1/public/sportsbook, and /api/v1/public/line-moves return keyless boards by league. An agent can start a signup with POST /api/v1/agent/signup and collect the key with POST /api/v1/agent/token once a person approves.
GET STARTED