Stormglass API vs Visual Crossing Weather API

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.

Visual Crossing Weather API

History from 1970, current conditions and a 15-day forecast from one endpoint. Key only in the query string on the REST API.

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

Visual Crossing Weather API

1. Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records
2. Count records before a backfill. Hourly data is 24 records a day, so a year for one place is 8,760
3. Pass unitGroup=metric. The default is US units
4. Use the MCP server with X-VC-API-Key rather than pasting the key into a URL
5. Keep to one request at a time on Free and Professional. A second concurrent job returns 429