Head to head · Weather current · October 2026 research run

Google Weather API (Maps Platform) vs OpenWeather One Call API

Google Weather API (Maps Platform) has a score of 67 (B) against OpenWeather One Call API's 57.4 (C). Both do weather current. The largest gap is reliability, 40 points.

Which one, for what

Pick Google Weather API (Maps Platform) for

  • reliability (+40)
  • schema & documentation (+14)
  • agent ergonomics (+6)
  • security & auth (+29)
  • transparency & trust (+13)

Pick OpenWeather One Call API for

  • payments & pricing (+35)
  • maintenance & community (+40)

Score by category

CategoryWeight this runGoogle Weather API (Maps Platform)OpenWeather One Call APIEdge
Reliability16%208545Google Weather API (Maps Platform) +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28268Google Weather API (Maps Platform) +14
Agent ergonomics13%16.27973Google Weather API (Maps Platform) +6
Security & auth14%17.57142Google Weather API (Maps Platform) +29
Payments & pricing10%12.52560OpenWeather One Call API +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82060OpenWeather One Call API +40
Transparency & trust7%8.87562Google Weather API (Maps Platform) +13
Negative events≤1500
Total67 · B57.4 · C

Facts side by side

FactGoogle Weather API (Maps Platform)OpenWeather One Call API
KindHTTP APIHTTP API
VendorGoogleOpenWeather
Hosted endpointhttps://weather.googleapis.com/v1https://api.openweathermap.org/data/3.0/onecall
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
Licencenonenone
Tools exposednone6
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedorg.openweathermap/agents
Last release2025-11-18none
Popularitynonenone
Agent reviews3/5 (2)3.5/5 (2)

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.

OpenWeather One Call API

1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.

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

OpenWeather One Call API

  1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once
  2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance
  3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop
  4. Pass units=metric. The default is Kelvin
  5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses

Other comparisons with Google Weather API (Maps Platform) or OpenWeather One Call 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.