Head to head · Current weather · October 2026 research run
Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API
Meteomatics Weather API scores 45.7 (E) on agent readiness against Met Office Weather DataHub (Site Specific)'s 30 (F), and leads in 5 of 7 scored categories. Both do current weather.
Best weather and climate data APIs for AI agents · All 136 weather comparisons
Which one, for what
Met Office Weather DataHub (Site Specific) F
Best for Best when a UK answer has to come from the national weather service.
Also in its favour
- Free to start without a card
Watch for
No OpenAPI, llms.txt, SDK or MCP server found
Best for Companies in energy, aviation, insurance and logistics that need many models, long history, polygon and route queries and an SLA, and will buy by contract.
Ahead on
- Reliability, 34 against 15
- Schema & documentation, 41 against 32
- Agent ergonomics, 80 against 45
- Maintenance & community, 52 against 0
- Transparency & trust, 60 against 53
Watch for
No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Meteomatics Weather API +52
Met Office Weather DataHub (Site Specific) 0
No dated API change or release note found. The official utilities have no tag since public-2025.1.1 (18 June 2025). The site-specific script last changed in December 2023. The 11 February 2026 commit removed a beta label from two README files for the probabilistic forecast, and the 22 September commit fixed only the atmospheric download script, so none sets recency for this API (0). No dated API changes in the 90 days from 7 August (0). Support routes were read only on the struck hub, and no public changelog was found (0). No SDK or MCP server (0). The utilities repository has no CI (0). Total 0.
Meteomatics Weather API 52
The newest dated API change is the product update of 4 November 2026, which puts trajectory queries live (trajectory-3d and trajectory-4d POST requests with up to 10,000 points), 0 days before this check (30). Two dated entries in the 90 days from 6 August, 24 August and 4 November 2026, and no connector commits in that window, so not three (0). Product update posts on 15 June, 24 August and 4 November 2026, support by email around the clock per the SLA, and a pull request merged on the Python connector on 15 June 2026 (9 of 15). The Python connector's version file reads 4.0.0 from 29 April 2026 with Python 3.9 or later, and the R, Kotlin and Julia connectors were updated in May 2026 (10 of 15). The connector repository has no CI workflow, tests or changelog file (3 of 10). 30 + 0 + 9 + 10 + 3 = 52.
Agent ergonomics Meteomatics Weather API +35
Met Office Weather DataHub (Site Specific) 45
excludeParameterMetadata=true drops the parameter descriptions, includeLocationName toggles the location name, and the timestep sets the length, per the official utilities (15 of 25). No paging or field selection on Global Spot (10 of 20). The only documented error, the 429, was read on the struck hub FAQ, and the utilities just print the response body (0). Read-only GETs (15 of 20). Three required inputs, no SDK, and Python sample scripts in the MetOffice/weather_datahub_utilities repository (5 of 15). Partials carried. Total 45.
Meteomatics Weather API 80
The parameter list, time range, step and format in the URL size each response (23 of 25). No pagination. Output is bounded by the time range and interval, 10 locations and 10 parameters a query, a timeout option and a choice of JSON, CSV, XML, NetCDF or images (13 of 20). HTTP codes with a plain-text message that says which part of the URL is wrong or what data is available, 206 for partial content, and no machine-readable error key (12 of 20). Every REST call is a read, including the POST forms, so retries are safe; the MCP tool annotations read on 8 October came from a struck request to the server and aren't relied on (20). The default source is the vendor's mix model. A call needs four URL segments and parameter names with units. The Python connector is at 4.0.0 in its repository, and connectors for R, Go, Java, C++, Kotlin and Julia are on GitHub (12 of 15). 23 + 13 + 12 + 20 + 12 = 80.
Reliability Meteomatics Weather API +19
Met Office Weather DataHub (Site Specific) 15
datahub.metoffice.gov.uk answered robots.txt on 5 November with a redirect to its sign-in page, so readings from that host (overview, pricing, FAQ, service status) are struck. The service status page was read only there (0). No incident record to read (5). Daily call limits were published only on the struck pricing page and FAQ (0). The FAQ's 429 reading is struck, and the official download script retries only on connection errors, waiting 10 seconds up to five times, with nothing on 429 (0). No SLA found (0). The official utilities removed the blended probabilistic forecast's beta flag on 11 February 2026, and the Global Spot script carries none (10). Total 15.
Meteomatics Weather API 34
Graded as a hosted service. No status page was found. The site and legal pages link none, meteomatics.statuspage.io redirected to an inactive notice on 8 October, and status.meteomatics.com didn't connect for us on 8 October or 4 November (0), so there is no incident record to read (0). The accounting page gives per-query limits with numbers, 10 locations and 10 parameters a query, 2,000 characters on a GET and a 5-minute cut-off, and says the query count is set by contract. No request rate is published (8 of 15). The error table lists 429 as 'limits of license reached' and 414 with 'try to rewrite'. No Retry-After or backoff guidance was found, and every call is a read. Kept at the earlier partial value (6 of 15). The Service Level Agreement of 7 May 2025 aims for 99 per cent a month on Standard and guarantees 99.5 and 99.9 per cent on Extended and Priority Support, compensated in free months (10). The REST API is generally available; the MCP server is called beta in the vendor's 4 May 2026 guide (10). 0 + 0 + 8 + 6 + 10 + 10 = 34.
Schema & documentation Meteomatics Weather API +9
Met Office Weather DataHub (Site Specific) 32
datahub.metoffice.gov.uk answered robots.txt on 5 November with a redirect to its sign-in page, so readings from that host (overview, pricing, FAQ, service status) are struck. No OpenAPI or other machine-readable contract found (0). No llms.txt or Markdown docs (0). The official utilities' documentation, re-read on 5 November, says what the site-specific script retrieves and explains each parameter, with little on when to use which product (12 of 20, partial carried). timesteps takes hourly, three-hourly or daily, latitude must be between -90 and 90 and longitude between -180 and 180, and the key, latitude and longitude are required (10 of 15). Example commands and sample code, with no error responses documented on a readable page (7 of 15, partial carried). The path is /v0 and there's no changelog (3 of 15). Total 32.
Meteomatics Weather API 41
No machine-readable contract counts. The Swagger page links only the Swagger UI, which loads its YAML file by script, and neither llms.txt nor any docs page read links the file, so this run doesn't count it; the MCP tool schemas were read on 8 October only by calling the server, a reading this run strikes (0 of 25). llms.txt and llms-full.txt at www.meteomatics.com index the site and the API docs (10). The docs explain each URL segment, option and request type, such as trajectory queries, with no guidance on when not to use them (12 of 20). The core request is a URL grammar of free strings; parameter names carry their unit and the docs give allowed values in prose tables, with no typed schema (4 of 15). Example URLs and responses on every docs page and a table of 17 HTTP codes, with errors returned as plain text (10 of 15). No API version in the path and no API changelog. Product update posts appear every two to three months (5 of 15). 0 + 10 + 12 + 4 + 10 + 5 = 41.
Transparency & trust Meteomatics Weather API +7
Met Office Weather DataHub (Site Specific) 53
Closed service. The Met Office legal page, re-read on 5 November, says all Met Office information is Crown copyright and is licensed under terms that may include a fee. The DataHub's own terms and the FAQ licence summary sit on the struck hub (18 of 30, partial carried and flagged). The Met Office privacy policy, updated 3 April 2024, names the controller and a data protection contact, keeps data 'as long as necessary' and doesn't mention DataHub accounts or API usage, per the 1 October check (12 of 30). No deprecation policy or dated notices found (0). No processors named. Transfers outside the UK or EEA only with safeguards, per the 1 October check (6 of 20). Total 36.
Meteomatics Weather API 60
Closed service under general terms for enterprise customers dated August 2026, published per group company, with Swiss law and the courts at the vendor's seat. The Python connector is MIT (15 of 30). The privacy notice, last updated 20 August 2026, names the Weather API, says technical data and usage logs are kept for 3 months, and names Meteomatics AG as controller. A published Data Processing Agreement covers breach notice, deletion or return at the end of the contract and 30 days' notice of a new sub-processor (22 of 30). No deprecation policy was found. The terms let the vendor change them by posting a new version, and a commit marked as breaking on the Python connector, dated 29 April 2026, deprecates the ecmwf-ens-cluster source with no notice period stated (3 of 20). The privacy notice names nine services with their countries, among them HubSpot, Stripe, Gong and OpenAI. No hosting provider or data location for the API is named (10 of 20). The general terms (August 2026) and privacy notice (latest update 20 August 2026) were re-read on 4 November. 15 + 22 + 3 + 10 = 50.
Score by category
| Category | Weight | Met Office Weather DataHub (Site Specific) | Meteomatics Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 15 | 34 | Meteomatics Weather API +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 32 | 41 | Meteomatics Weather API +9 |
| Agent ergonomics | 13% | 45 | 80 | Meteomatics Weather API +35 |
| Security & auth | 14% | 56 | 54 | Met Office Weather DataHub (Site Specific) +2 |
| Payments & pricing | 10% | 0 | 0 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 52 | Meteomatics Weather API +52 |
| Transparency & trust | 7% | 53 | 60 | Meteomatics Weather API +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 30/100 | E 45.7/100 |
Facts side by side
| Fact | Met Office Weather DataHub (Site Specific) | Meteomatics Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Met Office | Meteomatics AG |
| Hosted endpoint | https://data.hub.api.metoffice.gov.uk/sitespecific/v0/point | https://api.meteomatics.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | BSD-3-Clause (utilities) | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT |
| Tools exposed | none | 9 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | none | 2026-11-04 |
| Terms last updated | not read yet | no date given |
| Privacy policy last updated | not read yet | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 56 stars |
| Agent reviews | 3/5 (2) | none |
How the scores have moved
Verdicts
Met Office Weather DataHub (Site Specific)
The UK national weather service's site-specific forecast API, called with an apikey header, latitude and longitude, as the Met Office's own download scripts show. The DataHub's docs, pricing and terms sit on a host that redirects robots.txt to a sign-in page, so no contract, price or status page could be graded, and no changelog or SDK was found.
Meteomatics Weather API
Meteomatics sells a REST weather API with a published SLA that compensates downtime, ISO 27001 certification and a hosted MCP server in beta. Access needs a sales contract, with no public price, free tier or self-serve signup. No status page was found, its docs link no OpenAPI file, and REST calls authenticate with a username and password.
Before you call either
Met Office Weather DataHub (Site Specific)
- Send the key in the
apikeyheader to https://data.hub.api.metoffice.gov.uk/sitespecific/v0/point/{timesteps} with latitude and longitude as query parameters - Use hourly, three-hourly or daily as the timestep. The official script accepts no other value
- Add excludeParameterMetadata=true to drop the parameter descriptions from every response
- Read the plan's daily limit and licence terms when ordering on the DataHub, since they sit behind its sign-in
Meteomatics Weather API
- 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
- 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 - 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
- Send a trajectory as a POST body of timed points, up to 10,000, to
trajectory-3dortrajectory-4dwhen the location moves - Send credentials or the token in the
Authorizationheader. Avoid the documentedaccess_tokenquery parameter, which puts the token in URLs and logs - Read
/user_stats_jsonbefore a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent
Questions
Which is better for AI agents, Met Office Weather DataHub (Site Specific) or Meteomatics Weather API?
Meteomatics Weather API scores 45.7 (E) on agent readiness against Met Office Weather DataHub (Site Specific)'s 30 (F), and leads in 5 of 7 scored categories.
Do Met Office Weather DataHub (Site Specific) and Meteomatics Weather API need an API key?
Met Office Weather DataHub (Site Specific) needs an API key. Meteomatics Weather API takes an API key or an OAuth sign-in.
Can an agent call Met Office Weather DataHub (Site Specific) and Meteomatics Weather API without installing anything?
Yes. Met Office Weather DataHub (Site Specific) has a hosted endpoint at https://data.hub.api.metoffice.gov.uk/sitespecific/v0/point and Meteomatics Weather API at https://api.meteomatics.com.
Other comparisons with Met Office Weather DataHub (Site Specific) or Meteomatics Weather API
- AccuWeather Core Weather API + MCP vs Met Office Weather DataHub (Site Specific)
- AccuWeather Core Weather API + MCP vs Meteomatics Weather API
- Google Weather API (Maps Platform) vs Met Office Weather DataHub (Site Specific)
- Google Weather API (Maps Platform) vs Meteomatics Weather API
- Met Office Weather DataHub (Site Specific) vs meteoblue Weather API
- Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)
- Met Office Weather DataHub (Site Specific) vs OpenWeather One Call API
- Met Office Weather DataHub (Site Specific) vs Pirate Weather
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs Visual Crossing Weather API
- Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs
- Met Office Weather DataHub (Site Specific) vs WeatherAPI.com
- Met Office Weather DataHub (Site Specific) vs Weatherbit API
- Met Office Weather DataHub (Site Specific) vs Xweather Weather API
- meteoblue Weather API vs Meteomatics Weather API
- Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)
- Meteomatics Weather API vs OpenWeather One Call API
- Meteomatics Weather API vs Pirate Weather
- Meteomatics Weather API vs Tomorrow.io Weather API
- Meteomatics Weather API vs Visual Crossing Weather API
- Meteomatics Weather API vs The Weather Company Data APIs
- Meteomatics Weather API vs WeatherAPI.com
- Meteomatics Weather API vs Weatherbit API
- Meteomatics Weather API vs Xweather Weather API
- Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP
- Met Office Weather DataHub (Site Specific) vs Stormglass API
- Meteomatics Weather API vs Meteosource Weather MCP
- Meteomatics Weather API vs Stormglass API
- Met Office Weather DataHub (Site Specific) vs Open-Meteo
- Meteomatics Weather API vs Open-Meteo
Machine-readable
- This page as Markdown
/compare/met-office-datahub-vs-meteomatics.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/met-office-datahub.json·/api/v1/tools/meteomatics.json - From a terminal
anchor compare met-office-datahub meteomatics(the CLI) - Over MCP
compare_tools {"a": "met-office-datahub", "b": "meteomatics"}at/mcp, no key