Datapit reads the real data of your account with the official GPRO API and suggests setup, strategy, driver and car plans, and the season's accounts. It does not play for you: the token is read-only and you make the choices, in the game. It is not a simulator: every calculation is checked against real races, external calculators or the GPRO wiki, and when a number is an estimate the page says so.
Q1, Q2 and race with the setup formula: your driver, your car as it is today and the weather of each session.
Compound, stops, fuel and boost laps; the highest «Clear track» risk without running out of energy or breaking parts.
Training and tests race by race, for the following seasons too, with the Overall cap and the contract renewal.
Wear race by race to the end of the season, part changes, Power, Handling and Acceleration against the tracks.
Real income and costs from the statement and the forecast cash race by race.
Your races one by one, the lap times, the rankings and the driver market.
Datapit reads with the official GPRO API what you see in the game: office, driver, car, track and weather of the next race, practice, testing, group, statement and calendar. Every answer stays saved: the pages open at once and do not change until you press «Update».
It is at the top of every page, with the date of the oldest data and the calls you have left today. It checks what has changed in the game and downloads only that; if a race has finished, it logs it in the archive. Then it goes back to the page you were on and tells you what it updated and how many calls it used.
Every logged race saves the setup used, result, stops, tyre and fuel consumption, lap-by-lap weather, risks, the driver and car of that day and the replay of the whole group's race. The more races there are, the more the calculations use your numbers instead of general ones: the stops from one of your stints on the same track, the wear of the tracks you have already raced, the energy margin of your races.
GPRO does not publish its formulas, and Datapit is not the game engine. Every calculation is checked against real races, external calculators or the GPRO wiki; where an estimate remains the page says so, often with how far off it can be.
Every reading of your data is a call to the GPRO API, and each token has a quota of calls per race (1000 for GPRO Supporters, 100 for everyone else): you can see how many you have left at the top, next to “Update”. You don't have to count them: Datapit keeps every answer and shows the saved ones until you press “Update”, which re-downloads only what changed in the game.
| What | Calls | When |
|---|---|---|
| The first time | up to 14 | With nothing saved, the Summary or the Race weekend download the week's data (up to 9 calls), and the Summary, once only, the list of your races (1); the Car plan and the Economy add 4 (garage, statement, calendar and tracks). After that it does not happen again. |
| «Update» | 1 to about 14 | At the top of every page. One call to see what changed in the game, then it re-downloads only that: if nothing changed it costs 1. When a race is over it also records the race in the archive (result, setup, consumption and lap-by-lap replay) and moves on to the new race: that is the time it costs the most, about 14. The button says how many you have left, and if they could drop below 20 it asks you to confirm. |
| «Past races» | 1 per race | In History: the races you drove before Datapit, to put in the archive all together or only the ones you choose. Those unlocked on GPRO arrive complete, the others with the result only. It always leaves 30 calls for playing and after the next race you pick up from there. |
| «Download missing races» | 3 per race | In the Rankings: your division, the Italians and your group. If nothing is missing it costs 1 call; the other divisions cost 1 call per race, only if you open and download them. |
| Always free | 0 | Reloading a page (F5), moving from one page to another, changing the choices in the plans; Test sessions, Driver plan, History and Lap times only read the saved data; the Drivers market is a public file that does not use the quota. |
The rhythm that saves calls: do a batch of things in the game, then a single «Update». Datapit downloads only what has changed.
In the GPRO app (app.gpro.net) open Miscellaneous > API access and copy the token.
In «Sign in» paste the token. Then open the Summary: the first time it downloads the week's data (up to 10 calls) and tells you whether you have past races to put in the archive.
Wait for the race to finish and for GPRO to publish the results.
«Update»: logs the race in the archive and moves on to the new race. Do it before the next race: the lap-by-lap replay can be downloaded in full only for the last race.
Do the driver training, repairs and part changes as you decided.
Decide here first, without calls: the Driver plan for training and tests, the Car plan for the parts, the Economy to see whether the cash holds.
Do the test sessions. The driver comments on the setup only with the «Setup tuning» test priority.
After «Update» you find them in Test sessions, with the points that will reach the car.
Do the practice laps starting from the setup of the Race weekend.
«Update», then in the Race weekend read the driver's comments on each part of the setup and correct it.
Q1 and Q2, each with its own setup: they have different weather.
Race weekend, Setup section: one setup for Q1, one for Q2 and one for the race.
Race setup, fuel, tyres, risks and boost laps, before the choices close.
Race weekend, Race section: compound, stops, litres, risks and boost. «Update» downloads the weather forecast again if it is more than half an hour old.
The menu has four groups: Week, Season, Archive and Market. Open a page below to learn what it shows, how to use it, how far to trust the numbers and how many calls it costs.
The starting page. It is only for reading: it gathers in one place what you need to know before the race.
Warnings appear at the top when needed: past races to put in the archive, a driver change during the week, the end of the season.
It follows the order of the weekend, in four parts; the numbers at the top take you straight to each one.
How far to trust it: on the tracks the formula knows, the setup is off by at most 2.4 points against an external calculator. The stops come from a real stint of yours on the same track when there is one, otherwise from a tyre formula calibrated on your races (typical error 5% on the length). The most uncertain part is the pit time. The recommended strategy is saved until the start, to compare it later with the real race.
The driver judges the setup only with the «Setup tuning» test priority: with the others you keep the values tried, without a verdict. The stints save themselves when you open the Summary or the Race weekend during a test session.
It helps you grow the driver without going over your category's Overall cap, and know in advance what happens at the end of the season.
The training effects are measured on real trainings; for those never seen, every logged race measures their effect. The Overall formula is an estimate found online, not the official one. The plan saves itself, and the Car plan (tests) and the Economy (costs and prizes) use it too.
How far to trust it: wear follows GPRO's mechanism (typical track wear × level and risk × driver). Typical wear comes from your races on the tracks already raced, otherwise from a per-track table (average error of about 2.4 points on real races), and for the few tracks outside the table from a regression on your races. How many test points become car points is an estimate. The PHA alignment is not a GPRO rule: it is a way to measure with a number that the car goes better when it resembles the track. The plan saves itself.
The real accounts come from the GPRO statement; the forecast is an estimate that changes with your plans. At the start of a season, while there are fewer than 3 races, the averages also use the last ones of the previous season.
Like the Staff and Facilities page in the game, but with the costs level by level and an estimate: write the levels you would like to take the facilities to and see what they cost and how maintenance would change. Nothing is saved and nothing is changed in the game.
How far to trust it: levels, caps and prices are the game's. Maintenance is an estimate ($5,000 per level). How much a level is worth is not known: no source says, so there is no value ranking.
From Pro upwards the tyre supplier is chosen with the contract at the start of the season (in Rookie and Amateur everyone has Pipirelli). Here you pick a supplier from the list and see what changes compared with yours.
How far to trust it: durability follows the tyre formula, checked on your races also across different seasons; peak, dry and wet are measured on the results of thousands of Pro, Master and Elite managers (dry is the least certain); the compound pace per supplier comes from an external calculator. For the season the temperature of a track is an estimate from your races.
A race goes into the archive by itself: open the Summary or the Race weekend before the start (so the recommended strategy is saved too) and, once the race is over, press «Update». From here you also open Recommended strategy versus actual and Past races.
For each race with the strategy saved it compares the forecast with the real race:
It opens from the History or from the Summary's notice. It lists all the races you have run on GPRO, season by season, and says which are already in the archive. Tick the ones you want, one by one or a whole season, and press «Download the ticked races».
GPRO does not publish a time per track: here are the real laps of your driver with your car, from the archive. A record, not a forecast. For each track:
GPRO gives a maximum number of rows per list: in the biggest divisions you get the fastest managers, not all of them.