OpenF1 API

Name: OpenF1 API
Brand: OpenF1 API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData Transformationnone13 EndpointsREST

For Agents

Pull live and historical Formula 1 telemetry, lap times, pit stops, race-control messages, and weather across 13 endpoints from a free public REST API.

Install Jentic One Beta

Connect the OpenF1 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenF1 API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with OpenF1 API.

Stream car telemetry samples (speed, RPM, gear, throttle, brake) via /car_data with session and driver filters

Retrieve lap times and lap-by-lap data through /laps for any session and driver

Track gaps between cars during a session via /intervals at high refresh

GET STARTED

Start building with OpenF1 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use OpenF1 API for, with concrete tasks.

★ Race-Day Companion App

Build a second-screen race companion app that shows live laps, intervals, pit stops, and race-control messages while a Formula 1 session is underway. OpenF1 streams the data through query-filtered REST endpoints; the app polls /laps and /intervals every few seconds and renders a live timing tower without negotiating a commercial timing-data licence.

Call /laps?session_key=9999&driver_number=44 and return the most recent lap time and sector breakdown for the driver.

Strategy Reconstruction

Reconstruct a team's race strategy from /pit, /stints, /laps, and /race_control. Useful for analyst content ("what if Mercedes had pitted on lap 18?") and for engineering students learning tyre and stint modelling. Historical sessions are indexed with stable session_key and meeting_key values so notebooks can be re-run reliably.

For session_key 9472, fetch /stints and group by driver_number to list compound and lap span for each stint.

Telemetry Visualisation

Visualise raw telemetry — throttle, brake, RPM, speed, gear — via /car_data filtered by session and driver. Used by content creators and engineering tutorials to overlay driver inputs through a single corner. Sample rates are high enough for frame-by-frame charts without ingesting full broadcast feeds.

Call /car_data?session_key=9472&driver_number=1 with a date filter for one minute around lap 12 and chart speed over time.

Agent-Driven F1 Q&A

An AI agent answering Formula 1 questions can use Jentic to discover the right OpenF1 endpoint for a query like "what was Verstappen's fastest lap in Bahrain 2024?". Jentic returns /laps with the input schema; the agent chooses the session_key and driver_number, sorts the response by lap_duration, and returns the answer grounded in the API.

Through Jentic, find the operation for "laps in a session" and call it with the resolved session_key and driver_number, returning the minimum lap_duration.

Key Endpoints

13 endpoints — openf1 is a free rest api that exposes real-time and historical formula 1 data including car telemetry, driver and team metadata, lap times, intervals, pit stops, race-control messages, sessions, stints, team radio, and weather.

METHOD

PATH

DESCRIPTION

GET

/sessions

List F1 sessions filtered by meeting, year, or type

GET

/meetings

List Grand Prix weekends

GET

/drivers

List drivers participating in a session

GET

/laps

Get lap times and sector data

GET

/intervals

Gaps between cars during a session

GET

/pit

Pit-stop events

GET

/car_data

Per-car telemetry samples

GET

/race_control

Race-control messages

GET

/sessions

List F1 sessions filtered by meeting, year, or type

GET

/meetings

List Grand Prix weekends

GET

/drivers

List drivers participating in a session

GET

/laps

Get lap times and sector data

GET

/intervals

Gaps between cars during a session

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OpenF1 is unauthenticated, so no credentials are stored. Jentic still proxies the call so the agent's integration pattern (search, load, execute) is uniform with authenticated APIs.

Intent-based discovery

Agents query Jentic with intents like "lap times in an F1 session" or "pit stops in a Grand Prix" and receive the matching OpenF1 operation with its session_key, driver_number, and date filters typed correctly.

Time to first call

Direct OpenF1 integration: half a day to learn session_key and meeting_key resolution. Through Jentic: under 15 minutes.

FAQs

Specific to using OpenF1 API through Jentic.

What authentication does the OpenF1 API use?

OpenF1 is fully unauthenticated — no API key, OAuth token, or signed request is required. Jentic still routes the request through MAXsystem so observability and retry behaviour match authenticated APIs and the integration is forward-compatible if OpenF1 adds keys later.

Can I get live timing data with the OpenF1 API?

Yes. /intervals and /laps return data within a few seconds of the live broadcast feed during sessions, and /position tracks running order in real time. Poll with the session_key for the active session and a date filter for the most recent samples.

What are the rate limits for the OpenF1 API?

OpenF1 publishes guidance to be reasonable with polling — there is no hard documented limit but heavy real-time consumers should aggregate filters (session_key plus a tight date range) rather than scanning the dataset, and back off on HTTP 429 if returned.

How do I find the session_key for a specific Grand Prix through Jentic?

Use the Jentic search query "list F1 sessions for a Grand Prix". Jentic returns /sessions with its query schema; the agent supplies meeting_key (resolved from /meetings by year and country) and reads the resulting session_key values. Sign up at https://app.jentic.com/sign-up.

Is the OpenF1 API free to use?

Yes. OpenF1 is a free public service. The project accepts donations but does not charge for API access at any tier.

Can the OpenF1 API stream telemetry as WebSocket?

No. OpenF1 is REST-only — clients poll the relevant endpoint with a date filter to get recent samples. For low-latency consumers, narrow the time window and increase polling frequency rather than expecting a push channel.