An agent can read that a forecast costs 12 credits and a market lookup costs 3 before deciding how to answer, which is the difference between a considered query plan and an expensive one. worldcup_explain_market_move is the tool that stands out on substance: a source-cited explanation of a price movement is a genuinely hard thing to produce and exactly what a human would ask. Note this is betting-adjacent tooling — the signals are informational, and the backtest with a CLV ledger is there so you can judge the model rather than trust it.
Machina's World Cup endpoint. It joins a Dixon-Coles match model to live prediction-market prices and looks for the gap between them. Every tool states its credit cost in its own description.
- worldcup_health — a free whoami and key check
- worldcup_get_schedule and worldcup_resolve — fixtures with their ids, and any provider id or free-text name resolved to a canonical entity
- worldcup_get_event_context — form, standings slice, injuries and optional research for one fixture
- worldcup_search_markets and worldcup_get_market_state — Kalshi and Polymarket in one normalised shape, then one market's price, book depth and history
- worldcup_get_match_forecast — 1X2 probabilities and the model-versus-market gap, 12 credits
- worldcup_find_market_edges and worldcup_get_signal — scan for gaps across the tournament, or fuse model and best price into a per-fixture recommendation
- worldcup_backtest_forecasts and worldcup_explain_market_move — calibration and CLV history, and a source-cited explanation of why a price moved
An API key, checked at tool level rather than at connection. Costs are per tool: health is free, market tools 3 credits, a forecast 12.
Paste a URL with a key — add the endpoint to your client