The short answer
OpenWeather is billed per call / freemium tiers. It has a free tier: 1M calls/mo (classic) + 1k One Call calls/day. The paid plans we list start at ~$40/month (Startup).
Plans and prices
| Plan | Price | What it covers |
|---|---|---|
| Free | $0 | 60 calls/min, ~1,000,000 calls/month; current weather, 5-day/3-hour forecast, basic endpoints |
| One Call API 3.0 (pay as you call) | 1,000 calls/day free, then ~0.0012 GBP (~$0.0015) per call | Current, minute (1h), hourly (48h), daily (8d), alerts, historical archive, summaries; per-call billing |
| Startup | ~$40/month | 600 calls/min, 10M calls/month; ~95% availability target, data update every ~2 hours |
| Developer | ~$180/month | 3,000 calls/min, 100M calls/month; 99.5% availability, hourly updates |
| Professional | ~$470/month | 30,000 calls/min, 1B calls/month; 99.5% availability, ~10-min updates |
| Enterprise | from $3,000/month | 100,000 calls/min, 3B calls/month; up to 99.9% availability, dedicated/custom terms |
How OpenWeather bills you
The pricing model is per call / freemium tiers. The most widely adopted weather API, with a huge free tier, the One Call product, and enormous community/tutorial presence. Best suited to: ubiquitous developer weather api.
What to watch for on the bill
- Meaningful uptime (99.5%+) and faster data refresh are gated behind higher paid tiers; Startup targets only ~95%
- Free tier rate limits (60 calls/min, 429 errors) are easy to hit for moderately popular apps
The pricing page we read
Source: https://openweathermap.org/price. Prices change, so confirm there before you commit.
Compare OpenWeather with alternatives
- OpenWeather vs Tomorrow.io pricing
- OpenWeather vs WeatherAPI.com pricing
- OpenWeather vs Open-Meteo pricing
Other weather apis: Tomorrow.io, WeatherAPI.com, Open-Meteo, Visual Crossing, AccuWeather.
Looking at quality rather than price? See the OpenWeather score on APIbenchmarks. Full entry: OpenWeather pricing.