Head to head · Current weather · October 2026 research run

Meteomatics Weather API vs WeatherAPI.com

WeatherAPI.com scores 66.5 (B) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on security & auth. 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.

Ahead on

  • Security & auth, 54 against 37

Watch for

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

WeatherAPI.com B

Best for Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.

Ahead on

  • Reliability, 80 against 34
  • Schema & documentation, 89 against 41
  • Payments & pricing, 45 against 0
  • Maintenance & community, 60 against 52
  • Transparency & trust, 65 against 60

Also in its favour

  • Free to start without a card

Watch for

Key only in the query string, keys can't be scoped, and no security.txt

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.

Schema & documentation WeatherAPI.com +48

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.

WeatherAPI.com 89

OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though q is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15).

Reliability WeatherAPI.com +46

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.

WeatherAPI.com 80

Status page at status.weatherapi.com on Better Stack, with api.weatherapi.com and the website as components (20). Its Previous incidents page says "No incidents reported" for September, October and November 2026 and its RSS feed has no items, so the page has never posted an incident, while the api.weatherapi.com monitor shows 99.839, 99.920 and 99.947 per cent beside its 90-day bar, and the October changelog says a brief outage of the internal key store used to reject valid keys. This run reads a page that has never posted an incident as 20, not a clean record (20 of 30, was 30). Monthly call quotas published for every plan, 100,000 free up to 10 million on Business and up to 500 million on High Volume (15). A spent quota returns 403 with error code 2007, distinct from auth errors, but there's no 429, Retry-After or backoff guidance (5 of 15). The terms promise 99.9 per cent to High Volume customers with service credits, and the plan table lists uptime per plan (10). Generally available (10). 20 + 20 + 15 + 5 + 10 + 10 = 80.

Payments & pricing WeatherAPI.com +45

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.

WeatherAPI.com 45

No x402, MPP or L402 (0). Plan prices are public, from $7 a month for 3 million calls to High Volume at $1,275 a month for 500 million, but there's no per-call or overage price (10 of 20). Free at 100,000 calls a month with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Security & auth Meteomatics Weather API +17

Meteomatics Weather API 54

REST calls use HTTP Basic with a username and password sent by email, or a token from login.meteomatics.com that lasts 2 hours and is documented as an access_token query parameter. No key rotation or separate keys were found in the docs. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE (S256), refresh tokens and one scope, weather:read (12 of 30, after the 10-point deduction for a secret in the URL). The whole API is read-only and the single OAuth scope is a read scope (15 of 20). Responses are mostly numbers. Aviation bulletins and official alerts carry third-party text, and the MCP guide tells users to check model output, with no guidance on untrusted content (9 of 15). /user_stats and /user_stats_json report query counts against contract limits, and the privacy notice says usage logs are kept for 3 months. No per-call log for the customer was found (5 of 15). ISO 27001 and Cyber Essentials certification on the information security page (re-read 4 November), with a security address for vulnerability reports and a promise to 'respond promptly'. No security.txt (404 on 8 October) and no bug bounty (13 of 20). 12 + 15 + 9 + 5 + 13 = 54.

WeatherAPI.com 37

The key goes only in the key query parameter, so it lands in URLs and logs (20 less 10). Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, but none can be scoped, and Business adds IP blocking (12 of 30). Read-only data (15 of 20). Alerts come from government agencies (10 of 15). Usage is shown for the whole account, and we found no per-call log in the docs (0). No security.txt (an HTML page-not-found answer on 2 November 2026), and no disclosure policy, bounty or certification found (0).

Maintenance & community WeatherAPI.com +8

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.

WeatherAPI.com 60

The changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60.

Transparency & trust WeatherAPI.com +5

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.

WeatherAPI.com 65

Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20).

Score by category

CategoryWeightMeteomatics Weather APIWeatherAPI.comEdge
Reliability16%3480WeatherAPI.com +46
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4189WeatherAPI.com +48
Agent ergonomics13%8080even
Security & auth14%5437Meteomatics Weather API +17
Payments & pricing10%045WeatherAPI.com +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5260WeatherAPI.com +8
Transparency & trust7%6065WeatherAPI.com +5
Negative events≤1500
TotalE 45.7/100B 66.5/100

Facts side by side

FactMeteomatics Weather APIWeatherAPI.com
KindHTTP APIHTTP API
VendorMeteomatics AGWeatherAPI.com (Zoomash Ltd)
Hosted endpointhttps://api.meteomatics.comhttps://api.weatherapi.com/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidFreemium
x402nono
LicenceProprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MITnone
Tools exposed9none
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-04none
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity56 starsnone
Agent reviewsnone3.5/5 (2)

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.

WeatherAPI.com

WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found.

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

WeatherAPI.com

  1. Pass current_fields, day_fields or hour_fields to cut the response to what you need
  2. Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429
  3. Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names
  4. Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms
  5. Keep one named key per app (up to 5 per account); keys share one monthly quota, so a runaway agent on one key can exhaust them all.

Questions

Which is better for AI agents, Meteomatics Weather API or WeatherAPI.com?

WeatherAPI.com scores 66.5 (B) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on security & auth.

Do Meteomatics Weather API and WeatherAPI.com need an API key?

Meteomatics Weather API takes an API key or an OAuth sign-in. WeatherAPI.com needs an API key.

Can an agent call Meteomatics Weather API and WeatherAPI.com without installing anything?

Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and WeatherAPI.com at https://api.weatherapi.com/v1.

Other comparisons with Meteomatics Weather API or WeatherAPI.com

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.