---
title: "Match Preview"
method: POST
path: "/skills/match-preview"
tags: ["skills"]
---

# Match Preview

`POST /skills/match-preview`

## Request

- Base URL: `https://api.machina.gg/world-cup/v1`
- URL: `https://api.machina.gg/world-cup/v1/skills/match-preview`
- Auth: HTTP bearer

Grounded preview: form, key men, group context, market snapshot.

## Request body

- object: Identify the fixture in plain English, pass `event` free text, or `team` (+ optional `opponent` + `date`). No URNs or provider ids needed; unresolved inputs return an explicit warning, ambiguous ones return candidates. The response echoes the resolved `event_urn` (and `resolved_fixture`) so follow-up calls can chain on it.
  - `event` string: Plain-English fixture, e.g. "Brazil vs Morocco" (also accepts "v" / "x" / "-" separators).
  - `team` string: Team name, e.g. "Morocco". Use with optional `opponent` and `date`.
  - `opponent` string: Optional opponent name to disambiguate the fixture.
  - `date` string, date: Optional fixture date as YYYY-MM-DD.
  - `event_urn` string: Canonical event URN, if you already have one (every fixture response echoes it). Plain-English inputs above make this optional.

## Response `200`

Structured World Cup intelligence. The response echoes the resolved `event_urn` (and `resolved_fixture`) so follow-up calls can chain on it. Response schemas are partial during the developer preview.

## Other responses

- `401`: Missing or invalid API key.
- `402`: Insufficient credits for this endpoint; `error.top_up_url` says where to top up. Metered endpoints only.

---

[API](https://skmtc.dev/machina/apis/machina-world-cup-intelligence-apis.md) · [All operations](https://skmtc.dev/machina/apis/machina-world-cup-intelligence-apis/llms.txt) · [OpenAPI document](https://skmtc.dev/machina/apis/machina-world-cup-intelligence-apis/revisions/60b3b92bde77?raw)