Get an audit

Head to head · Weather forecasts · October 2026 research run

AccuWeather Core Weather API + MCP vs Stormglass API

AccuWeather Core Weather API + MCP scores 48.4 (D) on agent readiness against Stormglass API's 39.9 (E), and leads in 3 of 7 scored categories. Stormglass API leads on agent ergonomics and security & auth. Both do weather forecasts.

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

AccuWeather Core Weather API + MCPAccuWeather · HTTP API D48.4/100#814 of 950 Stormglass APIStorm Glass AB · HTTP API E39.9/100#914 of 950

Which one, for what

AccuWeather Core Weather API + MCP D

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

Ahead on

  • Reliability, 65 against 34
  • Schema & documentation, 60 against 40
  • Transparency & trust, 55 against 45

Watch for

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

Stormglass API E

Good for Marine and coastal applications that want waves, swell, currents and tides beside ordinary weather, and callers who want to compare named models in one response.

Ahead on

  • Agent ergonomics, 65 against 60
  • Security & auth, 44 against 39

Watch for

No OpenAPI file, llms.txt, official SDK or changelog was found. The docs are eleven Markdown pages

Score by category

CategoryWeight this runAccuWeather Core Weather API + MCPStormglass APIEdge
Reliability16%206534AccuWeather Core Weather API + MCP +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26040AccuWeather Core Weather API + MCP +20
Agent ergonomics13%16.26065Stormglass API +5
Security & auth14%17.53944Stormglass API +5
Payments & pricing10%12.52525even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81315Stormglass API +2
Transparency & trust7%8.85545AccuWeather Core Weather API + MCP +10
Negative events≤1500
Total48.4 · D39.9 · E

Facts side by side

FactAccuWeather Core Weather API + MCPStormglass API
KindHTTP APIHTTP API
VendorAccuWeatherStorm Glass AB
Hosted endpointhttps://dataservice.accuweather.comhttps://api.stormglass.io/v2
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under Storm Glass AB's Terms and Conditions. The Free and Small plans are not for commercial use
Tools exposed26none
Read-only variant documentedyesno
llms.txtyesno
Last releasenone2026-02-26
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 noticeyesyes
Arbitration or class-action waivernot found in the textyes
Agent reviews2.5/5 (2)none

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.

Stormglass API

A read-only weather and marine API with about 70 hourly parameters, per-source values from named national models, tide data and ERA5 history from 2014. No OpenAPI file, status page, SDK or security page was found, the free plan allows 10 requests a day, and the docs and FAQ disagree on the status code for a spent quota.

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

Stormglass API

  1. Send the key as Authorization: KEY with no Bearer prefix. A missing or wrong key returns 403 with {"errors":{"key":"API key is invalid"}}
  2. Always pass source=sg or a short source list on /weather/point. The default is every source, which multiplies the size of each hourly record
  3. Treat 402 as a spent daily quota, not a billing failure, and stop until the next day. Read meta.requestCount against meta.dailyQuota on each response
  4. Use /historical/point for past dates, at most 10 days a call and nothing newer than about 7 days. /weather/point looks back 14 days only
  5. Send and read all times in UTC. Tide sea levels are relative to the chosen datum (MSL by default) and are not water depth

Questions

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

AccuWeather Core Weather API + MCP scores 48.4 (D) on agent readiness against Stormglass API's 39.9 (E), and leads in 3 of 7 scored categories. Stormglass API leads on agent ergonomics and security & auth.

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

Both need an API key.

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

Yes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and Stormglass API at https://api.stormglass.io/v2.

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