---
title: "Match Info"
method: POST
path: "/v1/mcp/match_info"
tags: ["mcp"]
---

# Match Info

`POST /v1/mcp/match_info`

## Request

- Base URL: `https://api.infersports.dev` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infersports.dev/v1/mcp/match_info`
- Auth: none declared

## Request body

- MatchInfoRequest
  - `query` string, required: Natural-language fixture or team, e.g. 'Brazil vs Argentina' or just 'Brazil'.
  - `timezone` string, nullable: Optional IANA timezone (e.g. 'America/New_York', 'Asia/Shanghai') to show the kickoff time in local time; default UTC.
  - `sport` string, nullable: Optional filter: football | basketball.
  - `date` string, nullable: Optional UTC date 'YYYY-MM-DD' to disambiguate same-name fixtures.

## Response `200`

Successful Response

- MatchInfoResult: One-call NL→basics: score, status, kickoff (local), and who's favored — no betting knowledge needed. The casual front door. ``status`` is the same go/no-go as get_sharp_line (ok | ambiguous | not_found; ambiguous is never guessed). ``summary`` is a ready-to-read one-liner. ``favorite`` and ``implied_probabilities`` are best-effort — null when no 1x2 is on file (e.g. the sharp book is gated on the Free tier and no other book quotes 1x2 for this fixture).
  - `status` string, required
  - `query` string, required
  - `summary` string, required
  - `match` MatchSummary: A fixture flattened for agent consumption (teams as names, optional live score).
    - `event_id` string, required: Canonical event id (evt_…); pass to get_match_odds / compare_lines.
    - `sport` string, required: football | basketball
    - `league` string, required: League name, e.g. 'English Premier League'.
    - `home_team` string, required
    - `away_team` string, required
    - `scheduled_at` string, nullable: Kickoff, ISO-8601 UTC.
    - `scheduled_at_local` string, nullable: Kickoff in the requested timezone (ISO-8601); null when no timezone was given.
    - `status` string, required: scheduled | live | finished
    - `score` Score
      - `home` integer, required
      - `away` integer, required
    - `red_cards` Score
      - `home` integer, required
      - `away` integer, required
    - `clock` string, nullable: Match clock when live, humanized for display: e.g. '1st half 25'', '2nd half 47'' (the real minute, not estimated) or 'half-time'; null pre-match or when the feed omits it. Basketball clocks (e.g. 'Q2 4:12') pass through as-is.
    - `confidence` number, nullable: Fuzzy-match confidence 0–1 (find_match only; null elsewhere).
    - `summary` string, nullable: One-line human-readable status, e.g. "Man City vs Arsenal — LIVE 1h 23 2-1." or "… — Kicks off 18:00 UTC on Jun 01." — ready to read to a user.
  - `scheduled_at_local` string, nullable: Kickoff in the requested timezone (ISO-8601); null if no timezone given or unparseable.
  - `timezone` string, nullable: Echo of the requested timezone.
  - `favorite` Favorite: Who the market favors, in plain terms — de-vigged from the full-time 1x2 line.
    - `outcome` string, required: home | draw | away.
    - `team` string, nullable: Team name for home/away; null for a draw.
    - `win_probability` number, required: De-vigged implied probability for this outcome (0–1).
    - `source` string, nullable: Bookmaker key the 1x2 was de-vigged from.
  - `implied_probabilities` object, nullable: De-vigged win probabilities per 1x2 outcome (home/draw/away); null when no 1x2.
  - `alternatives` MatchAlternative[]
    - `event_id` string, required
    - `label` string, required: 'Home vs Away' label for disambiguation.
    - `confidence` number, required
  - `ask_user` string, nullable
  - `as_of` string, nullable
  - `stale` boolean, nullable: Freshness of the data (W4); null when no match resolved.
  - `decision` Decision, required: Pre-computed go/no-go for the caller (W3): we decide whether it's safe to proceed so the agent doesn't have to reason it out (and risk guessing). Branch on ``safe_to_proceed``: true → act on the result without asking; false → put ``ask_user`` to the human, or follow ``next_action`` when there's a clear recovery step (e.g. nothing resolved → list fixtures).
    - `safe_to_proceed` boolean, required: True when the result is unambiguous enough to act on without asking the user.
    - `confidence` number, nullable: Resolution confidence 0–1 (null when not applicable).
    - `ask_user` string, nullable: A disambiguation question to put to the user; null when safe_to_proceed.
    - `next_action` NextAction: The single best next call to make, pre-computed so the agent doesn't have to plan it (W3).
      - `tool` string, required: Tool to call next, e.g. 'get_match_odds' | 'compare_lines' | 'list_today_matches'.
      - `args` object: Ready-to-use arguments for that call, e.g. {'event_id': 'evt_…'}.
      - `reason` string, required: Why this is the suggested next step.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/infersports/apis/infersports-api.md) · [All operations](https://skmtc.dev/infersports/apis/infersports-api/llms.txt) · [OpenAPI document](https://skmtc.dev/infersports/apis/infersports-api/revisions/1a1c3b357ea7?raw)
