OddsJam
OddsJam's Sports Betting API offers real-time betting odds from 100+ sportsbooks including player props, alternate markets, injury data, schedules, rankings, and scores for sports betting applications.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles OddsJam the way a machine reads it — 22 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OddsJam scores 44.9/100 (thin), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OddsJam
Each block below is one kind of artifact we hold for OddsJam. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OddsJam Fixtures API
The Fixtures API from OddsJam — 11 operation(s) for fixtures.
OddsJam Futures API
The Futures API from OddsJam — 2 operation(s) for futures.
OddsJam Grader API
The Grader API from OddsJam — 3 operation(s) for grader.
OddsJam Injuries API
The Injuries API from OddsJam — 2 operation(s) for injuries.
OddsJam Leagues API
The Leagues API from OddsJam — 2 operation(s) for leagues.
OddsJam Markets API
The Markets API from OddsJam — 4 operation(s) for markets.
OddsJam Players API
The Players API from OddsJam — 1 operation(s) for players.
OddsJam Sports API
The Sports API from OddsJam — 2 operation(s) for sports.
OddsJam Sportsbooks API
The Sportsbooks API from OddsJam — 3 operation(s) for sportsbooks.
OddsJam Streaming API
The Streaming API from OddsJam — 3 operation(s) for streaming.
OddsJam Teams API
The Teams API from OddsJam — 3 operation(s) for teams.
OddsJam Tournaments API
The Tournaments API from OddsJam — 2 operation(s) for tournaments.
Scroll within the panel for all 12 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
OddsJam API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Oddsjam Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Oddsjam Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
OddsJam (OpticOdds) Streaming API
Real-time streaming surface for the OddsJam / OpticOdds Sports Betting API. Two delivery mechanisms are publicly documented: 1. Server-Sent Events (SSE) over long-lived HTTPS co...
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
OddsJam API Rules
SPECTRALSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for OddsJam — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/oddsjam · machine-readable index on apis.io