Head to head · Current weather · October 2026 research run

AccuWeather Core Weather API + MCP vs Meteomatics Weather API

AccuWeather Core Weather API + MCP scores 50.8 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 3 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do current weather.

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

Which one, for what

AccuWeather Core Weather API + MCP D

Best for Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user.

Ahead on

  • Reliability, 75 against 34
  • Schema & documentation, 60 against 41
  • Payments & pricing, 38 against 0

Watch for

Terms forbid using the data to train, validate or otherwise inform any AI system

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 60
  • Security & auth, 54 against 39
  • Maintenance & community, 52 against 3
  • Transparency & trust, 60 against 51

Watch for

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

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.

Maintenance & community Meteomatics Weather API +49

AccuWeather Core Weather API + MCP 3

No release notes or changelog on the portal, re-read on 4 November. The API terms update of 28 April 2026 was the only dated change on 1 October, and a terms date isn't an API change in this run's reading; it is also now 190 days old (0). The MCP server grew from 26 to 27 tools with no dated entry (0). No dated changes in the last 90 days (0). Support through a contact form, with no public changelog or community channel (3 of 15). The official MCP server isn't in the registry, per the 1 October check, and there's no official SDK (0). No package to judge (0). 0 + 0 + 3 + 0 + 0 = 3.

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.

Reliability AccuWeather Core Weather API + MCP +41

AccuWeather Core Weather API + MCP 75

Status page at status.accuweather.com with Enterprise API and Developer Portal API components (20). Its history feed, read in full on 4 November, lists in the 90 days from 6 August intermittent degraded performance with 'our APIs' on 20 August (1 hour 22 minutes) and from 21 to 23 August, the Historical and Lightning APIs on 19 October and MinuteCast on 2 November. All four are degraded performance, three name one or two products, and none reports the API down, so they read as partial and the record is minor incidents only. The 26 August and 23 September entries were announced maintenance with windows (20 of 30). Call quotas published per package, 500 a day on the trial up to 2.4 million a month on Elite, but no per-second limit (15). 429 and 503 are defined in the status code table, and the MCP troubleshooting table says to 'Wait and retry' on 429, with no Retry-After header documented. Every call is a read. Backoff guidance alone (10). No SLA, and the terms cap liability at $100 (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

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.

Payments & pricing AccuWeather Core Weather API + MCP +38

AccuWeather Core Weather API + MCP 38

No x402, MPP or L402 (0). Package prices and per-1,000 overage rates are public, from $2 a month for 15,000 calls with $0.25 per 1,000 over (15 of 20). A 14-day trial at 500 Core Weather calls a day. Neither the FAQ nor llms-full.txt says whether it needs a card, so we gave half (10 of 20, the earlier partial kept). A person signs up in a browser (0). 0 + 15 + 10 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Agent ergonomics Meteomatics Weather API +20

AccuWeather Core Weather API + MCP 60

27 MCP tools covering all 106 Core Weather GET endpoints, with no toolsets or subset option found. REST responses shrink a little with details=false and by choosing the 1, 5, 10 or 15-day endpoint (15 of 25). No field selection or paging (10 of 20). RFC 7807 errors with a trace id and a documented status table (16 of 20). Read-only GETs, and the docs describe the MCP server as read-only (15 of 20). Every weather call needs a location key from a separate search call first, and there's no official SDK (4 of 15). 15 + 10 + 16 + 15 + 4 = 60.

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.

Schema & documentation AccuWeather Core Weather API + MCP +19

AccuWeather Core Weather API + MCP 60

No OpenAPI or other machine-readable contract found. The Core Weather, MinuteCast and Lightning references are drawn from OpenAPI documents, but no page we read links a spec as a download. The MCP tools page lists each tool's arguments, which we couldn't check as JSON Schema without a key. The earlier partial is kept (8 of 25). llms.txt, llms-full.txt and a .md twin for every docs page (10). The MCP tools page says what each tool returns and where coverage stops, such as MinuteCast and Lightning staying on REST (14 of 20). Parameters are documented, mostly location keys, language codes and booleans (10 of 15). Quick-start examples and an 11-row status code table, with RFC 7807 problem bodies carrying type, title, status and trace (13 of 15). Versioned /v1 paths, but no changelog or release notes anywhere on the portal, re-read on 4 November (5 of 15). 8 + 10 + 14 + 10 + 13 + 5 = 60.

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.

Security & auth Meteomatics Weather API +15

AccuWeather Core Weather API + MCP 39

A plain key, sent as a Bearer header on REST. The MCP authentication page documents an apikey URL parameter as the alternative, and the connection guide uses it for Claude and ChatGPT, so we deducted 10. Keys can be rotated on the subscriptions page, with no scopes or IP limits found (12 of 30). Read-only API and a read-only MCP server (17 of 20). Alerts and indices text comes from AccuWeather and national agencies (10 of 15). No per-call log found (0). No security.txt on developer.accuweather.com per the 1 October check, and www.accuweather.com's robots.txt answered Access Denied on 4 November, so its earlier 404 is struck. No disclosure policy, bounty or certification found (0). 12 + 17 + 10 + 0 + 0 = 39.

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.

Score by category

CategoryWeightAccuWeather Core Weather API + MCPMeteomatics Weather APIEdge
Reliability16%7534AccuWeather Core Weather API + MCP +41
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6041AccuWeather Core Weather API + MCP +19
Agent ergonomics13%6080Meteomatics Weather API +20
Security & auth14%3954Meteomatics Weather API +15
Payments & pricing10%380AccuWeather Core Weather API + MCP +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%352Meteomatics Weather API +49
Transparency & trust7%5160Meteomatics Weather API +9
Negative events≤1500
TotalD 50.8/100E 45.7/100

Facts side by side

FactAccuWeather Core Weather API + MCPMeteomatics Weather API
KindHTTP APIHTTP API
VendorAccuWeatherMeteomatics AG
Hosted endpointhttps://dataservice.accuweather.comhttps://api.meteomatics.com
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT
Tools exposed279
Read-only variant documentedyesno
llms.txtyesyes
Last releasenone2026-11-04
Terms last updated2026-04-28no date given
Privacy policy last updatedcouldn't be readno 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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone56 stars
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

AccuWeather Core Weather API + MCP

An official hosted MCP server exposes all 106 Core Weather GET endpoints as 27 read-only tools on the same key as the REST API, and the status page shows only partial incidents since August. There is no changelog, the terms allow API changes without notice, and they forbid using the data to train or inform any AI system.

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.

Before you call either

AccuWeather Core Weather API + MCP

  1. Cache location keys. They don't change, and the lookup is the call worth saving
  2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns
  3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs
  4. On 429 wait and retry. On the trial it usually means the 500-call daily allowance is spent until it resets
  5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

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

Questions

Which is better for AI agents, AccuWeather Core Weather API + MCP or Meteomatics Weather API?

AccuWeather Core Weather API + MCP scores 50.8 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 3 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security & auth, maintenance & community and transparency & trust.

Do AccuWeather Core Weather API + MCP and Meteomatics Weather API need an API key?

AccuWeather Core Weather API + MCP needs an API key. Meteomatics Weather API takes an API key or an OAuth sign-in.

Can an agent call AccuWeather Core Weather API + MCP and Meteomatics Weather API without installing anything?

Yes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and Meteomatics Weather API at https://api.meteomatics.com.

Other comparisons with AccuWeather Core Weather API + MCP or Meteomatics Weather 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.