# Match Recap

> Match Recap is a paid API for AI agents from agents.machina.gg, paid per call via MPP or x402, $0.4/call, status healthy (last checked 2026-09-14, last successful call 2026-09-03).

Returns a post-match editorial recap for a completed World Cup 2026 fixture, addressable by plain-English fixture name, team/opponent/date, or event URN.

## Facts

- Endpoint: POST https://agents.machina.gg/world-cup/v1/skills/match-recap
- Price: $0.4/call
- Payment: MPP, x402
- Status: healthy
- Last checked: 2026-09-14
- Last successful call: 2026-09-03
- Success rate: 100% of calls made through Zero
- Activations on Zero: 1
- Provider: agents.machina.gg
- Website: https://agents.machina.gg
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agents-machina-gg-match-recap-469828fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t47eP0Ja3q-xx6ULsUVYQ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-machina-gg-match-recap-469828fb -d '<json body>'
```

Example prompt: Can you get me the post-match recap for Brazil vs Morocco from the 2026 World Cup — the editorial summary written after the final whistle?

## When to prefer this

Use this endpoint when you need the finished editorial narrative of a completed World Cup 2026 match. It accepts flexible plain-English inputs (fixture name, team/opponent/date) without requiring provider-specific IDs, and automatically resolves canonical URNs. Prefer it over general web search when you need structured, source-cited, grounded recap content tied to the Machina entity model, especially when chaining with other Machina endpoints like match context or player performance.

## Known failure modes

- Fixture not yet finished — recap not available until after final whistle
- Ambiguous input returns a list of candidate fixtures rather than a single recap
- Unresolvable team name or event string returns an explicit warning
- Invalid date format returns a validation error
- event_urn not found returns a not-found error

## How this service works

Post-match recap authored once the final whistle blows, addressable by event, event URN, or team and opponent on a date.

## Output

Returns a structured JSON object containing the authored post-match editorial recap text, the resolved fixture details (teams, date, score), the canonical event URN, and source citations. The response echoes the event URN so downstream calls can chain on it. Only available for matches where the final whistle has blown.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "date": {
   "type": "string",
   "format": "date",
   "description": "Optional fixture date as YYYY-MM-DD."
  },
  "team": {
   "type": "string",
   "description": "Team name, e.g. \"Morocco\". Use with optional `opponent` and `date`."
  },
  "event": {
   "type": "string",
   "description": "Plain-English fixture, e.g. \"Brazil vs Morocco\" (also accepts \"v\" / \"x\" / \"-\" separators)."
  },
  "opponent": {
   "type": "string",
   "description": "Optional opponent name to disambiguate the fixture."
  },
  "event_urn": {
   "type": "string",
   "description": "Canonical event URN, if you already have one (every fixture response echoes it). Plain-English inputs above make this optional."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-machina-gg-match-recap-469828fb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.machina.gg](https://www.zero.xyz/host/agents.machina.gg/llms.txt)