---
name: racecalendar-f1-discovery
description: Use when discovering public Formula 1 calendars, results, standings, circuit pages, historical archive pages, sitemap inventory, or the Race Calendar public API.
---

# Race Calendar F1 Discovery

Use this skill to find public Formula 1 data exposed by Race Calendar App.

## Discovery Order

1. Read https://racecalendar.app/llms.txt for the machine-readable site guide.
2. Use https://racecalendar.app/sitemap.xml for the exhaustive crawl inventory.
3. Fetch crawlable pages with `Accept: text/markdown` when a compact agent-readable page is preferred.
4. Use https://api.racecalendar.app/api/v2/openapi.json for the public API contract.
5. Use https://racecalendar.app/.well-known/api-catalog for API catalog links and health/status entry points.
6. Use https://racecalendar.app/.well-known/mcp/server-card.json to discover the optional read-only MCP tools.
7. Follow https://racecalendar.app/updates.atom.xml or https://racecalendar.app/updates.json for reviewed reports, finalized results, and material schedule corrections.

## Primary Public Pages

- https://racecalendar.app/f1
- https://racecalendar.app/f1/results
- https://racecalendar.app/f1/winners
- https://racecalendar.app/f1/drivers
- https://racecalendar.app/f1/teams
- https://racecalendar.app/f1/circuits
- https://racecalendar.app/f1/countries
- https://racecalendar.app/f1/history

## Public API Notes

- The public API hostname is https://api.racecalendar.app.
- Read the OpenAPI document before calling endpoints with structured parameters.
- API responses are cache-friendly JSON and do not require authentication for public calendar and archive reads.
- The read-only MCP server is available at https://racecalendar.app/mcp and does not require authentication.
- Read https://racecalendar.app/auth.md before using any account-adjacent route; purchase, referral, account, and admin operations are not public agent tools.
- Prefer linked web pages when an answer needs canonical URLs for indexing or citation.