Met Office Weather DataHub (Site Specific) vs Meteomatics Weather 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.

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.

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

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