Head to head · Weather forecasts · October 2026 research run

Stormglass API vs Xweather Weather API

Xweather Weather API scores 67.1 (B) on agent readiness against Stormglass API's 39.9 (E), and leads in every scored category. Both do weather forecasts.

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

Which one, for what

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Xweather Weather API B

Good for Teams that need lightning, hail, road weather or tropical data beside ordinary conditions and forecasts, with an MCP server and an OpenAPI file ready for agents.

Ahead on

  • Reliability, 74 against 34
  • Schema & documentation, 83 against 40
  • Agent ergonomics, 78 against 65
  • Security & auth, 52 against 44
  • Payments & pricing, 32 against 25
  • Maintenance & community, 81 against 15
  • Transparency & trust, 68 against 45

Watch for

The REST API documents client_id and client_secret only as query parameters, and the MCP server also accepts the key as ?api_key=

Score by category

CategoryWeight this runStormglass APIXweather Weather APIEdge
Reliability16%203474Xweather Weather API +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24083Xweather Weather API +43
Agent ergonomics13%16.26578Xweather Weather API +13
Security & auth14%17.54452Xweather Weather API +8
Payments & pricing10%12.52532Xweather Weather API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81581Xweather Weather API +66
Transparency & trust7%8.84568Xweather Weather API +23
Negative events≤1500
Total39.9 · E67.1 · B

Facts side by side

FactStormglass APIXweather Weather API
KindHTTP APIHTTP API
VendorStorm Glass ABVaisala Oyj
Hosted endpointhttps://api.stormglass.io/v2https://data.api.xweather.com
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Storm Glass AB's Terms and Conditions. The Free and Small plans are not for commercial useProprietary service under the General Conditions of Subscription Services of Vaisala Group. The OpenAPI files and the agent skills on GitHub are MIT
Tools exposednone19
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.xweather/weather
Last release2026-02-262026-09-14
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date given2020-06-01
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularitynone0 stars, 1.4k npm/wk

Verdicts

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.

Xweather Weather API

A public OpenAPI file with 236 operations, a hosted MCP server in the official registry and a free tier of 15,000 accesses a month suit agents. REST credentials travel only in the query string, per-minute limits are unpublished, and the group terms bar commercial use of free plans and passing data to third parties unless a service description allows it.

Before you call either

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

Xweather Weather API

  1. Check success and error.code on every response. Application errors such as invalid_location return HTTP 200 with success false
  2. Send fields, limit and plimit. The docs put a 15-day hourly forecast at about 600 KB, and about 25 KB with three fields
  3. Read X-Cost-Tokens after each call. Cost is the endpoint multiplier times the intervals requested, so narrow from and to
  4. For MCP, send Authorization: Bearer <client_id>_<client_secret> and avoid the api_key query parameter, which puts the secret in the URL
  5. Add include_tags or include_tools to the MCP URL to load only the tool groups the task needs
  6. On 429 read Retry-After and the X-RateLimit-Reset-* headers. maxhits_min clears at the next minute, maxhits at the period reset

Questions

Which is better for AI agents, Stormglass API or Xweather Weather API?

Xweather Weather API scores 67.1 (B) on agent readiness against Stormglass API's 39.9 (E), and leads in every scored category.

Do Stormglass API and Xweather Weather API need an API key?

Stormglass API needs an API key. Xweather Weather API takes an API key or an OAuth sign-in.

Can an agent call Stormglass API and Xweather Weather API without installing anything?

Yes. Stormglass API has a hosted endpoint at https://api.stormglass.io/v2 and Xweather Weather API at https://data.api.xweather.com.

Other comparisons with Stormglass API or Xweather 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.