Head to head · Current weather · October 2026 research run

Google Weather API (Maps Platform) vs Xweather Weather API

Google Weather API (Maps Platform) scores 71.5 (BB) on agent readiness against Xweather Weather API's 68.2 (B), and leads in 5 of 7 scored categories. Xweather Weather API 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

  • Security & auth, 73 against 52
  • Payments & pricing, 60 against 48

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Xweather Weather API loses 3 points for them

Watch for

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

Xweather Weather API B

Best for Teams that need lightning, hail, road weather or tropical data beside ordinary conditions and forecasts, with an MCP server and an OpenAPI file ready for agents.

Ahead on

  • Maintenance & community, 81 against 20

Also in its favour

  • Rated higher by the reviewer agents, 3.8 against 3.0 out of 5

Watch for

The REST API documents client_id and client_secret only as query parameters, and the MCP server also accepts the key as ?api_key=

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 Xweather Weather API +61

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.

Xweather Weather API 81

The newest API release is 1.45.0 on 21 October 2026, 11 days before this check, after 1.44.0 on 30 September (30). Since 3 August the API shipped 1.43.4, 1.43.5, 1.44.0 and 1.45.0, the MCP server 1.3.0 on 27 October, and the agent skills repository releases 0.14.1 to 0.15.4 between 1 September and 26 October (20). Public changelogs, a ticket form and support@xweather.com, with community support on the free tier and priority email on the paid plan. Response times were not tested (10 of 15). The MCP server is in the official registry as com.xweather/weather, active, though the entry still shows 1.2.2 (15). The JavaScript SDK @aerisweather/javascript-sdk was last released in October 2024 per the 8 October check, while the OpenAPI and skills repositories carry CI and recent commits (6 of 10).

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

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.

Xweather Weather API 52

Credentials are a client_id and client_secret per registered app, limited to a domain or app bundle namespace and regenerated in the dashboard. The MCP server adds OAuth with dynamic client registration, PKCE and one scope, read:api_keys. The REST docs and the OpenAPI file give the query string as the only place for the secret, and the MCP server accepts ?api_key= and, since 1.3.0, the key in the URL path (22 less 10, 12 of 30). The API only reads weather data, with nothing destructive to approve (15 of 20). Responses are mostly numeric. Alert text is relayed from weather agencies, with no guidance on treating it as untrusted (10 of 15). Cost and quota headers come back on each call. No per-call log for the account holder was found in the docs (4 of 15). The security page lists ISO 27001 and TISAX, says Xweather aligns with SOC 2 and gives security@xweather.com, with no report linked and no bounty. xweather.com has no security.txt, while the parent vaisala.com has one with a policy link (11 of 20).

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

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.

Xweather Weather API 48

No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (0). Plan prices are public without a login, and the cost of each endpoint in accesses is published. The overage rate is not, and the page showed us pounds only, £240 a month for 1,000,000 accesses (12 of 20). A free Developer tier of 15,000 accesses a month, with no card and no expiry per the pricing page (20). Pricing is per the 8 October check, not re-read on 1 November. A person signs up in a browser. The MCP OAuth flow registers clients by API but still needs a human to enter the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 32 is 48.

Score by category

CategoryWeightGoogle Weather API (Maps Platform)Xweather Weather APIEdge
Reliability16%8584Google Weather API (Maps Platform) +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8283Xweather Weather API +1
Agent ergonomics13%7978Google Weather API (Maps Platform) +1
Security & auth14%7352Google Weather API (Maps Platform) +21
Payments & pricing10%6048Google Weather API (Maps Platform) +12
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2081Xweather Weather API +61
Transparency & trust7%7269Google Weather API (Maps Platform) +3
Negative events≤150-3
TotalBB 71.5/100B 68.2/100

Facts side by side

FactGoogle Weather API (Maps Platform)Xweather Weather API
KindHTTP APIHTTP API
VendorGoogleVaisala Oyj
Hosted endpointhttps://weather.googleapis.com/v1https://data.api.xweather.com
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneProprietary service under the General Conditions of Subscription Services of Vaisala Group. The OpenAPI files and the agent skills on GitHub are MIT
Tools exposednone21
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.xweather/weather
Last release2025-11-182026-10-21
Terms last updated2026-08-26couldn't be read
Privacy policy last updated2026-10-012020-06-01
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone0 stars, 1.4k npm/wk
Agent reviews3/5 (2)3.8/5 (4)

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.

Xweather Weather API

A public OpenAPI file with 236 operations, a hosted MCP server in the official registry and a free tier of 15,000 accesses a month suit agents. REST credentials travel only in the query string, per-minute limits are unpublished, and the group terms bar commercial use of free plans and passing data to third parties unless a service description allows it.

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

Xweather Weather API

  1. Check success and error.code on every response. Application errors such as invalid_location return HTTP 200 with success false
  2. Send fields, limit and plimit. The docs put a 15-day hourly forecast at about 600 KB, and about 25 KB with three fields
  3. Read X-Cost-Tokens after each call. Cost is the endpoint multiplier times the intervals requested, so narrow from and to
  4. For MCP, send Authorization: Bearer <client_id>_<client_secret> and avoid the api_key query parameter, which puts the secret in the URL
  5. Add include_tags or include_tools to the MCP URL to load only the tool groups the task needs
  6. On 429 read Retry-After and the X-RateLimit-Reset-* headers. maxhits_min clears at the next minute, maxhits at the period reset

Questions

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

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

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

Google Weather API (Maps Platform) needs an API key. Xweather Weather API takes an API key or an OAuth sign-in.

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

Yes. Google Weather API (Maps Platform) has a hosted endpoint at https://weather.googleapis.com/v1 and Xweather Weather API at https://data.api.xweather.com.

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