Skip to main content

Machine Readable Docs

Copy one of the context blocks below and paste it into any AI tool. It gives the AI enough knowledge of the Sportmicro APIs and docs structure to help with integration, endpoint discovery, filters, and code generation with no setup.

Works with Claude, ChatGPT, Gemini, Mistral, Copilot, Cursor, and other LLM tools.

Which block should I use?

BlockSizeBest for
Minimal~400 tokensQuick questions, one-off lookups, tight context budgets
Full~1,100 tokensReal implementation work, endpoint discovery, auth, filters, and docs navigation
MCP serverLocal tool accessConnecting Claude Code, Claude Desktop, Cursor, or another MCP client to curated Sportmicro tools
Cursor rulesSmallGiving Cursor project-level Sportmicro integration guidance without installing extra tooling
llms-full.txtMediumLoading a broader machine-readable catalog of docs, sports, and schemas in one fetch
Endpoint indexLargeAuditing coverage, discovering every documented endpoint, and giving an agent full API surface area
OpenAPI specsLarge, varies by sportTool configuration, schema-aware agents, and code generation
llms.txtURL onlyGiving an agent or crawler a structured entry point into the docs

Minimal context

Download minimal context
Sportmicro API Docs

Docs base: https://docs.sportmicro.com
API pattern: each sport has its own base URL, such as https://football.sportmicro.com or https://tennis.sportmicro.com
Auth: Authorization: Bearer {API-KEY}
Responses: JSON
Pagination: offset and limit query params; many endpoints default to 50 results and cap at 50
Language: many endpoints support lang=en
Filters: PostgREST-style query filters such as id=eq.{id}, season_id=eq.{season_id}, league_id=eq.{league_id}, start_time=gte.2026-06-11
Common resources: matches, standings, teams, players, leagues, tournaments, seasons, countries, arenas
WebSockets: wss://{sport}.sportmicro.com/live/{type}?token={api-key}
Docs routes: /docs/{sport}/sportmicro for intro pages and /docs/{sport}/{endpoint} for endpoint pages
OpenAPI specs: https://docs.sportmicro.com/openapi/{sport}.json
Machine-readable index: https://docs.sportmicro.com/llms.txt
Endpoint availability varies by sport.

Full context

Download full context
Sportmicro API Docs

Primary docs: https://docs.sportmicro.com

Each sport has its own REST API base URL:
- https://american-football.sportmicro.com
- https://aussie-rules.sportmicro.com
- https://badminton.sportmicro.com
- https://bandy.sportmicro.com
- https://baseball.sportmicro.com
- https://basketball.sportmicro.com
- https://beach-volleyball.sportmicro.com
- https://cricket.sportmicro.com
- https://darts.sportmicro.com
- https://esports.sportmicro.com
- https://floorball.sportmicro.com
- https://football.sportmicro.com
- https://futsal.sportmicro.com
- https://handball.sportmicro.com
- https://hockey.sportmicro.com
- https://rugby.sportmicro.com
- https://snooker.sportmicro.com
- https://table-tennis.sportmicro.com
- https://tennis.sportmicro.com
- https://volleyball.sportmicro.com
- https://waterpolo.sportmicro.com

Authentication:
- REST requests use Authorization: Bearer {API-KEY}
- WebSockets and SSE-style realtime examples use ?token={api-key}

Request conventions:
- JSON responses
- Offset/limit pagination; many endpoints default to 50 and cap at 50
- lang query parameter for translated output where supported
- PostgREST-style filters such as:
- id=eq.{id}
- season_id=eq.{season_id}
- league_id=eq.{league_id}
- start_time=gte.2026-06-11&start_time=lt.2026-06-12
- or=(home_team_id.eq.{team_id},away_team_id.eq.{team_id})
- select=id,name,start_time
- Docs often include update periods and recommended call frequencies

Common endpoint families across the docs:
- Discovery: classes, countries, leagues, tournaments, seasons, rounds, teams, players, coaches, referees, arenas
- Match data: matches, matches-by-date, matches-live, matches-lineups, matches-statistics, matches-incidents, matches-highlights, matches-weather, matches-tv-channels, matches-graphs
- Competition data: standings, coverage, coverage-live, cup-bracket
- Enrichment: news, media, logos, images
- Odds on supported sports: moneyline, spread, totals, asian-handicaps, over-under, odd-even, correct-score, and related markets
- Realtime on supported sports: /live/{type} websocket streams such as score, time, graph, incident, commentary, or status

Useful docs routes:
- https://docs.sportmicro.com/docs/getting_started
- https://docs.sportmicro.com/docs/authentication
- https://docs.sportmicro.com/docs/football/sportmicro
- https://docs.sportmicro.com/docs/football/matches
- https://docs.sportmicro.com/docs/tennis/sportmicro
- https://docs.sportmicro.com/docs/basketball/sportmicro

Example requests:
- GET https://football.sportmicro.com/matches
- GET https://football.sportmicro.com/matches?id=eq.{id}
- GET https://football.sportmicro.com/teams-by-league?league_id=eq.{league_id}
- GET https://tennis.sportmicro.com/matches?start_time=gte.2026-06-11&start_time=lt.2026-06-12
- GET https://basketball.sportmicro.com/standings?season_id=eq.{season_id}

OpenAPI specs are available per sport at:
https://docs.sportmicro.com/openapi/{sport}.json

Machine-readable index:
https://docs.sportmicro.com/llms.txt

Important: endpoint availability and market coverage vary by sport.

All endpoints

If you want the full Sportmicro endpoint surface, use the generated inventories below. These are built from the docs structure in this repo, so they reflect the endpoints currently documented on the site.

Current generated coverage:

MetricValue
Sports21
Documented endpoints1,047

Use llms.txt for a small curated entry point. Use llms-full.txt for a broader catalog. Use the full text or JSON index when you want an AI tool to see every endpoint across all sports.

Cursor rules

If you use Cursor, you can drop in a pre-written rules file so the editor starts with Sportmicro-specific URL patterns, auth conventions, filters, pagination, realtime URLs, and response-shape assumptions.

MCP server

If your AI client supports the Model Context Protocol, you can connect it to the published Sportmicro MCP package and let the client call curated Sportmicro tools directly.

Vibe coding

If you want ready-to-paste prompts for building apps against the real Sportmicro APIs, use the Vibe Coding guide.

OpenAPI specifications

Import a sport-specific OpenAPI spec into your AI tool, code editor, agent framework, or generator.

These files are large. Use the minimal or full context blocks above for normal Q&A, and reserve the OpenAPI specs for schema-aware tooling and code generation.

SportDocsOpenAPI spec
American FootballDocsJSON
Aussie RulesDocsJSON
BadmintonDocsJSON
BandyDocsJSON
BaseballDocsJSON
BasketballDocsJSON
Beach VolleyballDocsJSON
CricketDocsJSON
DartsDocsJSON
EsportsDocsJSON
FloorballDocsJSON
FootballDocsJSON
FutsalDocsJSON
HandballDocsJSON
HockeyDocsJSON
RugbyDocsJSON
SnookerDocsJSON
Table TennisDocsJSON
TennisDocsJSON
VolleyballDocsJSON
WaterpoloDocsJSON

llms.txt and llms-full.txt

Sportmicro now publishes both a curated machine-readable entry point and a broader expanded catalog:

https://docs.sportmicro.com/llms.txt
https://docs.sportmicro.com/llms-full.txt

Use llms.txt first when you want a short, high-signal map. Use llms-full.txt when you want a larger index of docs, sports, and schema files in one fetch.