DOCS

Getting Started

TELOS F1 is a browser-based telemetry analysis platform. No installation required — open the dashboard and start exploring.

1. Select a Grand Prix — choose any round from the 2026 calendar (22 circuits, Bahrain and Saudi Arabia not included this season).
2. Choose a Session — FP1, FP2, FP3, Qualifying, Sprint, or Race.
3. Pick a Driver — select the target driver from the driver selector. Optionally add a reference driver for comparison.
4. Select a Lap — choose any lap from the lap history panel. Star laps to bookmark them.
5. Analyze — explore the telemetry charts, gap delta, sector splits, stint analysis, and X-Mode data.

Telemetry Channels

Each channel is rendered as a time-series or distance-series chart. All channels are synchronized to the same x-axis for direct comparison.

Dashboard Controls

Keyboard Shortcuts

Gap Delta

The gap delta chart shows the time difference between the target and reference driver at each point on the lap. A negative value means the target driver is ahead (faster); a positive value means they are behind.

Gap is calculated using distance-based interpolation — both drivers' telemetry is resampled to a common distance axis, then the time difference is computed at each meter. This is the same method used by F1 pitwall engineers and is significantly more accurate than raw lap-time subtraction, which does not account for where on track time is gained or lost.

X-Mode

X-Mode is a special performance mode deployed by drivers in designated circuit zones to maximize power delivery or aerodynamic efficiency. On the speed trace, X-Mode activation segments are highlighted as purple overlays.

The Lap Insights panel displays the total X-Mode usage percentage for each lap. High X-Mode % typically correlates with lower sector times in activation zones.

Engineer View

Engineer View is a compact, information-dense layout designed for power users who want to see maximum data simultaneously. It reduces padding, compresses panels, and increases chart density.

Toggle via the ENG button in the top-right dashboard controls, or press E on your keyboard. Settings persist across reloads via LocalStorage.

Export

Any selected lap can be exported from the telemetry panel:

• CSV — flat table with all channel values per sample point. Compatible with Excel, Python (pandas), R.
• JSON — structured object with full metadata (session info, driver, lap time, sector splits) and channel arrays.
• Share Image — session summary screenshot via html2canvas, shareable via Web Share API or clipboard.

Data Sources

TELOS sources telemetry from two primary APIs:

Tutorials

Short, task-focused walkthroughs that chain the controls above into real analysis workflows. Click any guide to expand it.

REST API B2B

The TELOS public API gives partners programmatic access to our race data products — championship standings, the season calendar, the current grid, and our differentiating AI race predictions with verified accuracy track record. It powers media widgets, fantasy and betting platforms, and research workflows.

Access is sold on a contract basis. Request a key from the B2B team — once issued, it works against every endpoint below.

Authentication

Every request must carry a valid API key. Keys look like tlk_live_… and are shown to you once at creation — store them securely. Send the key one of two ways:

Recommended — Authorization header

curl "https://telos.connexastudios.com/api/v1/standings?type=drivers&year=2026" \
     -H "Authorization: Bearer tlk_live_xxxxxxxxxxxxxxxxxxxx"

Alternative — X-API-Key header

curl "https://telos.connexastudios.com/api/v1/next-race" \
     -H "X-API-Key: tlk_live_xxxxxxxxxxxxxxxxxxxx"

Rate Limits

Limits are enforced per key on a fixed one-minute window. Your tier is set on your contract. Every response includes the current limit state in its headers.

Exceeding the limit returns 429 rate_limited. Back off until X-RateLimit-Reset, or upgrade your tier for higher throughput.

Responses & Errors

All responses share a consistent envelope. Success returns ok: true with a data payload and a meta block; failure returns ok: false with a machine-readable error code and a human message.

Success

{
  "ok": true,
  "data": [ /* endpoint-specific payload */ ],
  "meta": {
    "api": "telos-v1",
    "generated_at": "2026-06-17T12:00:00+00:00"
  }
}

Error

{
  "ok": false,
  "error": "unauthorized",
  "message": "Missing or invalid API key."
}

Endpoints

Six read-only endpoints. All require authentication. Parameters are optional unless noted; sensible defaults (e.g. the current season) apply.