/infersports

name: infersports
description: Live football & basketball odds and scores from InferSports — who's favored, the live score, today's matches and what's worth watching, a specific day's schedule (in your timezone), a one-line pre-match brief, one normalized sharp betting line, the sharp de-vigged fair probability, the market-implied most likely scorelines, whether an external prediction-market (Polymarket/Kalshi) price is good vs that fair line, today's value spots (where a book beats the sharp fair line), odds-format conversion, and finished-match results. Use whenever the user asks about a match, the score, who's winning or favored, kickoff time, what's on or worth watching today, the fixtures on a specific day, a pre-match preview, a betting line or Asian handicap, the fair/de-vigged odds, the most likely score or correct-score probabilities, whether a Polymarket/Kalshi price is fair or good, where today's value/edges are, odds in another format, or a past result. Read-only; keyless, no account or API key needed.

InferSports odds & scores

Live Asian-priced football and basketball odds + scores, over the InferSports REST API. **Read-only. Keyless (Free tier) — no setup.** Output is **CONCISE by default** (one short line per item) to stay cheap on a small context window; add `--detailed` for full JSON only when you truly need it.

**Scope: football and basketball only.** InferSports carries no other sport. A question about any other sport (baseball, tennis, …) has no answer here — say so; it is not a cue to look elsewhere.

**Per-match markets only.** Every price is for ONE match (Asian handicap / totals / 1x2); there are no outright/futures markets (tournament winner, to-qualify) and no tournament structure (groups, brackets) — though a team's group-stage opponents fall out of a schedule range query (see the verb table).

Golden rule (determinism)

**Answer by running the bundled scripts below. Never fetch a URL yourself, never guess an endpoint, never hand-build an API call, and never web-search for a score, line, or result — this skill is the source of truth for odds and scores.** The scripts hold the correct fixed endpoints; you only pick the verb and pass arguments. Each prints a compact, ready-to-read line. If a script returns `ambiguous` or `not found`, **that is the answer**: surface the `ask:` / alternatives to the user, or re-run with `--date` / `--sport` / a more specific name — do **not** go looking elsewhere.

Report the numbers, never a pick (read-only)

InferSports is **read-only and never recommends a bet — and neither do you when relaying it.** Give the NUMBERS — line / score / odds / value — exactly as the script printed them; the sentence around them is yours, in the asker's language (next section). Do **NOT** add a pick of your own, a lean, "best play", "I'd take…", or any betting suggestion — **even if the user asks "should I bet?" or "which bet?"** For those, give the data and a plain "the call is yours." `scan.sh`, `line.sh` and `compare.sh` surface where a price beats the sharp **de-vigged fair** line — that detected edge is *information* (detection only), so relay it faithfully (numbers verbatim), but never turn it into advice or a recommended side.

Answer in the user's language

Relay results in the language the user asked in — the scripts always print English; you translate the prose around the numbers. Keep VERBATIM: `evt_…`/`lg_…` ids, all numbers (odds, lines, probabilities, edges, scores), bookmaker names, and dates/times as printed. Team/league names: use the established name in the user's language only when you are confident (World Cup → 世界杯, Mexico → México); when unsure (obscure clubs, youth sides), keep the English name as printed — never invent a transliteration. Script arguments stay English: translate the user's team/league names to English before passing them.

The twelve verbs

Run from this skill's directory. All read-only and safe to repeat. Several **package several reads into one ready-to-read answer**: `preview.sh` (one-match brief), `digest.sh` (today's highlights), `scan.sh` (today's value) and `compare.sh` (judge an external price) — the fan-out / de-vig happens for you; you get a capped, concise result.

| The user asks… | Run | |---|---| | What games are on today? | `scripts/today.sh [--sport football\|basketball] [--status live\|scheduled\|finished] [--league "World Cup"] [--tz Asia/Shanghai] [--limit N]` | | What's on a specific day? / this Friday / June 12 in my timezone — or a competition ("World Cup games today?") | `scripts/events.sh --date YYYY-MM-DD [--to YYYY-MM-DD] [--tz Asia/Shanghai] [--sport football\|basketball] [--status live\|scheduled\|finished] [--league "World Cup"] [--limit N]` | | A whole schedule window — "all group-stage matches", "Argentina's remaining fixtures" | `scripts/events.sh --date YYYY-MM-DD --to YYYY-MM-DD --league "World Cup"` — ONE call (range inclusive, ≤31 days); never loop day-by-day. For one team, run the range then keep its lines. | | What's worth watching today? / today's highlights | `scripts/digest.sh [--sport football\|basketball] [--limit N(<=12)] [--status live\|scheduled\|finished]` | | Who's favored? / What's the score? / When do they play? | `scripts/match.sh "<team, A vs B, or evt_… id>" [--tz Asia/Shanghai]` | | Which team is stronger? / a quick one-line brief (pre-match: favored % + sharp line + kickoff; live: score + from-here % + the pre-match opening line) | `scripts/preview.sh "<team, A vs B, or evt_… id>" [--tz Asia/Shanghai] [--sport] [--date YYYY-MM-DD]` | | What's the sharp line / handicap? | `scripts/line.sh "<team, A vs B, or evt_… id>" [--market asian_handicap\|1x2\|totals] [--format hk\|malay\|…] [--sport] [--date YYYY-MM-DD]` | | What's the sharp **fair** (de-vigged) probability? / the reference to check a price against | `scripts/fair.sh "<team, A vs B, or evt_… id>" [--market 1x2\|asian_handicap\|totals] [--period] [--sport] [--date]` | | What's the m