canonical: https://jentic.com/apis/parlay-api.com/parlay-api # ParlayAPI private research reads The ParlayAPI private research reads API returns sports coverage and available bookmaker odds for private research against your own ParlayAPI account. It lists the sports and competitions your account covers and retrieves current odds for a sport, filtered by region, market, bookmaker, event, and a commence-time window. Responses are read-only and carry no data redistribution rights, so the API suits analysis rather than resale. ## For AI agents List the sports a ParlayAPI account covers and read current bookmaker odds for a sport, filtered by region, market, bookmaker, and commence time. Authenticates with an API key or bearer token. ## Scope Does not place bets, settle wagers, or grant data redistribution rights. Use for reading sports and bookmaker odds data only. ## Capabilities - List the sports and competitions a ParlayAPI account covers - Retrieve available bookmaker odds for a sport across selected regions and markets - Filter odds by bookmaker, event, and commence-time window ## Use cases ### AI Agent Odds Lookup An AI agent doing sports research can pull the available odds for a sport through Jentic. The agent searches for the odds operation, passes the sport key and the regions and markets it wants, and receives the current bookmaker prices, without the developer wiring the API key or bearer token or reading the ParlayAPI reference docs. Example prompt: Call GET `/v1/sports/{sport_key}/odds` with regions and markets set to read current odds for a sport ### Sports Coverage Discovery Research tools first need to know which sports and competitions have data. The sports operation lists every sport key available on your account, which the odds operation then uses to pull prices, so an agent can enumerate coverage before requesting odds. Example prompt: Call GET `/v1/sports` to list the available sport keys, then request odds for one of them ### Odds Monitoring Analysts track how bookmaker prices move for upcoming events. The odds operation accepts a commence-time window and a bookmaker filter, so an agent can poll a sport on a schedule and record the odds for events starting in the next window for later comparison. Example prompt: Call GET `/v1/sports/{sport_key}/odds` with a commence-time window to read odds for upcoming events ## Key resources - **Sports** — The list of sports and competitions covered by your account - **Odds** — Available bookmaker odds for a sport, filtered by region, market, bookmaker, event, and commence time ## AI readiness 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. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 40 / 100 - Agent Usability: 94 / 100 - Security: 42 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/parlay-api.com/parlay-api/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring ParlayAPI by hand means sending your API key or bearer token, encoding the region, market, and bookmaker filters correctly, and respecting your account's data terms. Through Jentic you install once, import ParlayAPI from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** This API is read-only with two operations, so a rule can bound your agent to exactly the sports-list and odds reads it needs. You choose that set, so the agent retrieves research data but cannot reach anything else. - **Credential handling:** Your ParlayAPI key or token 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. - **Discovery method:** Agents search Jentic by intent such as 'get odds for a sport' or 'list available sports', and Jentic returns the matching ParlayAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **The Odds API** — Sports odds across many bookmakers and markets - **SportsData.io** — Sports statistics, scores, and odds feeds - **WHAPI Sports Data** — Sports fixtures and results data ## FAQ ### What authentication does the ParlayAPI private research reads API use? This API authenticates the odds operation with an API key, sent either as the `X-API-Key` header or the `apiKey` query parameter, or with a bearer token, per its OpenAPI spec. The sports list operation needs no credential. Through Jentic the key or token is stored encrypted by your own Jentic One instance and injected at call time. ### Can I read bookmaker odds with the ParlayAPI private research reads API? Yes. The odds operation returns current odds for a sport and accepts filters for region, market, bookmaker, event, and a commence-time window. Call the sports operation first to find the sport key you want prices for. ### What are the rate limits for the ParlayAPI private research reads API? The OpenAPI spec does not specify rate limits; your allowance depends on your ParlayAPI account. Check the vendor documentation at https://parlay-api.com for the limits that apply to your plan. ### How do I read odds with the ParlayAPI private research reads API through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import ParlayAPI from the API Directory, and store your key or token once. Your agent then searches for an intent such as 'get odds for a sport', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a ParlayAPI MCP server? You do not need an MCP server to give your agent the ParlayAPI private research reads API. Jentic connects it directly from the API Directory: import the API, store your credential once, and your agent calls the sports and odds operations on demand, which keeps your agent's context free of an extra server's tool definitions. ### Can I limit what my agent is allowed to do with the ParlayAPI private research reads API? Yes. ParlayAPI exposes only two read operations, so you can allow your agent just the ones it needs, such as listing sports and reading odds, and nothing else. Because you run Jentic One yourself, the agent reads research data but holds no other access, and every call is logged.