Head to head · Current weather · October 2026 research run

AccuWeather Core Weather API + MCP vs OpenWeather One Call API

OpenWeather One Call API scores 59.2 (C) on agent readiness against AccuWeather Core Weather API + MCP's 50.8 (D), and leads in 6 of 7 scored categories. AccuWeather Core Weather API + MCP leads on reliability. 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 45

Watch for

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

OpenWeather One Call API C

Best 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

  • Schema & documentation, 68 against 60
  • Agent ergonomics, 73 against 60
  • Payments & pricing, 90 against 38
  • Maintenance & community, 40 against 3
  • Transparency & trust, 59 against 51

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

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

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 OpenWeather One Call API +52

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.

OpenWeather One Call API 90

No x402, MPP or L402. The agent lane's top-ups are card only and need a person (0). Per-call prices published without login, $0.0015 a call on One Call by Call and $0.001 a call on the agent lane (20). The agent lane gives every account 1,000 One Call credits a day with only an email (20). POST an email to agents.openweathermap.org/v1/accounts and the data key comes back in the response (20). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community OpenWeather One Call API +37

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.

OpenWeather One Call API 40

The newest dated release is the MCP server's version 0.3.0, published to the official registry on 4 September 2026, 61 days before this check (20). In the 90 days from 6 August, MCP 0.2.0 and 0.3.0 on 4 September and the agent terms revision of 23 September, which isn't a release. Two releases, short of the three the line needs, and no dated API changelog (0). No public changelog for One Call. Support is through the help desk, which we didn't test (5 of 15). The MCP server is in the official registry as org.openweathermap/agents, a domain-verified namespace (15). No package to judge (0). 20 + 0 + 5 + 15 + 0 = 40.

Reliability AccuWeather Core Weather API + MCP +30

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.

OpenWeather One Call API 45

No public status page found, and status.openweathermap.org doesn't resolve (0). No incident history to read (5). Limits published with numbers, 1,000 One Call calls a day free, a default cap of 2,000 a day you can change, and 60 a minute on the Free plan (15). 429 is documented as quota exceeded, and the agent lane says its 429 names the interval to wait. All calls are GETs (10 of 15). The subscription table publishes uptime of 95 to 99.9 per cent for the Startup to Expert plans, but nothing for One Call by Call (5 of 10). One Call 4.0 is the current version (10). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

Agent ergonomics OpenWeather One Call API +13

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.

OpenWeather One Call API 73

exclude drops current, minutely, hourly, daily or alerts blocks on 3.0, and 4.0 splits the timeline by step (1 minute, 15 minutes, hour, day). The MCP server has six tools (20 of 25). 4.0 takes a start parameter to page through timelines (16 of 20). Error bodies carry a code and message, and the agent lane's errors.json gives each code with its HTTP status and the reaction to take (18 of 20). Read-only GETs, and the agent lane bills only 2xx responses. We didn't see MCP annotations (14 of 20). Three required parameters, but units defaults to Kelvin and there's no official SDK (5 of 15). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

Schema & documentation OpenWeather One Call API +8

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.

OpenWeather One Call API 68

No OpenAPI for the main REST API. The agent lane links an openapi.yaml and an errors.json dictionary, which we couldn't parse, so partial credit (12 of 25). llms.txt on openweathermap.org and on the agent lane, with a Markdown guide and llms-full.txt (10). Each response field is described, and the 3.0 page tells new integrations to use 4.0 (14 of 20). exclude and units values are listed in the docs, not in a contract (10 of 15). JSON examples for every endpoint, and errors documented as 400, 401, 404, 429 and 5xx with a cod, message and parameters body (15). Versioned paths, but no public changelog and no date for retiring 3.0 (7 of 15). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

Transparency & trust OpenWeather One Call API +8

AccuWeather Core Weather API + MCP 51

Closed service with API terms last updated 28 April 2026, re-read on 4 November (15). The API terms let AccuWeather collect, store and use request data such as locations and IP addresses and point to the privacy policy on www.accuweather.com. That host's robots.txt answered Access Denied on 4 November, so the 1 October reading of the privacy policy (retention tied to the account) is struck. No DPA found. The terms clause partly meets the line, so the earlier partial is kept (12 of 30). The terms say AccuWeather 'may change the APIs at any time without notice' (0). The provider list and the United States processing statement came from the privacy policy and are struck (0 of 20). 15 + 12 + 0 + 0 = 27.

OpenWeather One Call API 59

Closed service. The terms of sale, re-read on 4 November 2026 at their new address, still put products and services under CC BY-SA 4.0 and the data under ODbL (18 of 30). The privacy policy, last updated 18 July 2022, says API request parameters, IPs and user agents aren't collected or stored and keeps customer records six years. The agent lane runs under a second company, Extreme Electronics Ltd, with its own terms, and we found no DPA (18 of 30). 3.0 is marked deprecated with no date (5 of 20). Google Analytics and group companies in Latvia and the USA are named for transfers (12 of 20). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

Score by category

CategoryWeightAccuWeather Core Weather API + MCPOpenWeather One Call APIEdge
Reliability16%7545AccuWeather Core Weather API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6068OpenWeather One Call API +8
Agent ergonomics13%6073OpenWeather One Call API +13
Security & auth14%3942OpenWeather One Call API +3
Payments & pricing10%3890OpenWeather One Call API +52
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%340OpenWeather One Call API +37
Transparency & trust7%5159OpenWeather One Call API +8
Negative events≤1500
TotalD 50.8/100C 59.2/100

Facts side by side

FactAccuWeather Core Weather API + MCPOpenWeather One Call API
KindHTTP APIHTTP API
VendorAccuWeatherOpenWeather
Hosted endpointhttps://dataservice.accuweather.comhttps://api.openweathermap.org/data/3.0/onecall
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Tools exposed276
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedorg.openweathermap/agents
Terms last updated2026-04-28not read yet
Privacy policy last updatedcouldn't be read2022-07-18
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate OpenWeather One Call API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

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

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

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, AccuWeather Core Weather API + MCP or OpenWeather One Call API?

OpenWeather One Call API scores 59.2 (C) on agent readiness against AccuWeather Core Weather API + MCP's 50.8 (D), and leads in 6 of 7 scored categories. AccuWeather Core Weather API + MCP leads on reliability.

Do AccuWeather Core Weather API + MCP and OpenWeather One Call API need an API key?

Both need an API key.

Can an agent call AccuWeather Core Weather API + MCP and OpenWeather One Call API without installing anything?

Yes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and OpenWeather One Call API at https://api.openweathermap.org/data/3.0/onecall.

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