For AI agents

Big Balls Sports Data treats autonomous agents as a first-class audience. Four machine-readable surfaces let an agent (or a tool router on its behalf) discover the API, learn what tools are available, and call them with no human in the loop beyond the initial key issuance.

Discovery surfaces

Quickstart

Get a key, authenticate, and call a tool. Three steps with copy-pasteable shell.

MCP manifest

Tool catalogue at /mcp in tools/list shape. Names, descriptions, JSON Schema inputs.

OpenAPI spec

Static OpenAPI 3.1 spec at /openapi.json. The canonical contract used to generate SDKs.

llms.txt

Discovery file at /llms.txt advertising the machine-readable surfaces and primary endpoints.

Authentication for agents

API keys are issued to humans through the dashboard and shared with the agent. There is no agent-mediated signup, see /docs/authentication. Once shared, the agent authenticates with the bearer token on every request; the gateway does not distinguish agent traffic from human traffic and both count against the same key's quota.

Tool routing

The MCP manifest at /mcp is the integration point for tool routers (ToolRoute and similar). It lists eight primary tools (get_scores, get_odds, get_standings, get_stats, get_events, get_players, list_sports, get_match) with JSON Schema inputs and a one-line description of each response shape. The full endpoint catalogue lives in the OpenAPI spec.