Head to head · Current weather · October 2026 research run

Meteomatics Weather API vs Weatherbit API

Weatherbit API scores 52.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security & auth and maintenance & community. 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

  • Agent ergonomics, 80 against 61
  • Security & auth, 54 against 39
  • Maintenance & community, 52 against 11

Watch for

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

Weatherbit API D

Best 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, 66 against 34
  • Schema & documentation, 67 against 41
  • Payments & pricing, 45 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

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.

Payments & pricing Weatherbit API +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.

Weatherbit API 45

No x402, MPP or L402 in the docs, the spec or the pricing page (0). Plan prices are public without a login, with daily quotas and no per-call or overage price. The page showed us pounds only, £40, £179 and £410 a month (10 of 20, re-read on 4 November). A free plan at 50 requests a day and a 21-day Business trial, neither needing a card (20). A person signs up in a browser to get a key (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Maintenance & community Meteomatics Weather API +41

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.

Weatherbit API 11

The latest dated API announcement on the blog is still 1 August 2025 on its RSS feed on 4 November, 460 days before this check. The help articles edited in 2026 and the June 2026 timestamps in the docs' sample responses record no change to the API, so they don't set recency (0 of 30). No dated changelog entry or release falls in the 90 days from 6 August (0 of 20). A public blog for API updates that has gone quiet, a help centre, and email support with a stated three business day response that we did not test (6 of 15). pyweatherbit 2.2.2 on PyPI dates from 14 February 2024 and is the only official SDK (3 of 15). Its repository, cloned on 4 November, has no CI and no commit since 13 February 2024 (2 of 10). 0 + 0 + 6 + 3 + 2 = 11.

Reliability Weatherbit API +32

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.

Weatherbit API 66

Graded as a hosted service. Status page at status.weatherbit.io on UptimeRobot. Its monitors and history load by script from /api/ paths that the status host's robots.txt disallows, so on 4 November we couldn't see which parts of the service it covers, and the 8 October reading of three API monitors came from the same disallowed path and no longer counts. The line is kept at 20 as awarded on 8 October, as sendblue's and visual-crossing's UptimeRobot pages are, until the 15 or 20 reading for such pages is settled (20). The 8 October incident reading came from that path too, so the line takes the no-readable-history score, a limit of our reading and not a finding against Weatherbit (5). Requests per day and per second are published for every plan, 50 and 1 on Free up to 2 million and 150 on Business, re-read on 4 November (15). 429 is documented for both limits, every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and the help centre says to slow down or retry. No Retry-After or backoff schedule was found. Every call is a GET (11 of 15). The pricing table lists 99.5 per cent uptime on paid plans, which the help centre calls best effort, with custom SLAs on request and no published credits (5 of 10). The v2.0 API is generally available (10). 20 + 5 + 15 + 11 + 5 + 10 = 66.

Schema & documentation Weatherbit API +26

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.

Weatherbit API 67

Swagger 2.0 at weatherbit.io/static/swagger.json, version 2.0.0, with 21 GET paths, 37 response models and bodies for 400, 403, 429 and 500. It declares no security definition and lists plain http as a scheme (23 of 25, per the 8 October check, not re-read on 4 November). No llms.txt, which still returned 404 on 4 November, and no Markdown docs found (0). Each endpoint page lists parameters, return fields with types and a quota estimate, and warns against station lookups, but says little on when to pick one endpoint over another (13 of 20). units and lang are enums, 31 enum parameters in all. Location is six optional parameters with none marked required, and include and days carry no constraints in the spec (11 of 15). Request examples in curl, Ruby, Node.js and Python, sample responses and a status table with example bodies. Errors are one free-text string (12 of 15). The path is versioned as /v2.0. The changelog is a blog whose latest API post is still dated 1 August 2025 on its RSS feed on 4 November (8 of 15). 23 + 0 + 13 + 11 + 12 + 8 = 67.

Agent ergonomics Meteomatics Weather API +19

Meteomatics Weather API 80

The parameter list, time range, step and format in the URL size each response (23 of 25). No pagination. Output is bounded by the time range and interval, 10 locations and 10 parameters a query, a timeout option and a choice of JSON, CSV, XML, NetCDF or images (13 of 20). HTTP codes with a plain-text message that says which part of the URL is wrong or what data is available, 206 for partial content, and no machine-readable error key (12 of 20). Every REST call is a read, including the POST forms, so retries are safe; the MCP tool annotations read on 8 October came from a struck request to the server and aren't relied on (20). The default source is the vendor's mix model. A call needs four URL segments and parameter names with units. The Python connector is at 4.0.0 in its repository, and connectors for R, Go, Java, C++, Kotlin and Julia are on GitHub (12 of 15). 23 + 13 + 12 + 20 + 12 = 80.

Weatherbit API 61

This is an API with no MCP server. days and hours cap forecast length and include adds minutely data, alerts or lightning only on request. There is no field selection, and a daily forecast row carries about 40 fields (14 of 25). Date ranges, units, lang and a one-month cap per historical call. No pagination is needed (13 of 20). Five status codes with a JSON error string and no machine-readable code. 204 with an empty body means no data, and 403 covers both a missing key and a plan without access (12 of 20). All 21 endpoints are read-only GETs, safe to retry (15 of 20). Only key and a location are required and units default to metric. One official SDK, pyweatherbit for Python, last released in February 2024 (7 of 15). 14 + 13 + 12 + 15 + 7 = 61.

Security & auth Meteomatics Weather API +15

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.

Weatherbit API 39

One plain key per account on Free, Standard and Plus, up to 10 on Business. It is accepted only as the key query parameter, so it lands in URLs and logs, and the spec lists http beside https (20 less 10, 10 of 30). Read-only data with nothing to approve (15 of 20). Alert titles and descriptions are relayed from meteorological agencies, and the rest is numeric (10 of 15). Quota counters come back in response headers and from /subscription/usage, but no per-call log for the account holder was found in the docs (4 of 15). security.txt still returned 404 on 4 November, and no disclosure policy, bounty or certification was found on the site (0). 10 + 15 + 10 + 4 + 0 = 39.

Score by category

CategoryWeightMeteomatics Weather APIWeatherbit APIEdge
Reliability16%3466Weatherbit API +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4167Weatherbit API +26
Agent ergonomics13%8061Meteomatics Weather API +19
Security & auth14%5439Meteomatics Weather API +15
Payments & pricing10%045Weatherbit API +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5211Meteomatics Weather API +41
Transparency & trust7%6063Weatherbit API +3
Negative events≤1500
TotalE 45.7/100D 52.9/100

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 documentednoyes
llms.txtyesno
Last release2026-11-042025-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 stars78 PyPI/wk

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.

Weatherbit API

A read-only weather API with a Swagger 2.0 spec, quota headers on every response and published per-day and per-second limits for every plan. 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 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

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 52.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), 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.