Get an audit

Head to head · Weather current · October 2026 research run

Meteomatics Weather API vs WeatherAPI.com

WeatherAPI.com scores 65.3 (B) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on security & auth. Both do weather current.

Meteomatics Weather APIMeteomatics AG · HTTP API D49.6/100#606 of 722 WeatherAPI.comWeatherAPI.com (Zoomash Ltd) · HTTP API B65.3/100#260 of 722

Which one, for what

Meteomatics Weather API D

Good 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

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

Ahead on

  • Reliability, 90 against 34
  • Schema & documentation, 89 against 71
  • Payments & pricing, 30 against 0
  • Transparency & trust, 65 against 59

Also in its favour

  • Free to start without a card

Watch for

Key only in the query string, and no security.txt

Score by category

CategoryWeight this runMeteomatics Weather APIWeatherAPI.comEdge
Reliability16%203490WeatherAPI.com +56
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27189WeatherAPI.com +18
Agent ergonomics13%16.28080even
Security & auth14%17.55437Meteomatics Weather API +17
Payments & pricing10%12.5030WeatherAPI.com +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84245WeatherAPI.com +3
Transparency & trust7%8.85965WeatherAPI.com +6
Negative events≤1500
Total49.6 · D65.3 · B

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-08-24none
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 stars, 16k PyPI/wknone
Agent reviewsnone3.5/5 (2)

Verdicts

Meteomatics Weather API

A public OpenAPI file, a hosted MCP server whose nine tools are all marked read-only, a published SLA with compensation and ISO 27001 certification suit company use. Access needs a sales contract, with no public price, free tier or self-serve signup found, no status page, and REST calls that authenticate with a username and password.

WeatherAPI.com

3 million calls for $7 a month, and 100,000 a month free with no card. Key only in the query string, and no security.txt.

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 credentials or the token in the Authorization header. Avoid the documented access_token query parameter, which puts the token in URLs and logs
  5. Read /user_stats_json before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent
  6. Treat reserved values such as -888 and -999 as invalid or missing data, and shrink the request when a 408 arrives after the 300-second timeout

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. Use https://api.weatherapi.com/v1. The docs still show an http:// base URL

Questions

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

WeatherAPI.com scores 65.3 (B) on agent readiness against Meteomatics Weather API's 49.6 (D), 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.

Get an auditSee a sample report