Head to head · Current weather · October 2026 research run

Meteomatics Weather API vs Xweather Weather API

Xweather Weather API scores 68.2 (B) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 5 of 7 scored categories. Both do current weather.

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

Which one, for what

Meteomatics Weather API E

Best for Companies in energy, aviation, insurance and logistics that need many models, long history, polygon and route queries and an SLA, and will buy by contract.

Also in its favour

  • No incidents deducted, where Xweather Weather API loses 3 points for them

Watch for

No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation

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

  • Reliability, 84 against 34
  • Schema & documentation, 83 against 41
  • Payments & pricing, 48 against 0
  • Maintenance & community, 81 against 52
  • Transparency & trust, 69 against 60

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.

Reliability Xweather Weather API +50

Meteomatics Weather API 34

Graded as a hosted service. No status page was found. The site and legal pages link none, meteomatics.statuspage.io redirected to an inactive notice on 8 October, and status.meteomatics.com didn't connect for us on 8 October or 4 November (0), so there is no incident record to read (0). The accounting page gives per-query limits with numbers, 10 locations and 10 parameters a query, 2,000 characters on a GET and a 5-minute cut-off, and says the query count is set by contract. No request rate is published (8 of 15). The error table lists 429 as 'limits of license reached' and 414 with 'try to rewrite'. No Retry-After or backoff guidance was found, and every call is a read. Kept at the earlier partial value (6 of 15). The Service Level Agreement of 7 May 2025 aims for 99 per cent a month on Standard and guarantees 99.5 and 99.9 per cent on Extended and Priority Support, compensated in free months (10). The REST API is generally available; the MCP server is called beta in the vendor's 4 May 2026 guide (10). 0 + 0 + 8 + 6 + 10 + 10 = 34.

Xweather Weather API 84

Graded as a hosted service. Status page at status.xweather.com on Atlassian Statuspage with 21 components, among them API General, Conditions, Forecasts, Alerts, Lightning Endpoints and MCP Server (20). Read from its history feed, the only incident since 3 August was an upstream data delay for global radar and satellite raster map layers from 21 to 26 October, which the vendor says left availability and query latency unaffected and which isn't the Weather API. Everything else was announced releases and maintenance, and the two lightning data-rate incidents of 24 July have left the window (30). Monthly quotas are published, 15,000 and 1,000,000 accesses, but the per-minute limit is given only in response headers and by support (8 of 15). 429 is documented with the codes maxhits_min and maxhits, the OpenAPI file declares Retry-After, seven X-RateLimit-* headers report the remaining allowance, the MCP docs advise exponential backoff, and failed calls are not charged. The API is read-only, so no idempotency keys are needed (13 of 15). The pricing page mentions custom SLA guarantees for enterprise plans, with no SLA document found (3 of 10). The REST API at 1.45.0 and the MCP server at 1.3.0 are generally available (10).

Payments & pricing Xweather Weather API +48

Meteomatics Weather API 0

No x402, MPP or L402 in the docs or the OpenAPI file. The error table lists 402, with no payment protocol behind it (0). The pricing page says prices are based on usage and gives no figure, only a form to talk to sales (0). No free tier or trial is on the site. The general terms let Meteomatics grant a trial through an individual offer (0). A person talks to sales and receives a username and password by email. The MCP server registers OAuth clients by API but still needs that account (0). The pricing page re-read on 4 November still says 'Talk to our experts to learn more about our pricing'. 0 + 0 + 0 + 0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

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.

Schema & documentation Xweather Weather API +42

Meteomatics Weather API 41

No machine-readable contract counts. The Swagger page links only the Swagger UI, which loads its YAML file by script, and neither llms.txt nor any docs page read links the file, so this run doesn't count it; the MCP tool schemas were read on 8 October only by calling the server, a reading this run strikes (0 of 25). llms.txt and llms-full.txt at www.meteomatics.com index the site and the API docs (10). The docs explain each URL segment, option and request type, such as trajectory queries, with no guidance on when not to use them (12 of 20). The core request is a URL grammar of free strings; parameter names carry their unit and the docs give allowed values in prose tables, with no typed schema (4 of 15). Example URLs and responses on every docs page and a table of 17 HTTP codes, with errors returned as plain text (10 of 15). No API version in the path and no API changelog. Product update posts appear every two to three months (5 of 15). 0 + 10 + 12 + 4 + 10 + 5 = 41.

Xweather Weather API 83

OpenAPI 3.2.0 and 3.1.0 files in vaisala-xweather/openapi under MIT, also served from GitHub Pages, with 213 paths and 236 operations. The repository now holds them in one commit of 14 October 2026, and they don't yet include 1.45.0's /roadweather/alerts. The MCP tools' input schemas need a key to list and were not read (25). llms.txt at www.xweather.com/llms.txt indexes the site and docs pages. The docs pages have no Markdown copies (a .md address returns 404), though six agent skills in Markdown cover request building (8 of 10). Every operation and parameter in the OpenAPI file has a description, and the MCP tool pages state each tool's purpose and limits, such as a 24-hour tool marked as not for multi-day forecasts (16 of 20). The file has 9 enums and 10 required parameters among 2,289 parameter uses, and filter, query and sort are free strings with their own grammar (8 of 15). Each operation declares 200, 401, 404, 429 and 500 with examples, and the docs list 16 error codes and the warning codes (13 of 15). Dated, numbered changelogs for the API and the MCP server. The API path carries no version (13 of 15).

Maintenance & community Xweather Weather API +29

Meteomatics Weather API 52

The newest dated API change is the product update of 4 November 2026, which puts trajectory queries live (trajectory-3d and trajectory-4d POST requests with up to 10,000 points), 0 days before this check (30). Two dated entries in the 90 days from 6 August, 24 August and 4 November 2026, and no connector commits in that window, so not three (0). Product update posts on 15 June, 24 August and 4 November 2026, support by email around the clock per the SLA, and a pull request merged on the Python connector on 15 June 2026 (9 of 15). The Python connector's version file reads 4.0.0 from 29 April 2026 with Python 3.9 or later, and the R, Kotlin and Julia connectors were updated in May 2026 (10 of 15). The connector repository has no CI workflow, tests or changelog file (3 of 10). 30 + 0 + 9 + 10 + 3 = 52.

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).

Transparency & trust Xweather Weather API +9

Meteomatics Weather API 60

Closed service under general terms for enterprise customers dated August 2026, published per group company, with Swiss law and the courts at the vendor's seat. The Python connector is MIT (15 of 30). The privacy notice, last updated 20 August 2026, names the Weather API, says technical data and usage logs are kept for 3 months, and names Meteomatics AG as controller. A published Data Processing Agreement covers breach notice, deletion or return at the end of the contract and 30 days' notice of a new sub-processor (22 of 30). No deprecation policy was found. The terms let the vendor change them by posting a new version, and a commit marked as breaking on the Python connector, dated 29 April 2026, deprecates the ecmwf-ens-cluster source with no notice period stated (3 of 20). The privacy notice names nine services with their countries, among them HubSpot, Stripe, Gong and OpenAI. No hosting provider or data location for the API is named (10 of 20). The general terms (August 2026) and privacy notice (latest update 20 August 2026) were re-read on 4 November. 15 + 22 + 3 + 10 = 50.

Xweather Weather API 69

Closed service under Vaisala's group subscription terms, dated 1 January 2023, which set a liability cap of twelve months' fees and ICC arbitration. They are written for annual, invoiced contracts and leave the product's own rules to service descriptions that were not found in public. The OpenAPI files and agent skills are MIT (15 of 30). The privacy policy is the group policy effective 1 June 2020. It covers online services, keeps data for a period it calls reasonable with no figure, and still cites the US Privacy Shield. No DPA was found (12 of 30). The changelog marks deprecations with dates, the API has deprecated and warn_deprecated codes, and the terms promise notice of modifications with a 30-day right to end the contract after a material reduction. No notice period is stated (8 of 20). A data processors page names about 40 processors with a location for each, with a caveat that it may be incomplete (16 of 20).

Score by category

CategoryWeightMeteomatics Weather APIXweather Weather APIEdge
Reliability16%3484Xweather Weather API +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4183Xweather Weather API +42
Agent ergonomics13%8078Meteomatics Weather API +2
Security & auth14%5452Meteomatics Weather API +2
Payments & pricing10%048Xweather Weather API +48
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5281Xweather Weather API +29
Transparency & trust7%6069Xweather Weather API +9
Negative events≤150-3
TotalE 45.7/100B 68.2/100

Facts side by side

FactMeteomatics Weather APIXweather Weather API
KindHTTP APIHTTP API
VendorMeteomatics AGVaisala Oyj
Hosted endpointhttps://api.meteomatics.comhttps://data.api.xweather.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub 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 exposed921
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.xweather/weather
Last release2026-11-042026-10-21
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date given2020-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
Popularity56 stars0 stars, 1.4k npm/wk
Agent reviewsnone3.8/5 (4)

How the scores have moved

Verdicts

Meteomatics Weather API

Meteomatics sells a REST weather API with a published SLA that compensates downtime, ISO 27001 certification and a hosted MCP server in beta. Access needs a sales contract, with no public price, free tier or self-serve signup. No status page was found, its docs link no OpenAPI file, and REST calls authenticate with a username and password.

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

Meteomatics Weather API

  1. Ask the account owner for credentials first. There is no signup, and both the REST API and the MCP server need a Meteomatics account with API access
  2. Build REST URLs as validdatetime/parameters/location/format, for example 2026-10-08T00:00:00Z/t_2m:C/52.52,13.40/json. Parameter names carry their unit after a colon
  3. Keep each query to 10 locations and 10 parameters unless the contract says otherwise, and use POST when a GET URL passes 2,000 characters
  4. Send a trajectory as a POST body of timed points, up to 10,000, to trajectory-3d or trajectory-4d when the location moves
  5. Send credentials or the token in the Authorization header. Avoid the documented access_token query parameter, which puts the token in URLs and logs
  6. Read /user_stats_json before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent

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

Xweather Weather API scores 68.2 (B) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 5 of 7 scored categories.

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

Both take an API key or an OAuth sign-in.

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

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

Other comparisons with Meteomatics 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.