canonical: https://jentic.com/apis/betslipdoctor.ai/betslipdoctor # BetSlip Doctor Agent API The BetSlip Doctor Agent API reads, grades, and tracks sports betslips for their owner. It stores and revises tracked slips, runs durable grade jobs on confirmed tickets, and returns the owner's betting-history summary, saved reports, and library. It also reads the current main-market odds board and compares posted prices across the legs of a slip. No endpoint places wagers or accesses sportsbook credentials. ## For AI agents Read, track, and grade owner-scoped sports betslips, read betting history and reports, and compare posted odds. Returns JSON over an OAuth-secured REST API and never places a wager. ## Scope Does not place wagers, access sportsbook accounts, or move funds. Use for reading, grading, and tracking owner-scoped betslips and odds only. ## Capabilities - Read and track betslips scoped to their owner - Grade a confirmed ticket with a durable grading job - Read the owner's imported betting-history summary - Read saved grade jobs, their progress, and reports - Read the main-market odds board and compare posted prices for slip legs ## Use cases ### AI Agent Betting Analysis via Jentic An agent that helps a bettor analyse slips can call BetSlip Doctor through Jentic without running the OAuth flow or refreshing tokens. The agent searches by intent, authorizes once, and reads, tracks, or grades slips as structured data. Because no endpoint places a wager, the agent analyses and reports rather than acting on a sportsbook. Example prompt: Search Jentic for 'grade a betslip', authorize with OAuth, and start a grade job for a confirmed ticket ### Betslip Tracking and Grading Track a slip and grade it once the ticket is confirmed. BetSlip Doctor creates or revises a tracked slip and runs a durable grade job whose progress and report an agent can read, so a bettor's assistant keeps a record of each slip and its graded outcome. Example prompt: Call POST `/api/v1/slips` to track a slip, then POST `/api/v1/grade` to start grading a confirmed ticket ### Odds and Price Comparison Read the current main-market board and compare the posted prices for the legs of a slip. BetSlip Doctor returns the board and a price-shop result, so an agent can show where each leg prices best before the bettor decides, without the API ever placing the bet. Example prompt: Call POST `/api/v1/price-shop` to compare posted prices for a slip's legs ### Betting History and Reports Pull the owner's betting-history summary and the saved grade reports and library. BetSlip Doctor returns a history summary and the reports endpoint lists durable grade jobs and their results, so an agent can summarise performance over time. Example prompt: Call GET `/api/v1/history` to read the owner's betting-history summary ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/slips` | Read tracked slips | | POST | `/api/v1/slips` | Create or revise a tracked slip | | POST | `/api/v1/grade` | Start a durable grade job for a ticket | | GET | `/api/v1/history` | Read the owner's betting-history summary | | GET | `/api/v1/reports` | Read grade jobs, reports, and library | | GET | `/api/v1/board` | Read the current main-market board | | POST | `/api/v1/price-shop` | Compare posted prices for slip legs | ## Key resources - **Slips** — Read, create, and revise owner-scoped tracked slips - **Grade** — Durable grading jobs for confirmed tickets - **Reports** — Grade jobs, progress, reports, and the saved library - **History** — The owner's imported betting-history summary - **Odds** — Main-market board and posted-price comparison for slip legs ## 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:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 41 / 100 - Agent Usability: 94 / 100 - Security: 90 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/betslipdoctor.ai/betslipdoctor/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 the BetSlip Doctor API by hand means running the OAuth 2.1 authorization-code flow with PKCE, requesting the right read, track, and grade scopes, and refreshing the short-lived access tokens yourself. Through Jentic you install once, import BetSlip Doctor from the API Directory, store the OAuth credential once, and your agent calls it. - **Permission scoping:** BetSlip Doctor gates each operation behind an OAuth scope (slips read, track, grade, history, reports, and odds), so a rule can grant your agent only the scopes and operations you choose. Because no endpoint places a wager, the strongest action you can allow is grading or revising a tracked slip. - **Credential handling:** Your BetSlip Doctor OAuth credential 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 'grade a betslip' or 'compare odds', and Jentic returns the matching BetSlip Doctor operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ParlayAPI** — Alternative parlay and betting analytics - **The Odds API** — Live sports odds across many bookmakers - **BetsAPI** — Sports results and betting market data ## FAQ ### Is there a BetSlip Doctor MCP server? You don't need a separate MCP server to give your agent the BetSlip Doctor API. Jentic connects it directly from the API Directory: import it, authorize once with OAuth, and your agent calls the slip, grade, and odds operations it needs. ### Can I limit what my agent is allowed to do with the BetSlip Doctor API? Yes. Every operation is gated by an OAuth scope, so you grant your agent just the scopes it needs, such as reading slips and odds, and it can read and compare while grading or tracking stays out unless you add those scopes. Every call is logged by your self-hosted instance. ### What authentication does the BetSlip Doctor API use? The BetSlip Doctor API uses OAuth 2.1 authorization code with PKCE and per-operation scopes, per its OpenAPI spec, and access tokens are short-lived. Through Jentic the OAuth credential is stored encrypted by your own Jentic One instance and injected at call time. ### Can I grade a betslip with the BetSlip Doctor API? Yes. You track a slip, then start a durable grade job for a confirmed ticket and read its progress and report. No endpoint places a wager or touches sportsbook credentials. ### What are the rate limits for the BetSlip Doctor API? The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://betslipdoctor.ai for current limits. ### How do I grade a betslip with the BetSlip Doctor API through Jentic? Search Jentic for 'grade a betslip' and it returns the BetSlip Doctor grade operation with its input schema; authorize once with OAuth and the agent starts a grade job for a confirmed ticket. To run it on your own infrastructure, install Jentic One from its GitHub repo.