Free / open data
Jolpica-F1
Volunteer-run open source Formula 1 API with endpoints backward compatible with the retiring Ergast service, free to use and funded by donations.
Facts verified against the provider's site on
Tone of public discussions, liked vs criticised points, reliability complaints; not enough public discussion to judge.
Computed from public data only; uptime and latency are not measured yet. Enterprise feeds that sell by contract score lower on transparency by design. How the score works
- Starting price
- Not public
- Free access
- Free tier
- Sports
- 2 (Formula 1, Motorsport)
- Live data
- Not disclosed
- Delivery
- Polling only (REST)
- Discussions
- 2 threads
- GitHub adoption
- 1.6k repos
Best for
Formula 1 projects, especially ones migrating from the retired Ergast API, that need free historical results and standings.
Not ideal for
Commercial products needing guarantees: it is volunteer-run, rate-limited and the licence does not address the data.
Limitations to check
- − Free and rate-limited; limit values not stated
- − Volunteer-run and donation funded
- − Apache-2.0 licence covers the code, not the data
Written from the provider's own pages (source).
Last checked 2026-11-03
Jolpica-F1 at a glance
- What is Jolpica-F1 best for?
- Formula 1 projects, especially ones migrating from the retired Ergast API, that need free historical results and standings. Not ideal for: Commercial products needing guarantees: it is volunteer-run, rate-limited and the licence does not address the data.
- How much does Jolpica-F1 cost?
- Jolpica-F1 does not publish prices on the pages we checked.
- Does Jolpica-F1 have a free tier?
- Yes. Jolpica-F1 lists a free plan called "Free".
- What does Jolpica-F1 cover?
- Jolpica-F1 is a free / open data. Its sports: Formula 1, Motorsport; data: Fixtures, Historical data, Results, Standings, Team stats.
- Does Jolpica-F1 have a WebSocket or streaming API?
- No streaming is listed. Jolpica-F1 delivers data by REST, so you poll for updates.
- What do developers say about Jolpica-F1?
- Free, volunteer-run Formula 1 API that took over from the retired Ergast service with compatible endpoints. Widely adopted: roughly thirty GitHub repos, popular F1 data-visualisation posts, and projects that integrate it for historical results and standings. Little explicit praise or criticism in discussion; no pricing or reliability complaints surfaced.
- What are the alternatives to Jolpica-F1?
- Close alternatives in the SportDex catalog: OpenF1, Football Charts, CollegeBasketballData.com, FastF1, StatPal.
Commercial decision
Pricing & plan limits
| Plan | Price | Requests | What's included |
|---|---|---|---|
| Free | Free | — | Free and rate-limited; maintainers ask for donations (hosting about $45/month)source |
Ergast-compatible base http://api.jolpi.ca/ergast/f1 per README. Rate limit values not captured.
Before choosing a paid plan, confirm
• What counts as one request (per call, per market, per region?)
• What happens when you exceed the quota: blocked or billed
• Whether live and historical data are on your plan
• Whether your use (public app, betting, resale) is licensed
The critical question
Data coverage
- Sports
- Formula 1Motorsport
- Data types
- FixturesHistorical dataResultsStandingsTeam stats
- Key competitions
- Formula 1
- Competitions
- Not disclosed
- Live / in-play
- Not disclosed
- Women's competitions
- Not disclosed
- Betting markets
- Not disclosed
- Bookmaker regions
- Not disclosed
- Bookmakers
- Not disclosed
- History depth
- Not disclosed
- Update frequency
- Not disclosed
- Name languages
- Not disclosed
- ID mapping
- Not disclosed
Coverage often depends on the plan; confirm the exact league and season on your plan.
Before you build
Usage rights & access
- Commercial use
- Not disclosed
- Betting products
- Not disclosed
- Redistribution
- Not disclosed
- Storing data
- Not disclosed
- Attribution
- Not disclosed
- Logos & photos
- Not disclosed
- Who can buy
- Individualssource
- Verification (KYC)
- Not required
- Not available in
- Not disclosed
- Only available in
- Not disclosed
Developer-ready evaluation
Integration & documentation
- Protocols
- REST
- Formats
- JSON
- Authentication
- none
- SDKs
- Not disclosed
- OpenAPI spec
- Not disclosed
- Claimed latency
- Not disclosed
- Status page
- Not disclosed
- Sandbox / test keys
- Not disclosed
- Support
- Not disclosed
- SLA uptime
- Not disclosed
Preview brief
# Integration brief: Jolpica-F1 Goal: build a feature on Jolpica-F1 data. Use only the official documentation below as the source of truth. ## Known facts (from SportDex, verify before relying on them) - Website: https://github.com/jolpica/jolpica-f1 - Docs: https://github.com/jolpica/jolpica-f1 - Sports: Formula 1, Motorsport - Data: Fixtures, Historical data, Results, Standings, Team stats - Protocols: REST; formats: json - Auth: none - Free plan: Free - Note: Ergast-compatible base http://api.jolpi.ca/ergast/f1 per README. Rate limit values not captured. ## Verify before writing code - live update frequency - whether commercial use is allowed on the plan you pick - exact endpoint paths, parameters and response fields (read the official docs, do not guess) ## Implementation rules - Keep the API key on the server (environment variable, backend route or edge function); never ship it to the browser. - Cache responses and respect rate limits; count how many requests each screen triggers. - Handle errors explicitly: invalid key, quota exceeded (429), missing fields, empty fixtures, timeouts. - Start with one demo request and log the raw response before building UI on assumed field names.
Data quality signals
Data source & company
- Official partners
- Not disclosed
- How data is collected
- community
- Certifications
- Not disclosed
- Payment methods
- Not disclosed
- Minimum contract
- Not disclosed
- Country
- Not disclosed
- Founded
- Not disclosed
Reddit · Hacker News · Stack Overflow · GitHub · YouTube
What developers say
Free, volunteer-run Formula 1 API that took over from the retired Ergast service with compatible endpoints. Widely adopted: roughly thirty GitHub repos, popular F1 data-visualisation posts, and projects that integrate it for historical results and standings. Little explicit praise or criticism in discussion; no pricing or reliability complaints surfaced.
Praised for
- Free and donation funded
- Ergast-compatible endpoints
- Broad adoption in open-source F1 tools
Complaints
Nothing specific.
Our summary of public discussions, not a rating. Vendor posts are not counted as user opinion.
Discussions
- Norris is a particular bad starter: the numbersr/formula1 · 2025-10
- Main Race Finished Positions heatmap so far in 2026.r/formula1 · 2026-10
Open-source projects using it
Shortlist next steps
Alternatives worth comparing

Open-source API for Formula 1 session data: lap times, car telemetry, positions, pit stops, weather, team radio and race control. Historical data from 2023 is free without auth; live access is a paid sponsorship.
Free tier⚡ StreamingFormula 1Motorsportfrom €9.90/mo10 discussions · 675 repos
Daily-updated football results, tables, goal timing, model probabilities and season projections for 98 leagues via JSON REST and an MCP server; open CC BY dataset and paid history tiers.
Free tierFootball (soccer)from €9/mo1 discussions · 14 repos
College basketball data service with a free personal API key, CSV exporter, analytics tools and a paid historical starter pack; sister project of the CFBD football API.
Free tierBasketballCollege sportsfrom $1/mo1 discussions · 42 repos
Unofficial Python library giving free access to Formula 1 lap timing, car telemetry, tyre, weather, schedules and session results as Pandas DataFrames. Most data now needs an F1TV subscription.
Free tierFormula 1MotorsportFree tier10 discussions · 118 repos
Sports data API for live scores, odds, news and match storylines across 12+ sports and 1,000+ soccer leagues. Two flat monthly plans with a 14-day trial and an OpenAPI schema.
14-day trialLiveFootball (soccer)American footballBasketball+5from $29/mo1 discussions · 0 repos
Evidence & transparency
Official sources
Facts were extracted from the provider's own pages on 2026-11-03. Empty fields mean the provider does not say, not that the feature is missing. How we know