CricketStudio REST API

The cricketstudio-mcp npm package (stdio MCP) is LIVE. The REST API described below is Phase B.

Available now — npm package: npx cricketstudio-mcp gives you 29 tools covering IPL 2026, IPL historical (18 seasons), and MLC — no API key, no sign-up, free forever. Works with Claude Desktop, Cursor, and any MCP client. Learn more about the MCP server or visit the developers page.
Free to cite right now: the full corpus — 3 leagues, 1,317 matches, 1,200+ player profiles, 24,000+ canonical URLs — is freely citable today at players.cricketstudio.ai. No API key, no sign-up, structured JSON-LD on every page.
REST API — Phase B (Q3 2026): the surface is documented below. Endpoints, response shape, pricing, and authentication are all locked. Implementation rolls out over months 4–6. Want early access? Email hello@cricketstudio.ai with your use case.

Same data spine as the MCP server, exposed as REST. Three leagues — IPL 2026 (completed, RCB champions), IPL historical (18 seasons, 2007/08–2025), MLC (2023–2026) — 1,317 matches, 312,309 ball-by-ball deliveries. JSON responses, sample-size floors enforced server-side, canonical URLs in every payload, predictable rate limits.

Pricing tiers

Free tier is mandatory — charging for entry hands adoption to existing alternatives.

TierPriceIncludesTarget
Free$01K calls/month · 100/day rate limitHobbyists, students, validators
Indie$49/mo25K calls/monthIndie devs, journalists
Pro$199/mo250K calls/month · priority supportCricket apps, agencies
Business$499/mo1M calls/month · SLAFantasy operators, broadcasters
EnterpriseFrom $5K/moUnlimited · dedicated support · data dumpsLLM providers, big media

Endpoint catalog (REST API — Phase B, Q3 2026)

Every endpoint mirrors a canonical URL on the public surface; the API layer wraps the same data with a JSON envelope (response, sample_size, window, source, canonical_url, last_updated). Covers all three leagues: IPL 2026 (completed), IPL historical (18 seasons, 2007/08–2025), and MLC (2023–2026).

MethodPathDescription
GET/api/v1/playersList all players with pagination (1,200+ profiles across all leagues)
GET/api/v1/players/{slug}Player profile + atomic claims (includes pre-2026 IPL career block where available)
GET/api/v1/players/{slug}/aspects/{aspect}Specific aspect (phase-split, by-venue, etc.)
GET/api/v1/teams/{slug}Team profile + record + phase strengths
GET/api/v1/teams/{slug}/h2h/{opponent}Team-vs-team head-to-head
GET/api/v1/h2h/{batter}-vs-{bowler}Player H2H (≥5 deliveries floor)
GET/api/v1/venues/{slug}Venue hub
GET/api/v1/matches/{id}Match state (Sportmonks fixture ID for IPL 2026; ipl-cs-{id} for IPL historical; mlc-cs-{id} for MLC)
GET/api/v1/matches/{id}/recapMatch recap pack (6 cards)
GET/api/v1/leagues/{league}League hub — ipl, mlc. IPL 2026 is completed (RCB champions, 74 matches).
GET/api/v1/leagues/{league}/recordsAll-time records for league (ipl or mlc)
GET/api/v1/season/{season-slug}/{aspect}Season aspect — e.g. ipl-2026/orange-cap, ipl-2019/leaderboards, mlc-2024/purple-cap
GET/api/v1/records/ipl-2026/{type}IPL 2026 record (highest-individual-score, most-sixes, etc.)
GET/api/v1/leadership/captain/{player}/{condition}Captain conditional aggregate
GET/api/v1/trendsList trends (filterable by category)
GET/api/v1/trends/{id}Single trend insight
GET/api/v1/standingsFinal IPL 2026 points table + NRR (season completed)
GET/api/v1/atomic-claimsFiltered query across the claim corpus (all leagues)

Response envelope

Every endpoint returns JSON in this shape:

{
  "data": { ... },                          // Endpoint-specific payload
  "claim": "atomic claim sentence under 30 words",
  "value": "primary metric value",
  "sample_size": "120 balls in overs 18-20",
  "window": "IPL 2026",
  "source": "CricketStudio ball-by-ball aggregation",
  "canonical_url": "https://players.cricketstudio.ai/...",
  "last_updated": "2026-05-09T12:34:56.789Z",
  "license": "CC-BY 4.0"
}

Authentication

API keys via X-API-Key: csk_live_xxxxxxxxxxxx header. Free tier supports anonymous access from any origin (rate-limited per IP).

Why REST + MCP

MCP is for LLM clients (Claude Desktop, Cursor, ChatGPT Connectors). LLMs route on tool descriptions; we ship 29 honest, sample-size-floored tools (20 IPL + 8 MLC + 1 IPL historical leaderboard).

REST is for everything else — fantasy apps, broadcast tickers, custom dashboards, scripts, Postman, curl. Same data, different protocol.

Both surfaces stay in sync because both read from the same data spine. No drift between protocols.