Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)

Meteomatics Weather API

A public OpenAPI file, a hosted MCP server whose nine tools are all marked read-only, a published SLA with compensation and ISO 27001 certification suit company use. Access needs a sales contract, with no public price, free tier or self-serve signup found, no status page, and REST calls that authenticate with a username and password.

NOAA National Weather Service API (api.weather.gov)

Free, no key and no account, with public domain data. US and territories only.

Meteomatics Weather API

1. Ask the account owner for credentials first. There is no signup, and both the REST API and the MCP server need a Meteomatics account with API access
2. Build REST URLs as validdatetime/parameters/location/format, for example 2026-10-08T00:00:00Z/t_2m:C/52.52,13.40/json. Parameter names carry their unit after a colon
3. Keep each query to 10 locations and 10 parameters unless the contract says otherwise, and use POST when a GET URL passes 2,000 characters
4. Send credentials or the token in the Authorization header. Avoid the documented access_token query parameter, which puts the token in URLs and logs
5. Read /user_stats_json before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent
6. Treat reserved values such as -888 and -999 as invalid or missing data, and shrink the request when a 408 arrives after the 300-second timeout

NOAA National Weather Service API (api.weather.gov)

1. Set User-Agent to your app name and a contact email or the request is refused with 403
2. Cache the /points response per coordinate. The office and grid rarely change
3. Round coordinates to four decimal places. More precision returns an error
4. Don't add cache-busting query parameters. Unknown parameters return 400
5. Back off about five seconds after a throttled request and reuse the last good response