# Meteomatics Weather API > Meteomatics Weather API returns forecasts, current observations, history back to 1940 and climate scenarios for points, routes, grids and polygons. It is a REST API with a hosted MCP server in beta, sold by contract to businesses. - Canonical: https://www.anchorterminal.com/tools/meteomatics - Markdown: https://www.anchorterminal.com/tools/meteomatics.md (~8,350 tokens) - Slim: https://www.anchorterminal.com/tools/meteomatics.min.md (~1,980 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/meteomatics.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade D · 49.6/100 · rank #606 of 722 · #12 in Weather & climate data · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Meteomatics AG (https://www.meteomatics.com) | | Kind | HTTP API | | Category | Weather & climate data (https://www.anchorterminal.com/categories/weather) | | Transport | HTTP | | Endpoint | `https://api.meteomatics.com` | | Auth | OAuth or key · Access is granted by sales. A person talks to Meteomatics, signs an offer and receives a username and password by email. REST calls send them as HTTP Basic, or exchange them at https://login.meteomatics.com/api/v1/token for a token that lasts 2 hours and is documented as an `access_token` query parameter. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE, refresh tokens and one scope, `weather:read`, and logs in with the same account. | | Pricing | Paid (Paid) · No public price. The pricing page says prices are based on usage and package and leads to a sales form. No free tier, sandbox or self-serve trial is on the site, so an agent can't start without a contract. The general terms allow a trial through an individual offer, fees are non-refundable and may be adjusted yearly, and the term renews unless ended 3 months ahead (https://www.meteomatics.com/en/pricing/, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | | Tools exposed | 9 | | Packages | pypi: `meteomatics` | | Source | https://github.com/meteomatics/python-connector-api | | Docs | https://www.meteomatics.com/en/api/getting-started/ | | llms.txt | https://www.meteomatics.com/llms.txt | | Last release | 2026-08-24 | | GitHub stars | 56 (as of 2026-10-08) | | PyPI downloads / week | 15,915 | | Surface graded | The public REST API at https://api.meteomatics.com, with the hosted MCP server noted beside it | | Request pattern | `api.meteomatics.com/validdatetime/parameters/locations/format?optionals`, by GET or POST. Locations are coordinates, lines, grids, polygons, postal codes or station identifiers | | Endpoints | OpenAPI 3.0.0 file, 31 paths and 31 operations. Time series and grids, polygons, `/find_station`, `/get_init_date`, `/get_time_range`, lightning lists, isolines and isobands, fronts, jet streams, UK flood alerts, earthquakes, aviation bulletins, `/user_stats`, WMS, WFS and vector tile styles | | MCP tools | get_weather_for_location, get_weather_for_locations, get_weather_for_polygon, get_weather_map, get_weather_map_legend, get_opmet, get_opmet_history, find_station, find_nearby_stations | | Credentials | Username and password by email after a contract. HTTP Basic, or a 2-hour token from login.meteomatics.com. OAuth with dynamic client registration, PKCE and the `weather:read` scope on the MCP server | | Limits | 10 locations and 10 parameters a query (10,000 locations with the area option), 2,000 characters recommended on a GET, 300-second timeout. Query count by contract, shown at `/user_stats_json`. No request rate published | | Errors | Plain-text messages with HTTP codes. 206 partial content, 400, 401, 402, 403, 404, 408, 413, 414, 429 (licence limits reached), 500, 501, 503, 504 and 505 | | Formats | JSON, CSV, XML, HTML, NetCDF, PNG, WebP and GeoTIFF, plus WMS, WFS and vector tiles | | Data range | History back to 1940, current observations, forecasts and climate scenarios to 2100, per the vendor. `/get_time_range` returns the dates available for a model and parameter | | Alerts and marine | Warning index parameters for frost, rain, snow, wind, fog and thunderstorms, UK flood alerts from Defra, national weather alert tiles, and marine parameters for waves, currents, tides, salinity and sea ice | | SLA | Standard aims for 99 per cent a month with no compensation. Extended Support guarantees 99.5 per cent and Priority Support 99.9 per cent, compensated with 1 to 3 free months. Dated 7 May 2025 | | Connectors | Python `meteomatics` 4.0.0 on PyPI (29 April 2026, MIT, Python 3.9 or later). Repositories for R, Go, Java, C++, Kotlin and Julia, and guides for Excel, Power BI, Tableau, QGIS and ArcGIS | | Certifications | ISO 27001 (announced 23 June 2026) and Cyber Essentials, per the information security page | | Status | No status page found | | Capabilities | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | | Tags | hosted, enterprise, sales-led, closed-source, openapi, llms-txt, mcp, oauth, python, sla, iso27001 | | JSON | https://www.anchorterminal.com/api/v1/tools/meteomatics.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 34 | 6.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 71 | 11.5 | | Agent ergonomics | 13% | 16.2 | 80 | 13.0 | | Security & auth | 14% | 17.5 | 54 | 9.4 | | Payments & pricing | 10% | 12.5 | 0 | 0.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 42 | 3.7 | | Transparency & trust (editorial 50, provenance 68) | 7% | 8.8 | 59 | 5.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **49.6 → D** | ### Why each score - Reliability 34: Graded as a hosted service. No status page was found. The site and legal pages link none, meteomatics.statuspage.io redirects to an inactive notice, and status.meteomatics.com didn't connect for us (0), so there is no incident record to read (0). The docs give 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 say the query count is set by contract and readable at `/user_stats_json`. No request rate is published (8 of 15). 429 is documented as licence limits reached and 408 comes with advice to shrink the query. No `Retry-After` or backoff guidance was found, and every call is a read (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 has been online since May 2015 per the docs. The MCP server is described as beta in the vendor's 4 May 2026 guide (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 71: OpenAPI 3.0.0 file at swagger-ui.meteomatics.com/meteomatics_swagger_definition.yaml with 31 paths and 31 operations. The docs say it is documentation only and doesn't list every weather parameter. The MCP server gives JSON Schema inputs for all nine tools (22 of 25). `llms.txt` and `llms-full.txt` at www.meteomatics.com index the site and the API docs (10). MCP tool descriptions say when to use each tool and what not to put in a field, and the docs explain each URL segment and option (15 of 20). The OpenAPI file has 43 enums, but the core request is a URL grammar of free strings, more than 1,800 parameter names aren't enumerated, and MCP inputs such as `parameters`, `aggregation` and `crs` are plain strings with allowed values in prose (8 of 15). Example URLs and responses on every docs page, 149 examples in the OpenAPI file and a table of 17 HTTP codes, with errors returned as plain text (11 of 15). No API version in the path and no API changelog. JSON responses carry `version` 3.0 and product update posts appear every two to three months (5 of 15). - Agent ergonomics 80: The parameter list, time range, step and format in the URL size each response, and the MCP server has nine tools in about 15 KB of definitions (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 form, and all nine MCP tools carry `readOnlyHint` true and `destructiveHint` false (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 on PyPI at 4.0.0, and connectors for R, Go, Java, C++, Kotlin and Julia are on GitHub (12 of 15). - Security & auth 54: REST calls use HTTP Basic with a username and password sent by email, or a token from login.meteomatics.com that lasts 2 hours and is documented as an `access_token` query parameter. No key rotation or separate keys were found in the docs. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE (S256), refresh tokens and one scope, `weather:read` (12 of 30, after the 10-point deduction for a secret in the URL). The whole API is read-only and the single OAuth scope is a read scope (15 of 20). Responses are mostly numbers. Aviation bulletins and official alerts carry third-party text, and the MCP guide tells users to check model output, with no guidance on untrusted content (9 of 15). `/user_stats` and `/user_stats_json` report query counts against contract limits, and the privacy notice says usage logs are kept for 3 months. No per-call log for the customer was found (5 of 15). ISO 27001 certification announced on 23 June 2026 with the certificate published, Cyber Essentials, and a security contact for vulnerability reports. No security.txt (404) and no bug bounty (13 of 20). - Payments & pricing 0: No x402, MPP or L402 in the docs or the OpenAPI file. The error table lists 402, with no payment protocol behind it (0). The pricing page says prices are based on usage and gives no figure, only a form to talk to sales (0). No free tier or trial is on the site. The general terms let Meteomatics grant a trial through an individual offer (0). A person talks to sales and receives a username and password by email. The MCP server registers OAuth clients by API but still needs that account (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 42: The newest dated product update is 24 August 2026 (an icing warning parameter and radar sources for Australia, Turkey and Japan), 45 days before this check (20 of 30). That is one dated entry in the last 90 days, not three (0). Product update posts on 26 March, 15 June and 24 August 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 reached 4.0.0 on PyPI on 29 April 2026 and needs Python 3.9 or later. The MCP server isn't in the official registry (10 of 15). The connector repository has no CI workflow, tests or changelog file (3 of 10). - Transparency & trust 59: 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/meteomatics.md (JSON https://www.anchorterminal.com/fixes/meteomatics.json) ### What we couldn't check - unchecked: whether a status page exists at status.meteomatics.com. The address didn't connect for us, the site links no status page, and meteomatics.statuspage.io redirects to an inactive notice - unchecked: authenticated behaviour, including response headers on 429, error bodies and the shape of `/user_stats_json`. We had no credentials and called no data endpoint or MCP tool - unchecked: open issues and pull requests on the connector repositories. The GitHub API refused us for its rate limit, so we read the cloned history only - Whether a trial or test account is still granted. The terms allow a trial through an individual offer and the Python connector has an example named `12_test_account_options.py`, but the site shows none - The MCP server answered `initialize` and `tools/list` without a token on 8 October 2026. The docs page doesn't say it is beta, while the 4 May 2026 guide does - The OpenAPI file lists http://api.meteomatics.com as a second server and one docs example uses http. We didn't test whether plain HTTP answers - The general terms are published per group company. We used the Meteomatics AG version, dated August 2026, and didn't compare the GmbH, Limited and Inc. versions - The lead was right. The MCP entry among the data connectors is a hosted server with OAuth, and credentials are issued after a sales conversation ### Sources - getting started: (seen 2026-10-08) - docs and site index (llms.txt): (seen 2026-10-08) - OpenAPI file: (seen 2026-10-08) - Swagger page: (seen 2026-10-08) - MCP server docs: (seen 2026-10-08) - MCP OAuth metadata: (seen 2026-10-08) - MCP endpoint (initialize and tools/list): (seen 2026-10-08) - MCP guide, 4 May 2026: (seen 2026-10-08) - token authentication: (seen 2026-10-08) - error codes: (seen 2026-10-08) - accounting and limits: (seen 2026-10-08) - usage statistics and meta requests: (seen 2026-10-08) - optional fields: (seen 2026-10-08) - FAQ: (seen 2026-10-08) - pricing: (seen 2026-10-08) - product page: (seen 2026-10-08) - Service Level Agreement: (seen 2026-10-08) - general terms, Meteomatics AG: (seen 2026-10-08) - privacy notice: (seen 2026-10-08) - Data Processing Agreement: (seen 2026-10-08) - information security: (seen 2026-10-08) - imprint: (seen 2026-10-08) - news and product updates: (seen 2026-10-08) - product update, August 2026: (seen 2026-10-08) - Python connector repository: (seen 2026-10-08) - Python connector on PyPI: (seen 2026-10-08) - MCP registry search: (seen 2026-10-08) - inactive Statuspage address: (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - domain registration (RDAP): (seen 2026-10-08) ## Who's behind it (provenance 68/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Meteomatics AG | 20/20 | | Domain age | meteomatics.com, registered 2011-09-21 (15 years) | 15/15 | | Endpoint on the vendor's domain | api.meteomatics.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The imprint names Meteomatics AG, Unterstrasse 12, 9000 St. Gallen, Switzerland, company number CHE-375.414.829, with group companies in England, Norway, Germany and the United States. The terms are the General Terms and Conditions for Enterprise Customers of Meteomatics AG, dated August 2026. Separate versions exist for Meteomatics GmbH, Meteomatics Limited and Meteomatics Inc. The privacy notice (latest update 20 August 2026) covers the group, names the Weather API and names Meteomatics AG as controller. A Data Processing Agreement is published beside it. The REST API answers at api.meteomatics.com, tokens at login.meteomatics.com and the MCP server at mcp.meteomatics.com. No status page was found. meteomatics.statuspage.io redirects to an inactive notice, and status.meteomatics.com didn't connect for us. No API changelog was found. Product updates are posted as news articles at www.meteomatics.com/en/news/. www.meteomatics.com, mcp.meteomatics.com and login.meteomatics.com return 404 for /.well-known/security.txt. The information security page gives a contact address for vulnerability reports. RDAP gives a registration date of 2011-09-21 for meteomatics.com. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.meteomatics.com/en/gtc-meteomatics-ag/), read 2026-10-08, gives no date, states 6 of the 7 things a reader expects. - Not found in the text. Gives the date it was last updated. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Also in the text (2026-10-08). The agreement renews automatically for further terms unless the customer gives notice of termination at least three months before the current term ends. "15.2 The Initial Term shall renew automatically for subsequent terms (each referred to as the ‘’Renewal Term’’) unless the Customer gives a notice of termination to Meteomatics not later than 3 (in words: three) months before the expiration of the Initial Period or Renewal Term." - Also in the text (2026-10-08). Meteomatics may adjust fees each year and at the start of each renewal term. "8.5 Meteomatics has the right to adjust the Fees annually and/or at the beginning of each Renewal Term." - Also in the text (2026-10-08). The customer must use the services only for internal business purposes or the purpose stated in the agreement. "9.1.2 use the Services of Meteomatics solely for internal business purpose or the purpose indicated in the Agreement;" **Privacy policy** (https://www.meteomatics.com/en/privacy-policy/), read 2026-10-08, gives no date, states 6 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Says how long data is kept. Names a period of 3 months. - Not found in the text. Says whether personal data is sold or shared for advertising. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). Meteomatics states it does not use personal data to train or improve general-purpose AI models unless the data subject expressly authorises it. "Where we use artificial intelligence systems in connection with our services or internal operations, we do not use personal data to train, retrain, fine-tune, or otherwise improve general-purpose artificial intelligence models unless expressly authorised by the relevant data subject." - Also in the text (2026-10-08). The privacy notice carries SMS terms under which the customer must keep records of each user's consent to text messages and hand them to the vendor on request. "(e) that it will maintain records of all User consent and revocation and will provide such records to the Service Provider promptly upon request." ## Live (updated 2026-10-08 21:53 UTC) - Right now: up, HTTP 200, 217 ms, checked 2026-10-08 21:53 UTC (get on `https://api.meteomatics.com`) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 223 ms · p95 447 ms - Always current: https://www.anchorterminal.com/api/v1/live/meteomatics.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Hosted MCP server at https://mcp.meteomatics.com/mcp with nine tools, each annotated `readOnlyHint` true and `destructiveHint` false - Published SLA dated 7 May 2025 with 99.5 and 99.9 per cent uptime guarantees on the two paid support levels, compensated in free months - Public OpenAPI 3.0.0 file with 31 operations, plus `llms.txt` and `llms-full.txt` indexes of the site and docs - ISO 27001 certification announced 23 June 2026, Cyber Essentials, and a named security contact for vulnerability reports - One URL pattern covers history from 1940, forecasts and climate scenarios, in JSON, CSV, XML, NetCDF or image formats ## Weaknesses - No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation - No status page found. meteomatics.statuspage.io redirects to an inactive notice and the site links none - REST calls use HTTP Basic with the account username and password, and the two-hour token may travel as an `access_token` query parameter - No request rate is published. The query count is set by contract, and 429 carries no documented `Retry-After` - No API changelog or deprecation policy found. Product update posts appear every two to three months - The MCP server is described as beta in the vendor's 4 May 2026 guide and isn't in the official MCP registry ## Before you call it (notes for agents) 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 ## Connect Install: ```bash pip install meteomatics ``` First request: ```bash curl -u USERNAME:PASSWORD 'https://api.meteomatics.com/2026-10-08T00:00:00Z/t_2m:C/52.520551,13.461804/json' ``` MCP client configuration: ```json { "name": "meteomatics", "type": "url", "url": "https://mcp.meteomatics.com/mcp" } ``` Through letme (picks today, calling later): https://letme.dev/meteomatics. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Xweather Weather API | B | 67.1 | 219 | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | no | https://www.anchorterminal.com/tools/xweather.md | | WeatherAPI.com | B | 65.3 | 260 | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | no | https://www.anchorterminal.com/tools/weatherapi-com.md | | meteoblue Weather API | C | 61.7 | 360 | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | no | https://www.anchorterminal.com/tools/meteoblue.md | | The Weather Company Data APIs | D | 52.6 | 565 | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | no | https://www.anchorterminal.com/tools/weather-company.md | | Tomorrow.io Weather API | D | 51.4 | 578 | weather.current, weather.forecast, weather.historical, weather.alerts, weather.marine | no | https://www.anchorterminal.com/tools/tomorrow-io.md | | Google Weather API (Maps Platform) | B | 66.8 | 226 | weather.current, weather.forecast, weather.historical, weather.alerts | no | https://www.anchorterminal.com/tools/google-weather-api.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The hosted MCP server at https://mcp.meteomatics.com/mcp lists nine tools for point, multi-point and polygon time series, WMS map images and legends, aviation reports and station search, all annotated read-only (source: ) - The vendor's guide of 4 May 2026 calls the MCP server a beta and says not every API function is supported through it (source: ) - Each query is limited to 10 locations and 10 parameters, or 10,000 locations with the area option, and is cut off after 5 minutes with a 408. The query count is set by contract (source: ) - The Service Level Agreement of 7 May 2025 has three levels, a 99 per cent monthly aim with no compensation, and 99.5 and 99.9 per cent guarantees compensated with 1 to 3 free months (source: ) - The general terms limit use to internal business purposes or the purpose in the agreement, and bar passing the services or documentation to third parties without written consent (source: ) - Meteomatics says the API draws on more than 110 models and 1,800 parameters, with history back to 1940, climate scenarios to 2100 and downscaling to 90 metres (source: ) - ISO 27001 certification was announced on 23 June 2026, with the certificate published, alongside Cyber Essentials (source: ) ## Compare - [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md): D 48.4 vs D 49.6 - [Google Weather API (Maps Platform) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.md): B 66.8 vs D 49.6 - [Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.md): E 45.5 vs D 49.6 - [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md): C 61.7 vs D 49.6 - [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md): D 49.6 vs D 49.6 - [Meteomatics Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md): D 49.6 vs C 57.4 - [Meteomatics Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.md): D 49.6 vs B 65.9 - [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md): D 49.6 vs D 51.4 - [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md): D 49.6 vs C 59.9 - [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md): D 49.6 vs D 52.6 - [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md): D 49.6 vs B 65.3 - [Meteomatics Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.md): D 49.6 vs C 57.7 - [Meteomatics Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-xweather.md): D 49.6 vs B 67.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on meteomatics.com or one of its subdomains, or the README of github.com/meteomatics/python-connector-api. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "meteomatics", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Meteomatics Weather API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Meteomatics Weather API on Anchor Terminal](https://www.anchorterminal.com/badges/meteomatics.svg)](https://www.anchorterminal.com/tools/meteomatics) ``` Plain link: ```html Meteomatics Weather API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Meteomatics Weather API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/meteomatics-dark.png - Light: https://www.anchorterminal.com/assets/share/meteomatics-light.png