sportsdata-mcp

Matches across every competition your key can see, for a date range. VERIFIED live — the envelope works without a key (though a keyless call sees no competitions). Returns: {filters, resultSet:{count, first, last, played}, matches:[{id, utcDate, status, matchday, stage, competition:{id, name, code}, homeTeam:{id, name, shortName, tla, crest}, awayTeam:{…}, score:{winner, duration, fullTime:{home, away}, halfTime:{…}}}]} — envelope VERIFIED; the match object shape is from the vendor's docs. Note the score lives in score.fullTime, not on the match. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Matches in a date window {"dateFrom": "<today>", "dateTo": "<today+2>"} Auth: needs your own key in FOOTBALL_DATA_ORG_KEY.

Top scorers in a competition. NEEDS A KEY (403 without). Returns: {count, filters, competition, season, scorers:[{player:{id, name, nationality, position}, team:{id, name}, goals, assists, penalties, playedMatches}]} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Premier League top scorers {"competition": "PL", "limit": 10} Auth: needs your own key in FOOTBALL_DATA_ORG_KEY.

League table for a competition. NEEDS A KEY (403 without). Returns: {filters, competition, season, standings:[{stage, type:'TOTAL'|'HOME'|'AWAY', group, table:[{position, team:{id, name, crest}, playedGames, won, draw, lost, points, goalsFor, goalsAgainst, goalDifference, form}]}]} — SHAPE FROM VENDOR DOCS. Note `standings` is a LIST of tables (TOTAL/HOME/AWAY); pick type == 'TOTAL' for the normal ladder. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Premier League table {"competition": "PL"} Auth: needs your own key in FOOTBALL_DATA_ORG_KEY.

One club with its squad and running competitions. NEEDS A KEY (403 without). Returns: {id, name, shortName, tla, crest, address, website, founded, clubColors, venue, runningCompetitions:[…], coach:{id, name, nationality, contract}, squad:[{id, name, position, dateOfBirth, nationality}]} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: One club {"teamId": 57} Auth: needs your own key in FOOTBALL_DATA_ORG_KEY.

The clubs in a competition. NEEDS A KEY (403 without). Returns: {count, filters, competition, season, teams:[{id, name, shortName, tla, crest, address, website, founded, clubColors, venue, coach, squad:[…]}]} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Premier League clubs {"competition": "PL"} Auth: needs your own key in FOOTBALL_DATA_ORG_KEY.

One league season: every match with full/half-time score, shots, cards, and CLOSING ODDS from ~10 bookmakers. The backtesting dataset. Returns: [{Div, Date:'16/08/2024', Time, HomeTeam, AwayTeam, FTHG, FTAG, FTR:'H'|'D'|'A', HTHG, HTAG, HTR, Referee, HS, AS, HST, AST, HF, AF, HC, AC, HY, AY, HR, AR, B365H, B365D, B365A, PSH, PSD, PSA, WHH, WHD, WHA, MaxH, AvgH, B365CH…}] (one row per match; ~380 rows for a 20-team season). ALL VALUES ARE STRINGS — cast before arithmetic. Dates are DD/MM/YYYY. A `C` in an odds column means CLOSING (B365CH = Bet365 closing home). Example: Premier League 2024/25 with closing odds {"season": "2425", "division": "E0"} Auth: none needed.

Every Formula E season ('championship') with its uuid — call this first, everything else needs the id. Returns: {championships:[{id (uuid), name:'SEASON 2024-2025', status:'Past'|'Live'|'Future', lastFinishedRound, series:{id, name}}]} Example: All seasons Auth: none needed.

Drivers' championship standings for one season. Returns: [{driverPosition, driverFirstName, driverLastName, driverTLA:'ROW', driverPoints, driverTeamName, driverTeamId, driverId, driverCountry}] — a TOP-LEVEL ARRAY, not wrapped Example: Drivers' championship {"championshipId": "4e287a6d-e2da-471a-9c8a-01141d6a1819"} Auth: none needed.

One race's detail: circuit, city, date and whether results exist. Returns: {id, name, sequence, date, city, country, circuit, championship, hasRaceResults, hasSessionResults, metadata} — a single object; there is no results payload on this host (see the docs) Example: One E-Prix {"raceId": "c1dd1f8a-5112-4864-8d2d-cfcc8951d197"} Auth: none needed.

The race calendar — all seasons, or one championship's rounds. Returns: {pageInfo:{…}, races:[{id (uuid), name:'Beijing E-Prix', sequence, date, city, country, circuit, championship, hasRaceResults, hasSessionResults}]} — WRAPPED, unlike standings Example: One season's calendar {"championshipId": "4e287a6d-e2da-471a-9c8a-01141d6a1819"} Auth: none needed.

Teams' championship standings, including each team's points race by race. Returns: [{teamPosition, teamName, teamId, teamPoints, teamRaceStandings:[{raceSequence, raceCountry, racePoints}]}] — top-level array. `teamRaceStandings` is the per-race points breakdown, and the closest thing to race results this host exposes. Example: Teams' championship {"championshipId": "4e287a6d-e2da-471a-9c8a-01141d6a1819"} Auth: none needed.

Classic (total-points) league standings, paginated. Returns: {league:{id, name, created, closed, admin_entry, start_event, league_type, scoring}, new_entries:{has_next, page, results}, standings:{has_next, page, results:[{id, entry, entry_name, player_name, rank, last_rank, rank_sort, total, event_total}]}} — `entry` is the manager id for fpl_manager; `rank` vs `last_rank` gives movement. Big leagues page at 50. Example: A league table {"leagueId": 314} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

The highest-scoring XI of a completed gameweek. Returns: {top_player:{id, points}, team:[{element, position, points}]} — 404s until the gameweek is finished. Example: A gameweek's best XI {"gameweek": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Whether bonus points and league tables have been finalised for the current gameweek. Returns: {status:[{bonus_added, date, event, points:'r'|'p'|'l'}], leagues:'Updated'|''} — this is how you know scores are FINAL. `bonus_added: false` means bonus points are still provisional, so a score read now may change. Example: Is this gameweek settled? Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Fixtures with FPL difficulty ratings, and goal/assist/bonus breakdowns once played. Returns: [{id, code, event, team_h, team_a, team_h_score, team_a_score, kickoff_time, started, finished, finished_provisional, minutes, team_h_difficulty:1-5, team_a_difficulty:1-5, stats:[{identifier:'goals_scored'|'assists'|'bonus'|'bps'|'saves'|…, h:[{element, value}], a:[{element, value}]}]}] — `stats` is EMPTY until the match is played, then carries per-player contributions keyed by player id. The two difficulty ratings are from each side's perspective. `finished_provisional` goes true before `finished`: bonus points are not final until `finished`. Example: One gameweek's fixtures {"event": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Positions, chips, phases and scoring settings — the lookup tables the other tools' ids refer to. Returns: {element_types:[{id:1-4, singular_name:'Goalkeeper', plural_name, squad_select, squad_min_play, squad_max_play, element_count}], chips:[{id, name:'wildcard'|'freehit'|'bboost'|'3xc', number, start_event, stop_event}], phases:[{id, name:'Overall'|'August', start_event, stop_event}], game_settings:{squad_squadplay, squad_total_spend, transfers_cost, transfers_limit, …}, element_stats:[{label:'Goals scored', name:'goals_scored'}], total_players:4085510} — `element_types` resolves the `element_type` id on every player (1 GK, 2 DEF, 3 MID, 4 FWD). `total_players` is how many squads exist worldwide, which is what an overall rank is out of. Example: The lookup tables Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

All 38 gameweeks: deadlines, average scores, highest score, chip usage, and which one is current. Returns: {events:[{id:1-38, name:'Gameweek 1', deadline_time:'2026-08-15T17:30:00Z', deadline_time_epoch, finished, data_checked, is_previous, is_current, is_next, average_entry_score, highest_score, highest_scoring_entry, most_selected, most_transferred_in, most_captained, most_vice_captained, top_element, transfers_made, chip_plays:[{chip_name, num_played}]}]} — `deadline_time` is THE thing an agent needs: transfers and lineup changes lock at it. `is_current`/`is_next` are how you find where the season is without doing date arithmetic. Example: The full gameweek calendar Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Head-to-head league standings with win/draw/loss records. Returns: {league:{id, name, league_type, scoring:'h'}, standings:{has_next, page, results:[{id, entry, entry_name, player_name, rank, last_rank, total, matches_played, matches_won, matches_drawn, matches_lost, points_for}]}} — `total` is H2H league points (3 a win), `points_for` the FPL points scored. Ranking is on `total`, so a high scorer can sit mid-table. Example: An H2H table {"leagueId": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Live per-player scoring for a gameweek — points as they are being earned. Returns: {elements:[{id, stats:{minutes, goals_scored, assists, clean_sheets, goals_conceded, saves, bonus, bps, total_points, expected_goals, …}, explain:[{fixture, stats:[{identifier, points, value}]}]}]} — `explain` breaks a player's points down by WHY they were awarded, which is the only way to reconcile a score. Returns `{elements: []}` for a gameweek that has not started — empty is normal pre-season, not a failure. Example: Live scoring for a gameweek {"gameweek": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

A manager's squad summary: overall rank, points, and every league they are in. Returns: {id, name:'Squad Name', player_first_name, player_last_name, player_region_name, summary_overall_points, summary_overall_rank, summary_event_points, summary_event_rank, current_event, started_event, last_deadline_bank, last_deadline_value, last_deadline_total_transfers, leagues:{classic:[{id, name, entry_rank, entry_last_rank}], h2h:[…], cup:{…}}} — `last_deadline_value` and `last_deadline_bank` are in TENTHS of a million, like player prices. Example: A manager's summary {"managerId": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

A manager's gameweek-by-gameweek history, past seasons, and chips already used. Returns: {current:[{event, points, total_points, rank, overall_rank, bank, value, event_transfers, event_transfers_cost, points_on_bench}], past:[{season_name:'2024/25', total_points, rank}], chips:[{name:'wildcard', time, event}]} — `chips` is what has ALREADY been played, which is how you know what is still available. `current` is empty before gameweek 1. Example: A manager's season {"managerId": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

The exact XI, bench order, captain and chip a manager used in a gameweek. Returns: {active_chip, automatic_subs:[{element_in, element_out}], entry_history:{event, points, total_points, rank, bank, value, event_transfers, event_transfers_cost, points_on_bench}, picks:[{element, position:1-15, multiplier:0|1|2|3, is_captain, is_vice_captain}]} — `position` 1-11 is the XI and 12-15 the bench IN ORDER. `multiplier` 2 is the captain, 3 a triple-captain chip, and 0 means they did not play (benched). Example: A manager's gameweek team {"managerId": 1, "gameweek": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set. Also answers this: espnfantasy_rosters, sleeper_league_rosters, yahoo_team_roster.

YOUR current squad including picks not yet visible to others, plus bank, free transfers and chip availability. Needs your FPL session cookie. Returns: {picks:[{element, position, selling_price, purchase_price, multiplier, is_captain, is_vice_captain}], chips:[{status_for_entry:'available'|'played'|'unavailable', name, number, start_event, stop_event, chip_type}], transfers:{cost, status, limit, made, bank, value}} — the ONE place `selling_price` and `purchase_price` appear: FPL sells a risen player back at half the gain, so selling_price is often below now_cost and that difference decides whether a transfer is affordable. Returns 403 {'detail':'Authentication credentials were not provided.'} without FPL_SESSION_COOKIE. Example: Your own squad {"managerId": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set. Also answers this: espnfantasy_rosters, sleeper_league_rosters, yahoo_team_roster.

One player in full: every gameweek this season, past seasons, and upcoming fixtures with difficulty. Returns: {fixtures:[{id, event, team_h, team_a, is_home, difficulty:1-5, kickoff_time}], history:[{element, fixture, round, total_points, minutes, goals_scored, assists, clean_sheets, bonus, bps, expected_goals, value, transfers_balance, selected, was_home, opponent_team}], history_past:[{season_name:'2024/25', total_points, minutes, goals_scored, end_cost, start_cost}]} — `difficulty` is FPL's own 1 (easiest) to 5 (hardest) rating, and it drives most fixture-run analysis. `value` in history is the price AT THAT GAMEWEEK, so you can see price movement. Example: One player's full record {"playerId": 1} Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Every FPL player with price, form, ownership, expected goals and availability. LARGE — ~65k tokens for all 581 players; use fpl_player_detail for one player's depth. Returns: {elements:[{id, web_name:'Salah', team:11, element_type:3, now_cost:145, total_points, points_per_game:'6.2', form:'5.4', selected_by_percent:'42.1', status:'a'|'i'|'d'|'s'|'u', news:'Knock - 75% chance of playing', chance_of_playing_next_round, minutes, goals_scored, assists, clean_sheets, bonus, expected_goals:'0.54', expected_assists, defensive_contribution, ict_index, ep_next:'6.1'}]} — `now_cost` is TENTHS of a million (145 = £14.5m). `status`: a available, i injured, d doubtful, s suspended, u unavailable. Trimmed from 105 fields per player to 22; the upstream blob is ~362k tokens, which no context window holds. Example: Every player, key fields Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

Official set-piece taker notes per club — who takes penalties, corners and free kicks. Returns: {last_updated, teams:[{id, notes:[{external_link, info_message:'Penalties: Haaland, then Alvarez', source_link}]}]} — genuinely useful for FPL and priced-market work alike: penalty duty is worth several points a season and moves with injuries. Example: Who takes the penalties Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

The 20 Premier League clubs with FPL's attack/defence strength ratings. Returns: {teams:[{id:1-20, name:'Arsenal', short_name:'ARS', code, strength:1-5, strength_overall_home, strength_overall_away, strength_attack_home, strength_attack_away, strength_defence_home, strength_defence_away, played, win, draw, loss, points, position, form}]} — `id` is FPL's own alphabetical 1-20, NOT the Premier League's official team id; join to the `premierleague` provider by name. The strength_* numbers are FPL's internal ratings (~1000-1400) and are what fixture-difficulty is derived from. Example: All 20 clubs Auth: works without a key; FPL_SESSION_COOKIE unlocks more if set.

One course in full: every tee box with per-hole par, yardage and stroke index. Returns: {course:{id, club_name, course_name, location:{…}, tees:{male:[{tee_name, course_rating, slope_rating, par_total, total_yards, number_of_holes, holes:[{par, yardage, handicap}]}], female:[…]}}} — SHAPE FROM VENDOR DOCS. NOTE `tees` is split by MALE/FEMALE tee sets, each a LIST of tee boxes, each with its own 18-hole array — three levels before a hole. `handicap` here is the hole's stroke index (1 = hardest), not a player handicap. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: One course in full {"id": 1} Auth: needs your own key in GOLFCOURSE_API_KEY.

Search the course catalogue by name or club. Returns: {courses:[{id, club_name, course_name, location:{address, city, state, country, latitude, longitude}}]} — SHAPE FROM VENDOR DOCS. Search returns the summary only; per-hole data needs golfcourseapi_course. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Find a course {"search_query": "Pebble Beach"} Auth: needs your own key in GOLFCOURSE_API_KEY.

Baseball highlight clips. Returns: {data:[{id, title, url, embedUrl, imgUrl, match:{…}}], pagination} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's baseball highlights {"date": "2024-07-04"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Basketball highlight clips (NBA, EuroLeague and others). Returns: {data:[{id, title, url, embedUrl, imgUrl, match:{…}}], pagination} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's basketball highlights {"date": "2024-01-15"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Ice-hockey highlight clips. Returns: {data:[{id, title, url, embedUrl, imgUrl, match:{…}}], pagination} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's hockey highlights {"date": "2024-01-15"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

American-football highlight clips. Returns: {data:[{id, title, url, embedUrl, imgUrl, match:{…}}], pagination} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's NFL highlights {"date": "2024-01-15"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Football highlight clips, by match, league or date. The main tool here. Returns: {data:[{id, title, type, url, imgUrl, embedUrl, channel, source, match:{id, date, league, homeTeam, awayTeam}}], pagination:{totalCount, limit, offset}} — SHAPE FROM VENDOR DOCS. `url` is a page link and `embedUrl` an iframe source; they are not interchangeable. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's football highlights {"date": "2024-08-17"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Football competitions covered, with the leagueId filters. Returns: {data:[{id, name, logo, country:{code, name, logo}, seasons:[…]}], pagination} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Competitions covered Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Football matches, to find the matchId a highlight lookup needs. Returns: {data:[{id, date, country, league:{id, name, logo}, homeTeam:{id, name, logo}, awayTeam:{…}, state:{description, score:{current, penalties}}}], pagination} — SHAPE FROM VENDOR DOCS. The score is nested under `state`, not on the match. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's matches {"date": "2024-08-17"} Auth: needs your own key in HIGHLIGHTLY_API_KEY.

Basketball fixtures and results by date. Returns: {code:0, data:[{matchId, leagueId, homeName, awayName, matchTime, status, homeScore, awayScore, quarterScores}]} — SHAPE FROM VENDOR DOCS. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's games {"date": "2024-01-15"} Auth: needs your own key in ISPORTS_API_KEY.

Football competitions with their ids. Returns: {code:0, data:[{competitionId, name, shortName, logo, type, color}]} — SHAPE FROM VENDOR DOCS. `code: 0` means success; anything else is an error delivered with HTTP 200. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Every competition Auth: needs your own key in ISPORTS_API_KEY.

Football matches in play now. Returns: {code:0, data:[{matchId, status, homeScore, awayScore, homeHalfScore, awayHalfScore, homeRed, awayRed, homeYellow, awayYellow, homeCorner, awayCorner, updateTime}]} — SHAPE FROM VENDOR DOCS. Corners and cards live here rather than in a separate statistics call. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: In play now Auth: needs your own key in ISPORTS_API_KEY.

Asian-handicap odds across companies — the reason to use this provider. Returns: {code:0, data:{handicap:[[matchId, companyId, initialHandicap, initialHome, initialAway, liveHandicap, liveHome, liveAway, …]], europeOdds:[[…]], overUnder:[[…]]}} — SHAPE FROM VENDOR DOCS. NOTE the payload is ARRAYS OF POSITIONAL ARRAYS, not objects: fields are identified by INDEX. Read the vendor's column order before parsing, and do not assume it matches other providers here. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: Asian handicap odds Auth: needs your own key in ISPORTS_API_KEY.

Football fixtures and results by date. Returns: {code:0, data:[{matchId, competitionId, homeId, homeName, awayId, awayName, matchTime, status, homeScore, awayScore, halfHomeScore, halfAwayScore}]} — SHAPE FROM VENDOR DOCS. `matchTime` is a UNIX TIMESTAMP, not an ISO string. NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name. Example: A day's fixtures {"date": "2024-08-17"} Auth: needs your own key in ISPORTS_API_KEY.

Circuits, with location and coordinates. Returns: {MRData:{CircuitTable:{Circuits:[{circuitId, circuitName, Location:{lat, long, locality, country}, url}]}}} Example: 2024 circuits {"season": "2024", "format": "json"} Auth: none needed.

Constructors' championship standings. Returns: {MRData:{StandingsTable:{StandingsLists:[{season, round, ConstructorStandings:[{position, points, wins, Constructor:{constructorId, name, nationality}}]}]}}} Example: 2024 constructors' championship {"season": "2024", "format": "json"} Auth: none needed.

Constructors (teams) — all-time, or those entered in one season. Returns: {MRData:{ConstructorTable:{season, Constructors:[{constructorId, name, nationality, url}]}}} Example: 2024 constructors {"season": "2024", "format": "json"} Auth: none needed.

Drivers' championship standings — after a season, or after a specific round. Returns: {MRData:{StandingsTable:{season, round, StandingsLists:[{season, round, DriverStandings:[{position, points, wins, Driver:{driverId, code, familyName}, Constructors:[{constructorId, name}]}]}]}}} — note the extra StandingsLists layer Example: 2024 drivers' championship {"season": "2024", "format": "json"} Auth: none needed.

Drivers — all-time, or the field for one season. Returns: {MRData:{DriverTable:{season, Drivers:[{driverId, permanentNumber, code, givenName, familyName, dateOfBirth, nationality, url}]}}} — `driverId` (e.g. 'max_verstappen') is the key every other tool filters on Example: 2024 field {"season": "2024", "format": "json"} Auth: none needed.

Lap-by-lap times for every driver in a race. LARGE — page it or narrow to one lap. Returns: {MRData:{total, RaceTable:{Races:[{Laps:[{number, Timings:[{driverId, position, time}]}]}]}}} — one entry per lap, each holding every driver's timing Example: First laps of 2024 round 1 {"season": "2024", "round": "1", "format": "json", "limit": 100} Auth: none needed.

Pit stops for a race: lap, time of day and stationary duration. Returns: {MRData:{RaceTable:{Races:[{PitStops:[{driverId, lap, stop, time, duration}]}]}}} — `duration` is stationary time ('23.2'), `time` is clock time of day Example: 2024 round 1 pit stops {"season": "2024", "round": "1", "format": "json"} Auth: none needed.

Qualifying results with Q1/Q2/Q3 times per driver. Returns: {MRData:{RaceTable:{Races:[{QualifyingResults:[{position, Driver, Constructor, Q1, Q2, Q3}]}]}}} — Q2/Q3 absent for drivers eliminated earlier Example: 2024 round 1 qualifying {"season": "2024", "round": "1", "format": "json"} Auth: none needed.

A season's race calendar with dates, circuits and (from 2021) each session's date/time. Returns: {MRData:{RaceTable:{season, Races:[{season, round, raceName, date, time, url, Circuit:{circuitId, circuitName, Location}, FirstPractice, Qualifying, Sprint}]}}} — `round` is what the result tools take Example: 2024 calendar {"season": "2024", "format": "json"} Auth: none needed.