# How to connect The Odds API to OpenClaw (paste one key, 8 tools) > Connect The Odds API to OpenClaw with ClawLink: paste your The Odds API key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/the-odds-api The usual route to The Odds API access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical The Odds API setup: install one ClawHub skill, connect The Odds API in the browser, and OpenClaw can call real The Odds API actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to The Odds API. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect The Odds API** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect the-odds-api # connect The Odds API (browser OAuth) npx -y @useclawlink/cli actions the-odds-api # list available actions npx -y @useclawlink/cli run the-odds-api --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect The Odds API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your The Odds API API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from The Odds API, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once The Odds API is connected in the dashboard, that agent calls the same 8 The Odds API tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## The Odds API MCP for OpenClaw Looking for a The Odds API MCP server for OpenClaw? ClawLink connects The Odds API to OpenClaw and exposes 8 The Odds API tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes The Odds API integration](https://claw-link.dev/hermes/the-odds-api) works the same way. ## What the OpenClaw The Odds API integration can do 8 The Odds API tools are ready for OpenClaw once the account is connected. ### All 8 The Odds API tools for OpenClaw | Tool | What it does | |---|---| | **Get event markets** `the_odds_api_get_event_markets` | Retrieve available market keys for each bookmaker for a specific event | | **Get event odds** `the_odds_api_get_event_odds` | Retrieve odds for a specific event | | **Get events** `the_odds_api_get_events` | Fetch live and upcoming events for a specified sport | | **Get odds** `the_odds_api_get_odds` | Fetch live and upcoming event odds for a specified sport, including bookmakers, regions, and | | **Get participants** `the_odds_api_get_participants` | Fetch list of participants (teams or players) for a specified sport | | **Get scores** `the_odds_api_get_scores` | Return live and recently completed event scores for a sport | | **Get sports** `the_odds_api_get_sports` | Retrieve a list of in-season sports | | **Get v3 odds** `the_odds_api_get_v3_odds` | Fetch odds using the legacy V3 API endpoint | ## Example prompts **Get Event Markets** > Pull the relevant data from The Odds API, summarize it in plain English, and point out anything that needs attention. **Get Event Odds** > Pull the relevant data from The Odds API, summarize it in plain English, and point out anything that needs attention. **Get Events** > Pull the relevant data from The Odds API, summarize it in plain English, and point out anything that needs attention. **Get Odds** > Pull the relevant data from The Odds API, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want The Odds API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the The Odds API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected The Odds API account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for The Odds API. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right The Odds API actions to the runtime in a format your agent can reliably use. | 8 tools for The Odds API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes The Odds API to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect The Odds API in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the The Odds API key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the The Odds API skill but can't call the tools The ClawHub skill teaches OpenClaw about The Odds API, but the calls run through the ClawLink plugin and your connected account. Make sure The Odds API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect The Odds API from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling The Odds API tools The Odds API tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every The Odds API call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### The Odds API returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for The Odds API has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw The Odds API integration? Yes. ClawLink is the fastest way to connect OpenClaw to The Odds API: link your The Odds API account once in the browser and OpenClaw can call the The Odds API API through 8 ready-made tools — no custom code or token handling. ### How do I add The Odds API to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink The Odds API skill from ClawHub, then you click Connect in the dashboard to authorize The Odds API. OpenClaw calls the tools from the next message — no config files, and the The Odds API key you paste is stored server-side instead of in your environment. ### How long does it take to connect The Odds API to OpenClaw? About two minutes. Sign in, click Connect next to The Odds API in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring The Odds API up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want The Odds API working from chat. ### OpenClaw installed the The Odds API skill but can't call the tools The ClawHub skill teaches OpenClaw about The Odds API, but the calls run through the ClawLink plugin and your connected account. Make sure The Odds API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.