Google Weather API (Maps Platform) vs Pirate Weather

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.

Pirate Weather

Named model sources and a documented priority order for every field. No SLA, and the terms call it best effort.

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

Pirate Weather

1. Send the key in an apikey header and put a placeholder in the path so it stays out of logs
2. Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
3. Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
4. Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
5. Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day