Met Office Weather DataHub (Site Specific) vs Stormglass API

Met Office Weather DataHub (Site Specific)

Statutory UK weather service, with a FAQ licence to copy, publish and adapt the data. No OpenAPI, llms.txt, SDK or MCP server.

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.

Met Office Weather DataHub (Site Specific)

1. Register an application and subscribe it to the Global Spot plan first. The key is tied to that order and shown once
2. Send the key in the apikey header with Accept: application/json, and latitude and longitude as query parameters
3. Add excludeParameterMetadata=true to drop the parameter descriptions from every response
4. Pick the timestep by need. hourly covers 48 hours, three-hourly 168, daily 7 days, and each call counts against the daily limit
5. Stop on a 429. The limit is daily and resets at 00:00 UTC

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