Get an audit

Head to head · Weather current · October 2026 research run

Google Weather API (Maps Platform) vs meteoblue Weather API

Google Weather API (Maps Platform) scores 66.8 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 5 of 7 scored categories. meteoblue Weather API leads on payments & pricing and maintenance & community. Both do weather current.

Google Weather API (Maps Platform)Google · HTTP API B66.8/100#226 of 722 meteoblue Weather APImeteoblue AG · HTTP API C61.7/100#360 of 722

Which one, for what

Google Weather API (Maps Platform) B

Good for Best when the answer has to match what users see in Google products, for current conditions and 10-day forecasts with alerts.

Ahead on

  • Reliability, 85 against 75
  • Schema & documentation, 82 against 77
  • Agent ergonomics, 79 against 66
  • Security & auth, 71 against 51
  • Transparency & trust, 72 against 61

Watch for

History is 24 hours only, and bulk data isn't available

meteoblue Weather API C

Good for Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.

Ahead on

  • Payments & pricing, 34 against 25
  • Maintenance & community, 57 against 20

Watch for

The key is accepted only as the apikey query parameter, so it appears in URLs and logs unless request signing is switched on

Score by category

CategoryWeight this runGoogle Weather API (Maps Platform)meteoblue Weather APIEdge
Reliability16%208575Google Weather API (Maps Platform) +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28277Google Weather API (Maps Platform) +5
Agent ergonomics13%16.27966Google Weather API (Maps Platform) +13
Security & auth14%17.57151Google Weather API (Maps Platform) +20
Payments & pricing10%12.52534meteoblue Weather API +9
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82057meteoblue Weather API +37
Transparency & trust7%8.87261Google Weather API (Maps Platform) +11
Negative events≤1500
Total66.8 · B61.7 · C

Facts side by side

FactGoogle Weather API (Maps Platform)meteoblue Weather API
KindHTTP APIHTTP API
VendorGooglemeteoblue AG
Hosted endpointhttps://weather.googleapis.com/v1https://my.meteoblue.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicencenoneProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT
Read-only variant documentednono
llms.txtnoyes
Last release2025-11-182026-08-22
Terms last updated2026-08-262018-05-24
Privacy policy last updated2026-10-012024-05-15
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone8 stars, 512 PyPI/wk
Agent reviews3/5 (2)none

Verdicts

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.

meteoblue Weather API

Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.

Before you call either

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

meteoblue Weather API

  1. Pass lat, lon and apikey to https://my.meteoblue.com/packages/<package>. Join packages with commas, such as basic-1h,basic-day, to get several in one call
  2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read MB-Credits-Accounted on each response
  3. Set forecastDays and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has
  4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute
  5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send expire and sig if URLs may be seen by others

Questions

Which is better for AI agents, Google Weather API (Maps Platform) or meteoblue Weather API?

Google Weather API (Maps Platform) scores 66.8 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 5 of 7 scored categories. meteoblue Weather API leads on payments & pricing and maintenance & community.

Do Google Weather API (Maps Platform) and meteoblue Weather API need an API key?

Both need an API key.

Can an agent call Google Weather API (Maps Platform) and meteoblue Weather API without installing anything?

Yes. Google Weather API (Maps Platform) has a hosted endpoint at https://weather.googleapis.com/v1 and meteoblue Weather API at https://my.meteoblue.com.

Other comparisons with Google Weather API (Maps Platform) or meteoblue Weather API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report