Head to head · Weather current · October 2026 research run

Meteomatics Weather API vs Weatherbit API

Weatherbit API scores 57.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security & auth and maintenance & community. Both do weather current.

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

  • Agent ergonomics, 80 against 61
  • Security & auth, 54 against 39
  • Maintenance & community, 42 against 21

Watch for

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

Weatherbit API C

Good for An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.

Ahead on

  • Reliability, 91 against 34
  • Payments & pricing, 30 against 0

Also in its favour

  • Free to start without a card

Watch for

The key is accepted only as the key query parameter, and the spec lists plain http as a scheme

Score by category

CategoryWeight this runMeteomatics Weather APIWeatherbit APIEdge
Reliability16%203491Weatherbit API +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27172Weatherbit API +1
Agent ergonomics13%16.28061Meteomatics Weather API +19
Security & auth14%17.55439Meteomatics Weather API +15
Payments & pricing10%12.5030Weatherbit API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84221Meteomatics Weather API +21
Transparency & trust7%8.85963Weatherbit API +4
Negative events≤1500
Total49.6 · D57.7 · C

Facts side by side

FactMeteomatics Weather APIWeatherbit API
KindHTTP APIHTTP API
VendorMeteomatics AGWeatherbit LLC
Hosted endpointhttps://api.meteomatics.comhttps://api.weatherbit.io/v2.0
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidFreemium
x402nono
LicenceProprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MITProprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT
Tools exposed9none
Read-only variant documentednono
llms.txtyesno
Last release2026-08-242025-08-01
Terms last updatedno date given2025-05-01
Privacy policy last updatedno date given2023-12-26
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
Popularity56 stars, 16k PyPI/wk78 PyPI/wk

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.

Weatherbit API

A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.

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

Weatherbit API

  1. Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution
  2. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then
  3. Treat HTTP 204 with an empty body as no data found, not as an error
  4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
  5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0

Questions

Which is better for AI agents, Meteomatics Weather API or Weatherbit API?

Weatherbit API scores 57.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security & auth and maintenance & community.

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

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

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

Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and Weatherbit API at https://api.weatherbit.io/v2.0.

Other comparisons with Meteomatics Weather API or Weatherbit 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.