Formula 1 data for agents and applications

REST API v2

Every public REST operation is a synchronous GET under /api/v2. GET requests are idempotent, public reads require no credentials, and the OpenAPI document defines unique operation IDs, parameters, response schemas, and typed JSON errors.

Base URL

https://api.racecalendar.app

OpenAPI

https://api.racecalendar.app/api/v2/openapi.json

Authentication

None for documented public reads

Version policy

Major version in the /api/v2 path

Model Context Protocol

The canonical MCP endpoint uses stateless Streamable HTTP and exposes the same read-only facts through tools, resources, prompts, completion, and an optional race-weekend dashboard for hosts that support MCP Apps.

Endpoint

https://racecalendar.app/mcp

Server card

https://racecalendar.app/.well-known/mcp/server-card.json

Authentication

Anonymous and read-only

App resource

ui://racecalendar/race-weekend-dashboard.html

Reliability and errors

Public reads are cache-friendly and complete synchronously; this API has no long-running job workflow. Invalid or unavailable REST resources return typed JSON errors. Bounded MCP data cache misses can return HTTP 429 with Retry-After; clients should preserve that delay instead of retrying immediately.

Machine-readable discovery

Start with the agent instructions for usage boundaries, then use the catalogs for protocol-specific metadata and canonical endpoints.

• Agent instructions and when-to-use guidance
• Agentic resource catalog
• RFC 9727 API catalog
• Agent Skills index
• Agent-readable site guide
• Public access and authentication policy