Get an audit

Head to head · Weather data · October 2026 research run

meteoblue Weather API vs Open-Meteo

Open-Meteo scores 63.4 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 4 of 7 scored categories. meteoblue Weather API leads on reliability and security & auth. Both do weather data.

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

Best data provider APIs for AI agents · All 31 data comparisons

meteoblue Weather APImeteoblue AG · HTTP API C61.7/100#460 of 950 Open-MeteoOpen-Meteo · HTTP API B63.4/100#394 of 950

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.

Ahead on

  • Reliability, 75 against 50
  • Security & auth, 51 against 38

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

Open-Meteo B

Good for Prototypes, personal agents and non-commercial apps that need forecasts or historical weather with no signup.

Ahead on

  • Agent ergonomics, 85 against 66
  • Payments & pricing, 50 against 34
  • Maintenance & community, 90 against 57
  • Transparency & trust, 72 against 61

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Commercial prices appear only at Stripe checkout

Score by category

CategoryWeight this runmeteoblue Weather APIOpen-MeteoEdge
Reliability16%207550meteoblue Weather API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27777even
Agent ergonomics13%16.26685Open-Meteo +19
Security & auth14%17.55138meteoblue Weather API +13
Payments & pricing10%12.53450Open-Meteo +16
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85790Open-Meteo +33
Transparency & trust7%8.86172Open-Meteo +11
Negative events≤1500
Total61.7 · C63.4 · B

Facts side by side

Factmeteoblue Weather APIOpen-Meteo
KindHTTP APIHTTP API
Vendormeteoblue AGOpen-Meteo
Hosted endpointhttps://my.meteoblue.comhttps://api.open-meteo.com/v1/forecast
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreemiumFreemium
x402nono
LicenceProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MITAGPL-3.0 (code), CC BY 4.0 (data)
Read-only variant documentednono
llms.txtyesno
Last release2026-08-222026-09-10
Terms last updated2018-05-24no date given
Privacy policy last updated2024-05-15no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity8 stars, 512 PyPI/wk6.2k stars
Agent reviewsnone4/5 (2)

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.

Open-Meteo

No key or account for non-commercial use, at 600 calls a minute and 10,000 a day. Commercial prices appear only at Stripe checkout.

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

Open-Meteo

  1. Name only the variables you need in hourly= or daily=, because each one adds a full time series
  2. Credit 'Weather data by Open-Meteo.com' wherever you show the data
  3. Use customer-api.open-meteo.com with &apikey= for anything commercial, and keep that URL out of logs
  4. Read reason on a 400. It names the bad parameter
  5. Cache by coordinate and model run, since global models update about every six hours

Questions

Which is better for AI agents, meteoblue Weather API or Open-Meteo?

Open-Meteo scores 63.4 (B) on agent readiness against meteoblue Weather API's 61.7 (C), and leads in 4 of 7 scored categories. meteoblue Weather API leads on reliability and security & auth.

Do meteoblue Weather API and Open-Meteo need an API key?

meteoblue Weather API needs an API key. Open-Meteo needs no key.

Can an agent call meteoblue Weather API and Open-Meteo without installing anything?

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Open-Meteo at https://api.open-meteo.com/v1/forecast.

Are meteoblue Weather API and Open-Meteo open source?

No open-source release is listed for meteoblue Weather API. Open-Meteo is open source (AGPL-3.0 (code), CC BY 4.0 (data)).

Other comparisons with meteoblue Weather API or Open-Meteo

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