Google Weather API (Maps Platform) vs WeatherAPI.com

Google Weather API (Maps Platform)

Covered by the Maps Platform SLA, 99.9 per cent with service credits. History is 24 hours only, and bulk data isn't available.

WeatherAPI.com

3 million calls for $7 a month, and 100,000 a month free with no card. Key only in the query string, and no security.txt.

Google Weather API (Maps Platform)

1. Ask for only the days or hours you need, one location a call. Every call is one billable event
2. Page with pageSize and pageToken rather than asking for 240 hours at once
3. Check the coverage page before promising alerts. Coverage is by country
4. Refetch rather than cache. The Maps terms give no caching window for weather content
5. Restrict the key to the Weather API and your server IPs in the Cloud console

WeatherAPI.com

1. Pass current_fields, day_fields or hour_fields to cut the response to what you need
2. Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429
3. Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names
4. Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms
5. Use https://api.weatherapi.com/v1. The docs still show an http:// base URL