Resolves sport keys, lists fixtures and participants, returns bookmaker prices and market coverage for an event, and reports live scores.
8actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro lists all scheduled sports events for a specified sport. Customer service reps quickly answer when-is-the-next-game questions with current data.
Each card is one request a support team gets, and the The odds api actions Ayro runs to close it.
Ayro confirms the sport key, lists the live and upcoming events under it, and pulls the teams or players involved, so a fixture question is answered without anyone opening a schedule page.
Ayro pulls odds for a whole sport or one specific event, filtered to the region and market asked about, and reads the nested bookmaker prices back as a straight comparison.
Ayro reads the market keys each bookmaker has recently quoted on a fixture, so a question about whether a market exists gets a real answer rather than an empty odds response.
Ayro returns current and recent scores for a sport and matches them against the fixture list, so a result question is answered from the feed while the game is still running.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the The odds api actions it has and picks the ones a request needs.
Authorize the The odds api account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the The odds api actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeThe odds api · Ayro
What can you do in The odds api without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside The odds api.
No. Every action in this toolkit reads: Get Sports, Get Events, Get Participants, Get Odds, Get Event Odds, Get Event Markets, and Get Scores. Nothing stakes, settles, or writes anything back to a bookmaker, so Ayro reports prices and results rather than acting on them.
All 8 actions your agent can call on The odds api, straight from the live MCP connection.
Retrieve available market keys for each bookmaker for a specific event.
Retrieve odds for a specific event.
Fetch live and upcoming events for a specified sport.
Fetch live and upcoming event odds for a specified sport, including bookmakers, regions, and markets.
Fetch list of participants (teams or players) for a specified sport.
Return live and recently completed event scores for a sport.
Retrieve a list of in-season sports.
Fetch odds using the legacy V3 API endpoint.
Same connection, same setup. Pick the next one your team already uses.
Places visitors by IP and coordinates, scores addresses for fraud and Tor exposure, and validates form details against live lookups.
Queries an index with filters and time ranges, reads its mapping first, and confirms the cluster is reachable before it runs.
Reads submissions across every form, clones a form and labels the copy, keeps label assignments tidy, and reports usage against plan limits.
Resolves a typed address into coordinates, names the place behind a coordinate pair, and returns either as GeoJSON, XML, or JSONP.
Starts a scrape and polls it to completion, crawls a site for the same fields, converts pages to Markdown, and checks credits before a bulk run.
Submits suspicious links and files for scanning, polls reports to completion, pivots across related indicators, and records verdicts and comments.

Authorize the account and your agent has all 8 actions from the first conversation.
