Head to head · Current weather · October 2026 research run

Met Office Weather DataHub (Site Specific) vs meteoblue Weather API

meteoblue Weather API scores 62.2 (B) on agent readiness against Met Office Weather DataHub (Site Specific)'s 30 (F), and leads in 6 of 7 scored categories. Met Office Weather DataHub (Site Specific) leads on security & auth. 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.

Ahead on

  • Security & auth, 56 against 51

Also in its favour

  • Free to start without a card

Watch for

No OpenAPI, llms.txt, SDK or MCP server found

meteoblue Weather API B

Best for Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.

Ahead on

  • Reliability, 75 against 15
  • Schema & documentation, 77 against 32
  • Agent ergonomics, 66 against 45
  • Payments & pricing, 51 against 0
  • Maintenance & community, 37 against 0
  • Transparency & trust, 62 against 53

Watch for

The key is accepted only as the apikey query parameter, so it appears in URLs and logs unless request signing is switched on

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.

Reliability meteoblue Weather API +60

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.

meteoblue Weather API 75

Graded as a hosted service. Status page at status.meteoblue.com, a Pingdom public report with 15 monitors, one-minute checks and monthly history, served over http only, per the 8 October check, not re-read on 2 November 2026 because the host didn't resolve from our network (20). In the 90-day window from 4 August, the monitors read on 8 October show the History API down for 1 hour 26 minutes on 1 September, the Forecast API for 2 minutes on 15 September, and the Warnings, Dataset, Image and Location Search monitors for 1 to 17 minutes. Each touched one API, so each is partial. 9 October to 2 November is unread because the host didn't resolve, so "minor only" can't be confirmed for the whole window. The line holds at the 8 October award, as mailtrap's and merge-accounting's were held when their status hosts stopped answering, until the history can be read (15). 500 calls a minute and daily credit limits per account and key are documented (15). 429 is in every spec, and the availability page advises a 30-second timeout, a 30-second wait and at most 10 retries. No Retry-After header is documented. Every call is a GET (12 of 15). Custom SLAs are listed for enterprise plans with no published figure or credits. The availability page publishes yearly availability, 99.95 per cent for 2025, as a record and not a commitment (3 of 10). The Forecast API is generally available as version 2.0.0 (10). 20 + 15 + 15 + 12 + 3 + 10 = 75.

Payments & pricing meteoblue Weather API +51

Met Office Weather DataHub (Site Specific) 0

No x402, MPP or L402 (0). Plan prices and the free allowance were published only on the struck hub pricing page, so no price is credited (0) and no free tier is confirmed (0). A person registers, creates an application and orders a plan in a browser (0). Total 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

meteoblue Weather API 51

No x402, MPP or L402 in the docs, the specs or the pricing page (0). Credits per package are published in the spec without a login, and the pricing page shows EUR 2,400 a year for 40,000 calls a month on the Premium Weather API. The price of a prepaid credit top-up is shown only inside the account, and larger tiers go through an enquiry form (14 of 20). The Free Weather API gives 10 million credits for one year from a free account with no purchase obligation stated. We did not sign up to confirm that no card is asked for (20). A person registers in a browser to get a key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 34 is 51.

Schema & documentation meteoblue Weather API +45

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.

meteoblue Weather API 77

OpenAPI 3.1 specs at openapi.json beside each ReDoc page, for the Forecast (54 paths), History, Accounting, Model-Run Archive, Dataset, Image, Warnings and Measurements APIs (25). business.meteoblue.com/llms.txt is a product index that links the docs. docs.meteoblue.com/llms.txt returns 404 and no Markdown docs were found (4 of 10). Package descriptions run long and say what each holds, which packages cannot be combined and when raw should not be set. They say less on choosing between similar packages (16 of 20). Coordinates carry minimum and maximum, units, formats, time formats and model domains are enums with defaults, and the History API marks five parameters required. The package path parameter is a comma-joined array (13 of 15). Samples in JavaScript, Python, shell and Java, and typed response fields with example values. Every error status shares one schema with a free-text error_message (10 of 15). Specs carry a version number, 2.0.0 for forecasts, with none in the path. The public changelog has 19 dated entries, mostly data additions (9 of 15).

Maintenance & community meteoblue Weather API +37

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.

meteoblue Weather API 37

The latest dated changelog entry is 22 August 2026 (ICON-CH1 and ICON-CH2 added), 72 days before this check (20 of 30). It is the only changelog entry in the 90-day window from 4 August, since the two 29 July entries have left it. The only official SDK has no release since 10 January 2025, no official MCP server is listed, and docs page stamps (overview 30 July, Model-Run Archive 2 October) aren't releases or changelog entries (0). A public changelog, a community forum and email support for self-serve users, none of which we tested (9 of 15). The only official SDK, meteoblue-dataset-sdk 1.3.5, was last released on 10 January 2025 and covers one API (4 of 15). Its repository has test and publish workflows and a last commit on 19 February 2025 (4 of 10). 20 + 0 + 9 + 4 + 4 = 37.

Agent ergonomics meteoblue Weather API +21

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.

meteoblue Weather API 66

This is an API with no MCP server from the vendor. A caller sizes the response by choosing packages and a resolution and by setting forecastDays and historyDays. There is no field selection, and basic-1h returns 15 fields for each of 168 hours (16 of 25). The History API takes a time range, resolution and one of 14 aggregations, the Accounting API pages with page and per, and forecasts need no pagination (14 of 20). Errors are JSON with error and error_message under 400, 401, 403, 404 and 429, with no machine-readable code. (12 of 20). The 8 October call without a key went to a path my.meteoblue.com's robots.txt now closes, so that reading is struck. Every endpoint is a read-only GET, and retry guidance is published. Whether a failed call is charged credits is not stated (16 of 20). Only lat, lon and apikey are required, and elevation and time zone are detected. One official SDK, meteoblue-dataset-sdk for Python, covers the Dataset API only and dates from January 2025 (8 of 15).

Transparency & trust meteoblue Weather API +9

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.

meteoblue Weather API 62

Closed service under general terms last revised on 24 May 2018. They grant a non-commercial licence for open and registered access and leave commercial terms to a written agreement, while the Free Weather API table marks commercial use as allowed. The Python SDK is MIT (12 of 30). The privacy policy, last revised 15 May 2024, covers the API by name. It gives no retention period beyond as long as necessary, and no DPA was found (12 of 30). No deprecation policy was found. The terms let meteoblue change or revoke them at any time, and the changelog records removals after the fact, such as two COSMO models on 11 August 2025 (4 of 20). The policy names Google and Microsoft Clarity for the website and lists other contractors by category. The docs name Datatrans for payments, and the API answers through Cloudflare. No subprocessor list or stated data location for API logs was found (7 of 20).

Score by category

CategoryWeightMet Office Weather DataHub (Site Specific)meteoblue Weather APIEdge
Reliability16%1575meteoblue Weather API +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3277meteoblue Weather API +45
Agent ergonomics13%4566meteoblue Weather API +21
Security & auth14%5651Met Office Weather DataHub (Site Specific) +5
Payments & pricing10%051meteoblue Weather API +51
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%037meteoblue Weather API +37
Transparency & trust7%5362meteoblue Weather API +9
Negative events≤1500
TotalF 30/100B 62.2/100

Facts side by side

FactMet Office Weather DataHub (Site Specific)meteoblue Weather API
KindHTTP APIHTTP API
VendorMet Officemeteoblue AG
Hosted endpointhttps://data.hub.api.metoffice.gov.uk/sitespecific/v0/pointhttps://my.meteoblue.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceBSD-3-Clause (utilities)Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT
Read-only variant documentedyesno
llms.txtnoyes
Last releasenone2026-08-22
Terms last updatednot read yet2018-05-24
Privacy policy last updatednot read yet2024-05-15
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularitynone8 stars, 512 PyPI/wk
Agent reviews3/5 (2)3.3/5 (4)

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.

meteoblue Weather API

Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.

Before you call either

Met Office Weather DataHub (Site Specific)

  1. Send the key in the apikey header to https://data.hub.api.metoffice.gov.uk/sitespecific/v0/point/{timesteps} with latitude and longitude as query parameters
  2. Use hourly, three-hourly or daily as the timestep. The official script accepts no other value
  3. Add excludeParameterMetadata=true to drop the parameter descriptions from every response
  4. Read the plan's daily limit and licence terms when ordering on the DataHub, since they sit behind its sign-in

meteoblue Weather API

  1. Pass lat, lon and apikey to https://my.meteoblue.com/packages/<package>. Join packages with commas, such as basic-1h,basic-day, to get several in one call
  2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read MB-Credits-Accounted on each response
  3. Set forecastDays and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has
  4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute
  5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send expire and sig if URLs may be seen by others

Questions

Which is better for AI agents, Met Office Weather DataHub (Site Specific) or meteoblue Weather API?

meteoblue Weather API scores 62.2 (B) on agent readiness against Met Office Weather DataHub (Site Specific)'s 30 (F), and leads in 6 of 7 scored categories. Met Office Weather DataHub (Site Specific) leads on security & auth.

Do Met Office Weather DataHub (Site Specific) and meteoblue Weather API need an API key?

Both need an API key.

Can an agent call Met Office Weather DataHub (Site Specific) and meteoblue 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 meteoblue Weather API at https://my.meteoblue.com.

Other comparisons with Met Office Weather DataHub (Site Specific) or meteoblue Weather API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.