Open API PricingOpen API Pricing

WeatherAPI.com vs Open-Meteo pricing

Both are in weather apis. WeatherAPI.com is billed per call / monthly tiers; Open-Meteo is billed free non-commercial / per-call commercial. Numbers below are copied from each vendor's pricing page.

WeatherAPI.com vs Open-Meteo pricing side by side
WeatherAPI.comFree tier or trial
Free tier
1M calls/mo (3-day forecast)
Billed
Per call / monthly tiers
Best for
Frictionless freemium weather API
Verified
Jun 27, 2026
Open-MeteoFree tier or trial
Free tier
10k calls/day, no key (non-commercial)
Billed
Free non-commercial / per-call commercial
Best for
Free open-source weather API
Verified
Jun 27, 2026

WeatherAPI.com plans

PlanPriceWhat it covers
Free$0/mo100K calls/month, 3-day forecast, 1 day of history, core APIs.
Starter$7/mo (or $75/yr)3M calls/month, 7-day forecast, past 7 days of history.
Pro+$25/mo (or $270/yr)5M calls/month, 300-day forecast, 365 days of history, bulk requests, Pollen API.
Business$65/mo (or $702/yr)10M calls/month, 300-day forecast, history from Jan 1 2010, bulk requests + IP blocking. Marketed as Most Popular.
EnterpriseCustomCustom call volume, 365-day forecast, full history, SLA and all advanced features.

Source: https://www.weatherapi.com/pricing.aspx

Open-Meteo plans

PlanPriceWhat it covers
Free / Open-Access (non-commercial)$0No API key or account; rate-limited to 600 calls/min, 5,000/hour, 10,000/day (~300k/month). No commercial use, no uptime guarantee.
API Standard$29/mo1M API calls/month, API key + dedicated endpoint, commercial licence, 99.9% uptime target. Includes Forecast, Marine, Air Quality, Geocoding, Elevation, Flood APIs.
API Professional$99/mo5M API calls/month; adds Historical Weather, Ensemble Forecast and Climate Change APIs on top of Standard.
API EnterpriseCustom (contact info@open-meteo.com)50M+ calls/month or custom volume/enterprise contracts; price not published on the pricing page.

Source: https://open-meteo.com/en/pricing

WeatherAPI.com pricing guideOpen-Meteo pricing guideQuality scores on APIbenchmarks →