Install Jentic One Beta

Connect the HaterPicks API (HaterAPI) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HaterPicks API (HaterAPI), 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%2Fhaterpicks.app%2Fhaterpicks" | 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%2Fhaterpicks.app%2Fhaterpicks" | 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 HaterPicks API (HaterAPI) API.

List live odds merged and de-duplicated across Australian bookmakers

Pull player-prop markets for a single sport

List positive-expected-value player-prop opportunities

List cross-bookmaker arbitrage opportunities

Price a same-game multi across bookmakers

GET STARTED

Start building with HaterPicks API (HaterAPI) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HaterPicks API (HaterAPI) API for, with concrete tasks.

★ Odds Aggregation Feed

An agent pulls one clean view of Australian sports odds instead of scraping each bookmaker. It lists odds for the game lines it cares about, head-to-head, totals, and spreads, already merged and de-duplicated across bookmakers. This gives a betting tool a single source for current prices without maintaining a scraper per site.

Call the odds operation and return the head-to-head prices for a given match across bookmakers

Value and Arbitrage Scanning

An agent scans for edges across bookmakers. On the plans that expose them, it lists positive-expected-value player-prop opportunities and cross-bookmaker arbitrage, then surfaces the ones above a chosen edge to an operator. Because EV and arbitrage are separate operations, the agent runs whichever the current plan supports.

List positive-EV opportunities and return those whose edge is above a given percentage

Same-Game Multi Pricing

An agent prices a same-game multi before a user commits to it. It sends the legs to the same-game-multi quote operation and reads back a merged price across bookmakers. This lets a tool show a combined price for a multi without the user pricing each leg by hand.

Send a set of same-game-multi legs to the quote operation and return the combined price

Key Endpoints

7 endpoints — the haterpicks api returns live australian sports-betting odds, merged and de-duplicated across australian bookmakers.

METHOD

PATH

DESCRIPTION

GET

/api/v1/odds

List live odds across Australian bookmakers

GET

/api/v1/ev

List positive-EV player-prop opportunities

GET

/api/v1/props

List player-prop markets for one sport

GET

/api/v1/arbs

List cross-bookmaker arbitrage opportunities

POST

/api/v1/sgm-quote

Price a same-game multi across bookmakers

GET

/api/v1/odds

List live odds across Australian bookmakers

GET

/api/v1/ev

List positive-EV player-prop opportunities

GET

/api/v1/props

List player-prop markets for one sport

GET

/api/v1/arbs

List cross-bookmaker arbitrage opportunities

POST

/api/v1/sgm-quote

Price a same-game multi across bookmakers

Why Jentic?

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

Setup

Wiring HaterPicks by hand means choosing between a bearer token and an x-api-key header, knowing which endpoints are open, and handling markets gated by plan. Through Jentic you install once, import HaterPicks from the API Directory, store the credential once, and your agent calls it.

Permission scoping

HaterPicks takes its parameters in the request rather than a resource id in the URL, so a rule bounds which operations your agent may call, not which market it reads. You choose the read operations it may use, such as listing odds and props, so the same-game-multi quote operation stays off until you add it.

Credential isolation

Your HaterPicks 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 'list live sports odds' or 'find arbitrage opportunities', and Jentic returns the matching HaterPicks operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using HaterPicks API (HaterAPI) API through Jentic.

What authentication does the HaterPicks API use?

Per its OpenAPI spec, the HaterPicks API accepts either a bearer token in the Authorization header or an x-api-key header, while the describe and waitlist endpoints are open. Through Jentic the credential is stored by your own self-hosted instance and injected when the agent calls a data operation, so it never appears in the agent's prompt or logs.

Can I get merged Australian bookmaker odds with the HaterPicks API?

Yes. The odds operation returns live game lines, such as head-to-head, totals, and spreads, already merged and de-duplicated across Australian bookmakers, so an agent reads one clean set of prices rather than scraping each site. Higher plans add player props, positive-EV opportunities, arbitrage, and same-game-multi pricing.

What are the rate limits for the HaterPicks API?

The OpenAPI spec does not state a numeric rate limit, and some operations are gated by plan rather than by request volume. Add backoff around 429 responses, and check the HaterPicks documentation at https://www.haterpicks.app for current limits and plan tiers.

Can I limit what my agent is allowed to do with the HaterPicks API?

Yes. HaterPicks takes its query parameters in the request, not a resource id in the URL path, so a rule bounds which operations your agent may call rather than which market it reads. You choose that it may list odds and player props while the same-game-multi quote operation stays off until you add it, and every call it makes is logged.

Is there a HaterPicks MCP server?

You do not need an MCP server to give your agent the HaterPicks API. Jentic connects it directly from the Jentic API Directory: import HaterPicks, store your key once, and your agent calls the odds and arbitrage operations on demand without loading another server's tool definitions into its context.

How do I read live odds with the HaterPicks API through Jentic?

Search Jentic by intent such as 'list live sports odds', and Jentic returns the HaterPicks odds operation with its input schema so the agent sends the right query. To run it on your own infrastructure, install Jentic One from its GitHub repo with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add HaterPicks from the directory.

Haterpicks App HaterPicks API (HaterAPI)

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer, apiKey7 EndpointsREST

For Agents

List live Australian sports odds merged across bookmakers, pull player props, and find positive-EV and arbitrage opportunities or price a same-game multi.

Use for: List live head-to-head odds for today's matches, Find positive-EV player-prop opportunities, Get the player-prop markets for one sport, Check for cross-bookmaker arbitrage opportunities

Not supported: Does not handle placing bets, settling wagers, or managing a betting account. Use for reading Australian sports odds, value, arbitrage, and same-game-multi prices only.

The HaterPicks API returns live Australian sports-betting odds, merged and de-duplicated across Australian bookmakers. An agent lists game lines such as head-to-head, totals, and spreads, pulls player-prop markets for a sport, and on higher plans lists positive-expected-value opportunities, cross-bookmaker arbitrage, and prices a same-game multi across bookmakers. A describe operation and a bookmaker desk-feed enquiry round out the surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

100%

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

71%

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: CSignals: 4

64%

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.

53%

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: CSignals: 1

55%

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: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HaterPicks API (HaterAPI) to your agent

Capabilities

Start building with HaterPicks API (HaterAPI) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Haterpicks App HaterPicks API (HaterAPI)

Jentic AI Readiness Score

HaterPicks API (HaterAPI)

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