Skip to main content

Overview

We provide AI-ready resources to help you build faster with AI coding assistants. Whether you’re using ChatGPT, Claude, Cursor, VS Code Copilot, or other AI tools, we have resources that give these tools the context they need to generate accurate, production-ready code.

Machine-Readable Documentation

We provide documentation in formats optimized for AI coding tools:

Documentation Index

A lightweight file listing all documentation pages with URLs and descriptions. AI tools can scan this to find relevant pages to fetch. URL: https://docs.odds-api.io/llms.txt Size: ~500 tokens

Complete Documentation

The entire API documentation compiled into a single text file. Best for AI tools with large context windows that can ingest everything at once. URL: https://docs.odds-api.io/llms-full.txt Size: ~2.5k tokens

OpenAPI Specification

Machine-readable API definition following the OpenAPI 3.0 standard. Contains all endpoints, parameters, request/response schemas, and examples. URL: https://docs.odds-api.io/api-reference/openapi.json Size: ~22k tokens

MCP Server

For AI tools that support the Model Context Protocol, our MCP server provides direct API access. See setup instructions below.

Quick Start: Copy-Paste Context

Copy this context block and paste it into your AI tool for instant API knowledge:
You are helping me build with the Odds-API.io sports betting odds API.

API Base URL: https://api.odds-api.io/v3
Authentication: API key as query parameter (?apiKey=YOUR_KEY)

Key endpoints:
- GET /sports - List sports (no auth)
- GET /bookmakers - List bookmakers (no auth)
- GET /events?sport={slug}&apiKey={key} - Get events
- GET /odds?eventId={id}&bookmakers={list}&apiKey={key} - Get odds
- GET /odds/multi?eventIds={ids}&bookmakers={list}&apiKey={key} - Batch odds (up to 10 events)
- GET /value-bets?bookmaker={name}&apiKey={key} - Value betting opportunities
- GET /arbitrage-bets?bookmakers={list}&apiKey={key} - Arbitrage opportunities

For complete documentation, fetch: https://docs.odds-api.io/llms-full.txt
For OpenAPI spec: https://docs.odds-api.io/api-reference/openapi.json

Setup by Tool

Claude (chat.anthropic.com)

  1. Start a new conversation
  2. Paste the context block above, or
  3. Ask Claude to fetch the full documentation:
Please fetch and read https://docs.odds-api.io/llms-full.txt to understand the Odds-API.io API, then help me [your task].

MCP Server

The Model Context Protocol (MCP) server provides direct API integration for AI tools, allowing them to fetch live data from your Odds-API.io account.

Features

  • 12 API tools - Get sports, bookmakers, events, odds, value bets, and arbitrage opportunities
  • Documentation resources - Access full docs and OpenAPI spec directly
  • Real-time data - Fetch live odds and events

Setup

claude mcp add odds-api --env ODDS_API_KEY="your-api-key" -- npx -y odds-api-mcp-server

Available Tools

ToolDescription
get_sportsList all available sports
get_bookmakersList all available bookmakers
get_leaguesGet leagues for a sport
get_eventsGet events with filtering options
get_live_eventsGet currently live events
search_eventsSearch events by text
get_oddsGet odds for an event
get_multi_oddsGet odds for multiple events
get_value_betsGet value betting opportunities
get_arbitrage_betsGet arbitrage opportunities
get_participantsGet teams/participants
get_documentationGet API documentation

Example Prompts

Here are some example prompts to get you started:

Building an Odds Comparison App

Using the Odds-API.io API, help me build a React component that:
1. Fetches upcoming Premier League matches
2. Gets odds from Bet365, SingBet, and Unibet
3. Displays a comparison table showing the best odds for each outcome

Creating a Value Bet Finder

Help me build a Python script that:
1. Fetches value bets from the Odds-API.io /value-bets endpoint
2. Filters for bets with > 5% expected value
3. Sends alerts to a Discord webhook when new value bets are found

Real-Time Odds Tracker

Create a Node.js service that:
1. Connects to the Odds-API.io WebSocket
2. Tracks odds movements for specific events
3. Stores historical data in a database
4. Exposes an API endpoint for querying odds history

Resources