Head to head · Weather current · October 2026 research run

meteoblue Weather API vs Xweather Weather API

Xweather Weather API scores 67.1 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 5 of 7 scored categories. Both do weather current.

Which one, for what

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.

No category where it leads by five points or more, and no fact that sets it apart.

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

Xweather Weather API B

Good 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

  • Schema & documentation, 83 against 77
  • Agent ergonomics, 78 against 66
  • Maintenance & community, 81 against 57
  • Transparency & trust, 68 against 61

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=

Score by category

CategoryWeight this runmeteoblue Weather APIXweather Weather APIEdge
Reliability16%207574meteoblue Weather API +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27783Xweather Weather API +6
Agent ergonomics13%16.26678Xweather Weather API +12
Security & auth14%17.55152Xweather Weather API +1
Payments & pricing10%12.53432meteoblue Weather API +2
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85781Xweather Weather API +24
Transparency & trust7%8.86168Xweather Weather API +7
Negative events≤1500
Total61.7 · C67.1 · B

Facts side by side

Factmeteoblue Weather APIXweather Weather API
KindHTTP APIHTTP API
Vendormeteoblue AGVaisala Oyj
Hosted endpointhttps://my.meteoblue.comhttps://data.api.xweather.com
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MITProprietary service under the General Conditions of Subscription Services of Vaisala Group. The OpenAPI files and the agent skills on GitHub are MIT
Tools exposednone19
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.xweather/weather
Last release2026-08-222026-09-14
Terms last updated2018-05-24couldn't be read
Privacy policy last updated2024-05-152020-06-01
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn'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
Popularity8 stars, 512 PyPI/wk0 stars, 1.4k npm/wk

Verdicts

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.

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

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

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, meteoblue Weather API or Xweather Weather API?

Xweather Weather API scores 67.1 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 5 of 7 scored categories.

Do meteoblue Weather API and Xweather Weather API need an API key?

meteoblue Weather API needs an API key. Xweather Weather API takes an API key or an OAuth sign-in.

Can an agent call meteoblue Weather API and Xweather Weather API without installing anything?

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Xweather Weather API at https://data.api.xweather.com.

Other comparisons with meteoblue Weather API 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.