Platform Overview
Understand the main ALT Sports Data product surfaces and choose the right starting point for your workflow.
Platform Overview
ALT Sports Data gives you a few different ways to work with the platform. They are designed to fit different jobs, but they all start with the same ALT Sports Data API credential.
Getting Started
Best first stop for developers and operators who want a clear path from credential to first successful request.
API Reference
Pure interactive endpoint reference with request details, schemas, and a right-side testing panel.
SDKs
Official TypeScript and Python clients for faster integrations.
MCP Server
Give Claude, Cursor, and other AI tools direct access to ALT Sports Data.
Which path should you choose?
Use Getting Started if you want
- a guided first read
- a simple explanation of credentials and testing
- quick examples before deeper platform details
Use API Reference if you want
- a pure route-by-route view
- request and response schemas
- a place to open a route and test it from the right-side panel
Use SDKs if you want
- faster development in TypeScript or Python
- typed clients instead of manual HTTP calls
- a cleaner integration surface for production code
Use MCP Server if you want
- agents to query live sports data
- ALT Sports Data inside Claude, Cursor, or similar tools
- the same credential to work across AI workflows
Coverage examples
The best examples in these docs should look like ALT Sports Data examples:
- upcoming WSL events
- the next BKFC card and available odds
- current-month F1 events
- supported Jai Alai, NLL, and DGPT coverage
That keeps the docs aligned with what makes the platform distinct.