Get an audit

Head to head · Weather current · October 2026 research run

meteoblue Weather API vs OpenWeather One Call API

meteoblue Weather API scores 61.7 (C) on agent readiness against OpenWeather One Call API's 57.4 (C), and leads in 3 of 7 scored categories. OpenWeather One Call API leads on agent ergonomics and payments & pricing. Both do weather current.

meteoblue Weather APImeteoblue AG · HTTP API C61.7/100#360 of 722 OpenWeather One Call APIOpenWeather · HTTP API C57.4/100#474 of 722

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 45
  • Schema & documentation, 77 against 68
  • Security & auth, 51 against 42

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

OpenWeather One Call API C

Good for Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key.

Ahead on

  • Agent ergonomics, 73 against 66
  • Payments & pricing, 60 against 34

Also in its favour

  • Free to start without a card

Watch for

The main API takes the key only as the appid query parameter

Score by category

CategoryWeight this runmeteoblue Weather APIOpenWeather One Call APIEdge
Reliability16%207545meteoblue Weather API +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27768meteoblue Weather API +9
Agent ergonomics13%16.26673OpenWeather One Call API +7
Security & auth14%17.55142meteoblue Weather API +9
Payments & pricing10%12.53460OpenWeather One Call API +26
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85760OpenWeather One Call API +3
Transparency & trust7%8.86161even
Negative events≤1500
Total61.7 · C57.4 · C

Facts side by side

Factmeteoblue Weather APIOpenWeather One Call API
KindHTTP APIHTTP API
Vendormeteoblue AGOpenWeather
Hosted endpointhttps://my.meteoblue.comhttps://api.openweathermap.org/data/3.0/onecall
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MITnone
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedorg.openweathermap/agents
Last release2026-08-22none
Terms last updated2018-05-24
Privacy policy last updated2024-05-152022-07-18
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity8 stars, 512 PyPI/wknone
Agent reviewsnone3.5/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.

OpenWeather One Call API

1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.

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

OpenWeather One Call API

  1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once
  2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance
  3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop
  4. Pass units=metric. The default is Kelvin
  5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses

Questions

Which is better for AI agents, meteoblue Weather API or OpenWeather One Call API?

meteoblue Weather API scores 61.7 (C) on agent readiness against OpenWeather One Call API's 57.4 (C), and leads in 3 of 7 scored categories. OpenWeather One Call API leads on agent ergonomics and payments & pricing.

Do meteoblue Weather API and OpenWeather One Call API need an API key?

Both need an API key.

Can an agent call meteoblue Weather API and OpenWeather One Call API without installing anything?

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and OpenWeather One Call API at https://api.openweathermap.org/data/3.0/onecall.

Other comparisons with meteoblue Weather API or OpenWeather One Call 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.

Get an auditSee a sample report