Czechia coverage is live at 4 km
Raná, Beskydy, Krkonoše, Kozákov, Doubrava, Javorový - Czech soaring at 4 km, four cycles a day, forecast fields as JSON.
Czechia is the country in this batch that is least obviously a soaring forecast problem and most actually one. The Alps justify themselves. Anyone glancing at a topo map can see why a 13 km global model fails over a Tirol valley. Czechia looks easier - mid-elevation, broad ridges, plenty of flatland - which is exactly why most pilots flying it are stuck with global-model output that gets the convergence and ridge-lift detail completely wrong.
As of today the Convek API serves a 4 km forecast over the whole country. Raná, the Beskydy ridges along the Slovak border, the Krkonoše, Kozákov, Doubrava, Javorový, and every coordinate across Bohemia and Moravia. Same live fields as Switzerland, Slovenia and Austria, four cycles a day, forecast values as JSON.
The country is also the proof point that Convek is not only an Alpine product. Czech XC is competitive at European level - the records out of Raná routinely hit the high hundreds of kilometres - and the underlying meteorology is exactly the kind of mid-elevation flatland-and-ridge mix that benefits enormously from going from 13 km to 4 km. Convergence lines along the main highland boundaries, ridge lift on the Krušné Hory, the warm-sector flow patterns that drive long Moravian XC days - all of it sharpens up at the higher resolution.
For Czech tasks specifically, the corridor endpoint is the one to know about. `/v1/corridor` in time-aware mode samples forecast fields along an actual track rather than at fixed waypoints, with the forecast hour advancing as the track does. Long flat Czech XC tasks that thread between airspace and convergence lines are the use case it was designed for, and they are awkward to forecast any other way.
On runtime, Czechia sits between Slovenia and Austria - end-to-end about 19 minutes per cycle. That is comfortably inside the four-daily schedule, with the 06z forecast published well before a 09:00 launch decision. Cadence and horizon are the standard 00z / 06z / 12z / 18z, 49 hours, hourly.
The domain rectangle covers 11.4 E to 19.6 E and 48.0 N to 51.6 N, buffered into Germany, Poland, Slovakia and Austria. Bohemia, Moravia, the Krkonoše, the Beskydy and the Šumava are all in the clean interior. Day-window and sounding labels use `Europe/Prague`, so the local-clock fields agree with what your variometer thinks the time is.
As ever, the only Czechia-specific code is the rectangle, the timezone, and a per-country Better Stack heartbeat. Same WRF-ARW build, same physics, same GFS initial conditions as everywhere else. The benchmark ran clean. The scheduled cycles since have run clean.
Czechia closes out the first European batch. After this, the country sequence pauses for a planned push on validation - five countries running four times a day is plenty of rectangles for one summer, and the next priority is being able to score those forecasts against radiosondes and pilot reports rather than just publishing them. Spain is benchmarked and on the runway for a later release, where its longer runtime can have its own scheduler slot without crowding out the rest.
Free tier is the usual 25 queries a day, no card. `region=cz` and a `lat` / `lon` to `/v1/site` is the whole API call. The Czechia coverage page has the coordinate box and field list, and the API docs have everything else. If you fly Czech XC, run a club, or are building Czech-pilot-facing tools, this is the feed.