College sports data across seven sports and every division — NCAA D1 (incl. FBS/FCS), D2, D3, NAIA, and NJCAA. Every surface here is designed so an agent can discover, evaluate, and use Magisterial without a human in the loop until it is time to pay.
The condensed, fetchable version of this page: magisterial.ai/llms.txt
The full coverage matrix — teams, players, games, and coaches per sport and division with season ranges — is free and unauthenticated. Confirm we hold what you need before doing anything else.
curl https://api.magisterial.ai/v1/coverage
The complete /v1 reference — auth, scoping, pagination, errors, every endpoint and object shape — is published as a single markdown document that fits in one model context:
https://api.magisterial.ai/v1/llms.txt
Prefer structured specs? OpenAPI 3.1 at /v1/openapi.json — import it, codegen from it, or hand it to a human at /v1/docs.
Keys are self-serve in the console. Free read endpoints run at 120 requests/minute. Test keys (mag_test_) work on every free read endpoint and are blocked from billed ones — development can never create charges. Usage-billed endpoints (portal, query, alerts, exports) sit under a monthly budget cap the account controls; see pricing.
curl "https://api.magisterial.ai/v1/teams?sport=soccer&division=D3&gender=men" \ -H "Authorization: Bearer mag_live_..."
A remote MCP server with OAuth 2.1 for assistants, or an API key as a bearer token for headless clients. Discovery lives at /.well-known/mcp.json; setup guides for Claude, Claude Code, and ChatGPT are on the connectors page.
https://api.magisterial.ai/mcp
Append .md to any key page URL — including every public player and coach profile — and you get the page as plain markdown, a fraction of the tokens of the HTML. Requests that prefer text/markdown in their Accept header get the twin at the human URL. Or flip the Human / Agent toggle in the header to see any page the way an agent does.
https://magisterial.ai/{player-or-coach-slug}.mdTyped Python and TypeScript clients generated from the published spec.
At least 90 days’ notice before any breaking /v1 change, with Deprecation and Sunset headers on affected endpoints. Follow the changelog and the status page.