Install Jentic One Beta

Connect the BetSlip Doctor Agent API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BetSlip Doctor Agent 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%2Fbetslipdoctor.ai%2Fbetslipdoctor" | sh

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%2Fbetslipdoctor.ai%2Fbetslipdoctor" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 BetSlip Doctor Agent API.

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

GET STARTED

Start building with BetSlip Doctor Agent API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BetSlip Doctor Agent API for, with concrete tasks.

★ 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.

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.

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.

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.

Call GET /api/v1/history to read the owner's betting-history summary

Key Endpoints

7 endpoints — the betslip doctor agent api reads, grades, and tracks sports betslips for their owner.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using BetSlip Doctor Agent API through Jentic.

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.

BetSlip Doctor Agent API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationoauth27 EndpointsREST

For 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.

Use for: I want to read my tracked betslips, Track a new betslip for grading, Grade a confirmed ticket, Get my betting-history summary

Not supported: Does not place wagers, access sportsbook accounts, or move funds. Use for reading, grading, and tracking owner-scoped betslips and odds only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

54%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

15%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BetSlip Doctor Agent API to your agent

Capabilities

Start building with BetSlip Doctor Agent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BetSlip Doctor Agent API

Jentic AI Readiness Score

BetSlip Doctor Agent API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness