Get an audit

Head to head · Weather current · October 2026 research run

AccuWeather Core Weather API + MCP vs OpenWeather One Call API

OpenWeather One Call API has a score of 57.4 (C) against AccuWeather Core Weather API + MCP's 48.8 (D). Both do weather current. The largest gap is maintenance & community, 47 points.

AccuWeather Core Weather API + MCPAccuWeather · HTTP API D48.8/100#372 of 452 OpenWeather One Call APIOpenWeather · HTTP API C57.4/100#294 of 452

Which one, for what

Pick AccuWeather Core Weather API + MCP for

  • reliability (+20)

Pick OpenWeather One Call API for

  • schema & documentation (+8)
  • agent ergonomics (+13)
  • payments & pricing (+35)
  • maintenance & community (+47)

Score by category

CategoryWeight this runAccuWeather Core Weather API + MCPOpenWeather One Call APIEdge
Reliability16%206545AccuWeather Core Weather API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26068OpenWeather One Call API +8
Agent ergonomics13%16.26073OpenWeather One Call API +13
Security & auth14%17.53942OpenWeather One Call API +3
Payments & pricing10%12.52560OpenWeather One Call API +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81360OpenWeather One Call API +47
Transparency & trust7%8.86062OpenWeather One Call API +2
Negative events≤1500
Total48.8 · D57.4 · C

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
Licencenonenone
Tools exposed266
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedorg.openweathermap/agents
Last releasenonenone
Popularitynonenone
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

AccuWeather Core Weather API + MCP

Official hosted MCP server, 26 read-only tools, same key as the REST API. Terms forbid using the data to train, validate or otherwise 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. Send Accept-Encoding: gzip and refresh on the Expires header rather than a fixed timer
  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

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.

Get an auditSee a sample report