Head to head · Current weather · October 2026 research run

Google Weather API (Maps Platform) vs Pirate Weather

Google Weather API (Maps Platform) scores 71.5 (BB) on agent readiness against Pirate Weather's 67.6 (B), and leads in 5 of 7 scored categories. Pirate Weather leads on maintenance & community. Both do current weather.

Best weather and climate data APIs for AI agents · All 136 weather comparisons

Which one, for what

Google Weather API (Maps Platform) BB

Best 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
  • Security & auth, 73 against 45
  • Payments & pricing, 60 against 45
  • Transparency & trust, 72 against 66

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

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

Pirate Weather B

Best for Agents and apps that want Dark Sky-shaped forecasts, model transparency and deep history on a small budget.

Ahead on

  • Maintenance & community, 80 against 20

Also in its favour

  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

No SLA, and the terms call it best effort

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Pirate Weather +60

Google Weather API (Maps Platform) 20

The last Weather API release note is still the alerts endpoint going GA on 18 November 2025 (page last updated 30 October 2026), 348 days before 1 November. The discovery document's revision 20261028 is a routine regeneration, not a dated change (0). No dated releases in the last 90 days (0). Dated release notes with RSS, plus Google's issue tracker and paid support (10 of 15). Google's Maps Experience agent tools MCP server, which includes weather lookup, is in the registry as com.googleapis.mapstools/mcp, version 1.0.0 of 19 April 2026, unchanged on 1 November. It's a separate product, so partial credit (10 of 15). No package to judge (0). 0 + 0 + 10 + 10 + 0 = 20.

Pirate Weather 80

Version 2.10.3 on 21 October 2026 (30). Four releases in the last 90 days, 2.10.0, 2.10.1 and 2.10.2 between 18 and 23 September and 2.10.3 on 21 October (20). Open issues per the 1 October check, not re-read on 1 November because GitHub's pages refuse our reader. 32 were open then, labelled and triaged, most of them requests for new capabilities or data sources, with two portal bugs marked 'awaiting developer response' since May and a new-account key error (#656) open since 7 July (20 of 25). The hosted MCP server isn't in the official registry, where only a third-party Pipeworx wrapper (0.2.0) appears, and there's no official SDK (0). Dependabot, CodeQL and test workflows on the code repository, with dependency bumps merged on 26 October and 1 November 2026 (10).

Security & auth Google Weather API (Maps Platform) +28

Google Weather API (Maps Platform) 73

Google Cloud API keys can be restricted to the Weather API and to IPs or apps, and rotated. OAuth 2.0 is available but only with the broad cloud-platform scope, which earns 30. The documented examples put the key in the key query parameter, and on 1 November the API answered a made-up ?access_token= with 401 invalid credentials (no credential gives 403 PERMISSION_DENIED), with access_token and key both listed as query parameters in the discovery document. That's one 10 off, however many routes a secret has into the URL, as google-maps-platform reads the same test (20 of 30). Read-only data (15 of 20). Alerts text comes from national agencies (10 of 15). Quotas and usage per API in the Cloud console, but no per-call log documented for Weather (8 of 15). google.com's security.txt is valid to 1 April 2030 and names the vulnerability reward programme, and the Maps Platform trust centre lists ISO/IEC 27001:2022 and 27017, SOC 2 and SOC 3, both read on 1 November. Read as google-maps-platform reads the same trust centre (20). 20 + 15 + 10 + 8 + 20 = 73.

Pirate Weather 45

A plain API key from the Apiable portal. The default is the key as a URL path segment, an apikey header is the documented alternative, and the hosted MCP server takes the key only as a query parameter on its URL, so we deducted 10 (10 of 30). Read-only data, no write actions (15 of 20). Alerts text comes from the issuing agencies (NWS, WMO members, MeteoAlarm), not from the public (10 of 15). Every response carries X-Forecast-API-Calls and the rate-limit headers, and a usage page in the docs reads them, but there's no per-call log (7 of 15). No security.txt (404 on pirateweather.net and docs.pirateweather.net on 1 November) and no SECURITY.md in either repository. CodeQL and Dependabot run on the code repository. No bounty or certification (3 of 20).

Payments & pricing Google Weather API (Maps Platform) +15

Google Weather API (Maps Platform) 60

No x402, MPP or L402 (0). Tiered per-1,000 prices published without login, $0.15 per 1,000 to 100,000 down to $0.038 above 5 million, re-read on 1 November (20). 10,000 free events a month need a project with billing attached, but the Maps Demo Key lets a personal Google account call the Weather API without billing information, within daily limits and for prototyping only, so a trial with no card exists, read as google-maps-platform reads the same key (20). A person signs in to a Google account and accepts terms in a browser before a key exists (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Pirate Weather 45

No x402, MPP or L402 (0). The free tier and the $2 plan are published, but higher plans sit in the Apiable portal, which rendered only with JavaScript on 1 October and whose host answered robots.txt with 403 AccessDenied on 1 November, so we count plan pricing that's partly public (10 of 20). 10,000 calls a month free with no card, per the 30 September check (20). A person has to sign up at pirate-weather.apiable.io and subscribe, and the key can take 20 minutes to go live (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Google Weather API (Maps Platform) +10

Google Weather API (Maps Platform) 85

The Google Maps Platform status dashboard lists Weather API as its own product, one of 37 (20). Its incident feed, re-read on 1 November, has four Maps incidents since 3 August (19 October Routes errors, 23 October reverse geocoding, 25 October address data, 28 September Android SDK crash) and none has ever named Weather API, so a clean record (30). Default quota of 6,000 queries a minute, published in the FAQ and adjustable in the Cloud console, per the 1 October check, not re-read on 1 November (15). No 429, Retry-After or backoff guidance found in the Weather docs (0). Weather API is listed as a Maps Platform Core Service under the SLA (page last modified 28 October 2026), 99.9 per cent monthly uptime with credits of 10 to 50 per cent (10). Current conditions, forecasts, history and alerts are GA, and the minute forecast is Experimental (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.

Pirate Weather 75

Status page at pirateweather.xitoring.io, linked from the home page and the changelog. It rendered only with JavaScript on 1 October and answered our reader with a Cloudflare bot check on 1 November, so the award rests on the 30 September check that it exists (20). The project's own incident reports page, now at docs.pirateweather.net, is readable. In the last 90 days it records one incident, on 27 August 2026, when a cleanup job at the Apiable portal removed about 140 subscriptions and revoked their keys while the API itself stayed up, a partial incident (20). Limits published with numbers, 10,000 calls a month free and 20,000 on the $2 plan, with Ratelimit-Limit, Ratelimit-Remaining and Ratelimit-Reset headers (15). 429 means the monthly quota is spent and the reset header says when it clears, and the docs say to retry a 500. No backoff guidance beyond that, though every call is a GET (10 of 15). The terms say best effort with no warranty, so no SLA (0). Version 2 of the API is the stable default (10).

Transparency & trust Google Weather API (Maps Platform) +6

Google Weather API (Maps Platform) 72

Closed service with Maps Platform terms last modified 26 August 2026, re-read on 1 November (15). Google's privacy policy, the Controller-Controller Data Protection Terms and GDPR, LGPD and Standard Contractual Clauses commitments on the trust centre agree with each other (22 of 30). The terms promise 12 months' notice before discontinuing a service or making a backwards-incompatible API change (20). The trust centre covers compliance frameworks, but we didn't find a Weather or Maps subprocessor list or data locations (8 of 20).

Pirate Weather 66

The API code is AGPL-3.0 and the docs and OpenAPI spec are Apache-2.0. We took 5 off the 30 because the terms say nothing about reusing response data (25 of 30). The privacy notice is a generator template last updated 23 September 2024, with retention 'as long as necessary' and no DPA. It agrees with itself but says little (12 of 30). Version 1 and 2 response shapes are both kept, and the changelog dates every change, but there's no written deprecation policy (10 of 20). The privacy notice names Apiable and Stripe, and the infrastructure blog posts name AWS ECS, Aurora PostgreSQL and Kong, but no data locations are stated (8 of 20).

Score by category

CategoryWeightGoogle Weather API (Maps Platform)Pirate WeatherEdge
Reliability16%8575Google Weather API (Maps Platform) +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8285Pirate Weather +3
Agent ergonomics13%7977Google Weather API (Maps Platform) +2
Security & auth14%7345Google Weather API (Maps Platform) +28
Payments & pricing10%6045Google Weather API (Maps Platform) +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2080Pirate Weather +60
Transparency & trust7%7266Google Weather API (Maps Platform) +6
Negative events≤1500
TotalBB 71.5/100B 67.6/100

Facts side by side

FactGoogle Weather API (Maps Platform)Pirate Weather
KindHTTP APIHTTP API
VendorGooglePirate Weather
Hosted endpointhttps://weather.googleapis.com/v1https://api.pirateweather.net/forecast
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicencenoneApache-2.0 (docs and spec), AGPL-3.0 (API code)
Read-only variant documentednono
llms.txtnono
Last release2025-11-182026-10-21
Terms last updated2026-08-26not read yet
Privacy policy last updated2026-10-01not read yet
Customer content may train modelsyesnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone907 stars
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Pirate Weather higher, the other way from the total score.

ReviewerGoogle Weather API (Maps Platform)Pirate Weather
BuoyAutonomous onboarding tester 2/5 Four human steps and a card before production 3/5 Two steps and a 20-minute wait
ScoutResearch agent 4/5 Cadence and sources stated, history stops at 24 hours 5/5 Every field traced to a named model

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Google Weather API (Maps Platform)

Covered by the Maps Platform SLA, 99.9 per cent with service credits, and no Weather incident on Google's status dashboard. A Maps Demo Key allows prototyping without billing. History is 24 hours only, bulk data isn't available, and there has been no release note since November 2025.

Pirate Weather

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

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

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

Questions

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

Google Weather API (Maps Platform) scores 71.5 (BB) on agent readiness against Pirate Weather's 67.6 (B), and leads in 5 of 7 scored categories. Pirate Weather leads on maintenance & community.

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

Both need an API key.

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

Yes. Google Weather API (Maps Platform) has a hosted endpoint at https://weather.googleapis.com/v1 and Pirate Weather at https://api.pirateweather.net/forecast.

Are Google Weather API (Maps Platform) and Pirate Weather open source?

No open-source release is listed for Google Weather API (Maps Platform). Pirate Weather is open source (Apache-2.0 (docs and spec), AGPL-3.0 (API code)).

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

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.