CricketStudio REST API

Programmatic access to the same atomic-claim data the MCP server exposes. Coming Q3 2026.

Phase B (Q3 2026): the REST API surface is documented below. Endpoints, response shape, pricing, and authentication all locked. Implementation rolls out over months 4-6 alongside the HTTP MCP transport. Want early access? Email hello@cricketstudio.ai with your use case.

Same data spine as the MCP server, exposed as REST. 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.

Tier	Price	Includes	Target
Free	$0	1K calls/month · 100/day rate limit	Hobbyists, students, validators
Indie	$49/mo	25K calls/month	Indie devs, journalists
Pro	$199/mo	250K calls/month · priority support	Cricket apps, agencies
Business	$499/mo	1M calls/month · SLA	Fantasy operators, broadcasters
Enterprise	From $5K/mo	Unlimited · dedicated support · data dumps	LLM providers, big media

Endpoint catalog

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).

Method	Path	Description
`GET`	`/api/v1/players`	List all players with pagination
`GET`	`/api/v1/players/{slug}`	Player profile + atomic claims
`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
`GET`	`/api/v1/matches/{id}/recap`	Match recap pack (6 cards)
`GET`	`/api/v1/season/ipl-2026/{aspect}`	Season aspect (orange-cap, purple-cap, etc.)
`GET`	`/api/v1/records/ipl-2026/{type}`	Single record (highest-individual-score, etc.)
`GET`	`/api/v1/leadership/captain/{player}/{condition}`	Captain conditional aggregate
`GET`	`/api/v1/trends`	List trends (filterable)
`GET`	`/api/v1/trends/{id}`	Single trend insight
`GET`	`/api/v1/standings`	Live points table + NRR
`GET`	`/api/v1/atomic-claims`	Filtered query across the claim corpus

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 aggregation of CricketMind ball-by-ball data",
  "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 12 honest, sample-size-floored tools.

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.