{ "data": { "a": { "slug": "meteoblue", "name": "meteoblue Weather API", "vendor": "meteoblue AG", "vendorUrl": "https://www.meteoblue.com", "kind": "http-api", "category": "weather", "summary": "Weather data APIs from meteoblue AG of Basel, Switzerland. The Forecast API returns point forecasts in packages by coordinates, with History, Warnings, Dataset, Image and Maps APIs beside it, over HTTPS with an API key.", "url": "https://www.anchorterminal.com/tools/meteoblue", "markdownUrl": "https://www.anchorterminal.com/tools/meteoblue.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteoblue.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteoblue.json", "repo": "https://github.com/meteoblue/python-dataset-sdk", "license": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "transports": [ "http" ], "remoteUrl": "https://my.meteoblue.com", "packages": [ { "registry": "pypi", "name": "meteoblue-dataset-sdk" } ], "auth": "api-key", "authNotes": "Self-serve key from a meteoblue account, created in a browser and managed in the Weather API Manager. The key goes in the `apikey` query parameter on every request, and no header option is documented. An account can hold several keys, each with a daily credit limit, an IP allow list, a referrer allow list and an optional shared secret for HMAC-SHA256 signed URLs. Paid plans start with an enquiry.", "pricing": "freemium", "pricingNotes": "Free Weather API with 10 million credits for one year from a free account, covering nine forecast packages, so an agent's owner can start without a contract. Calls cost 4,000 to 96,000 credits by package. The Premium Weather API is shown at EUR 2,400 a year for 40,000 calls a month, with larger tiers by enquiry. Prepaid credit prices are shown only after login (https://business.meteoblue.com/pricing, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI specs or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 8, "npmWeekly": null, "pypiWeekly": 512, "asOf": "2026-10-08" }, "docsUrl": "https://docs.meteoblue.com/en/weather-apis/introduction/overview", "llmsTxt": "https://business.meteoblue.com/llms.txt", "openapi": "https://my.meteoblue.com/packages/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "openapi", "llms-txt", "python", "status-page", "europe" ], "lastRelease": "2026-08-22", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 360, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 57, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.1 specs for the Forecast (54 paths), History, Dataset, Image, Warnings, Measurements, Accounting and Model-Run Archive APIs, each at `openapi.json` beside its ReDoc page", "The Forecast API spec lists credits per package, 4,000 for `basic-day` and `current`, 8,000 for `basic-1h`, and each response carries an `MB-Credits-Accounted` header", "Free Weather API with 10 million credits for one year from a self-serve account, with no purchase obligation stated", "Keys can be limited by daily credits, IP range and referrer, or tied to an HMAC-SHA256 signature with an expiry time", "Pingdom status page with 15 monitors and monthly history. The Forecast API monitor shows one 2-minute outage in the 90 days to 8 October 2026" ], "weaknesses": [ "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on", "The free trial covers nine forecast packages at hourly or coarser steps. Current conditions, sea, history, warnings and the Dataset API need a paid plan", "No security.txt, disclosure policy, SOC 2 or ISO 27001 was found. The only certificate published is ISO 9001:2015", "The general terms date from 24 May 2018, give no API-specific clauses and let meteoblue change or revoke them at any time", "The History API monitor shows an outage of 1 hour 26 minutes on 1 September 2026, and the status page is served over plain http only" ], "agentNotes": [ "Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call", "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", "Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 66, "maintenance": 57, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 35 }, "provenanceScore": 87 }, "connect": { "install": "pip install meteoblue-dataset-sdk", "http": "curl \"https://my.meteoblue.com/packages/basic-1h?lat=47.5596\u0026lon=7.5886\u0026tz=utc\u0026apikey=YOUR_APIKEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/meteoblue" }, "area": "domain-data", "provenance": { "legalEntity": "meteoblue AG", "domain": "meteoblue.com", "domainRegistered": "2005-11-15", "endpointOnVendorDomain": true, "terms": "https://business.meteoblue.com/terms-conditions", "privacy": "https://business.meteoblue.com/privacy-policy", "statusPage": "http://status.meteoblue.com/", "changelog": "https://business.meteoblue.com/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms and conditions (last revised 24 May 2018) are meteoblue's general terms for all services, products and data, the API included. They name meteoblue AG, Basel, under Swiss law with Basel as forum. No separate API agreement is published, and commercial terms are agreed in writing.", "The privacy policy (last revised 15 May 2024) states that it applies to all meteoblue services however they are used, and names the website, apps and API. The same two texts are also served at content.meteoblue.com/en/about-us/legal/.", "The imprint gives meteoblue AG, Greifengasse 38, CH-4058 Basel, commercial register number CHE-113.182.626.", "The APIs answer at my.meteoblue.com, warnings-api.meteoblue.com and measurements-api.meteoblue.com, behind Cloudflare.", "/.well-known/security.txt returns 404 on www.meteoblue.com, my.meteoblue.com, business.meteoblue.com and docs.meteoblue.com, and 403 on content.meteoblue.com.", "status.meteoblue.com is a Pingdom public report with 15 monitors. It answers over http. Over https the certificate does not match the host name.", "The changelog is on the business site, 19 dated entries from 11 August 2025 to 22 August 2026, mostly data and model additions.", "RDAP for meteoblue.com gives a registration date of 2005-11-15." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteoblue.json", "live": { "slug": "meteoblue", "probe": { "target": "https://my.meteoblue.com", "method": "get", "lastAt": "2026-10-08T21:12:15.476668876Z", "lastOk": true, "lastStatus": 404, "lastMs": 68, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 68, "p95ms24h": 164, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "http://status.meteoblue.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:46.956747067Z" }, "updatedAt": "2026-10-08T21:12:15.476668876Z" } }, "answer": "meteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics.", "b": { "slug": "meteomatics", "name": "Meteomatics Weather API", "vendor": "Meteomatics AG", "vendorUrl": "https://www.meteomatics.com", "kind": "http-api", "category": "weather", "summary": "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.", "url": "https://www.anchorterminal.com/tools/meteomatics", "markdownUrl": "https://www.anchorterminal.com/tools/meteomatics.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteomatics.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteomatics.json", "repo": "https://github.com/meteomatics/python-connector-api", "license": "Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT", "transports": [ "http" ], "remoteUrl": "https://api.meteomatics.com", "packages": [ { "registry": "pypi", "name": "meteomatics" } ], "auth": "mixed", "authNotes": "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", "pricingNotes": "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).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 56, "npmWeekly": null, "pypiWeekly": 15915, "asOf": "2026-10-08" }, "docsUrl": "https://www.meteomatics.com/en/api/getting-started/", "llmsTxt": "https://www.meteomatics.com/llms.txt", "openapi": "https://swagger-ui.meteomatics.com/meteomatics_swagger_definition.yaml", "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" ], "lastRelease": "2026-08-24", "graded": true, "anchor": { "graded": true, "score": 49.6, "grade": "D", "agentReady": false, "rank": 606, "ranked": true, "rankOf": 722, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 42, "payments": 0, "reliability": 34, "schema": 71, "security": 54, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "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" ], "agentNotes": [ "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 credentials or the token in the `Authorization` header. Avoid the documented `access_token` query parameter, which puts the token in URLs and logs", "Read `/user_stats_json` before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.6 } ], "editorialScores": { "ergonomics": 80, "maintenance": 42, "payments": 0, "reliability": 34, "schema": 71, "security": 54, "transparency": 50 }, "provenanceScore": 68 }, "connect": { "install": "pip install meteomatics", "http": "curl -u USERNAME:PASSWORD 'https://api.meteomatics.com/2026-10-08T00:00:00Z/t_2m:C/52.520551,13.461804/json'", "config": { "name": "meteomatics", "type": "url", "url": "https://mcp.meteomatics.com/mcp" } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/meteomatics" }, "area": "domain-data", "provenance": { "legalEntity": "Meteomatics AG", "domain": "meteomatics.com", "domainRegistered": "2011-09-21", "endpointOnVendorDomain": true, "terms": "https://www.meteomatics.com/en/gtc-meteomatics-ag/", "privacy": "https://www.meteomatics.com/en/privacy-policy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "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." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteomatics.json", "live": { "slug": "meteomatics", "probe": { "target": "https://api.meteomatics.com", "method": "get", "lastAt": "2026-10-08T21:12:15.506490015Z", "lastOk": true, "lastStatus": 200, "lastMs": 222, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 241, "p95ms24h": 447, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:15.506490015Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "meteoblue AG", "b": "Meteomatics AG", "name": "Vendor" }, { "a": "https://my.meteoblue.com", "b": "https://api.meteomatics.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "b": "Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT", "name": "Licence" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-22", "b": "2026-08-24", "name": "Last release" }, { "a": "2018-05-24", "b": "no date given", "name": "Terms last updated" }, { "a": "2024-05-15", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "8 stars, 512 PyPI/wk", "b": "56 stars, 16k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "meteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics.", "question": "Which is better for AI agents, meteoblue Weather API or Meteomatics Weather API?" }, { "answer": "meteoblue Weather API needs an API key. Meteomatics Weather API takes an API key or an OAuth sign-in.", "question": "Do meteoblue Weather API and Meteomatics Weather API need an API key?" }, { "answer": "Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Meteomatics Weather API at https://api.meteomatics.com.", "question": "Can an agent call meteoblue Weather API and Meteomatics Weather API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 34", "Schema \u0026 documentation, 77 against 71", "Payments \u0026 pricing, 34 against 0", "Maintenance \u0026 community, 57 against 42" ], "also": null, "goodFor": "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.", "slug": "meteoblue", "watchFor": "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on" }, { "aheadOn": [ "Agent ergonomics, 80 against 66" ], "also": null, "goodFor": "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.", "slug": "meteomatics", "watchFor": "No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation" } ], "job": { "capability": "weather.current", "name": "Weather current" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.json", "title": "AccuWeather Core Weather API + MCP vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.json", "title": "AccuWeather Core Weather API + MCP vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.json", "title": "Google Weather API (Maps Platform) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.json", "title": "Google Weather API (Maps Platform) vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.json", "title": "Met Office Weather DataHub (Site Specific) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.json", "title": "Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.json", "title": "meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.json", "title": "meteoblue Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.json", "title": "meteoblue Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.json", "title": "meteoblue Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.json", "title": "meteoblue Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.json", "title": "meteoblue Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.json", "title": "meteoblue Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.json", "title": "meteoblue Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-xweather.json", "title": "meteoblue Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.json", "title": "Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.json", "title": "Meteomatics Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.json", "title": "Meteomatics Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json", "title": "Meteomatics Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.json", "title": "Meteomatics Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "title": "Meteomatics Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.json", "title": "Meteomatics Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.json", "title": "Meteomatics Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-xweather.json", "title": "Meteomatics Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-xweather" } ], "scores": [ { "by": 41, "edge": "meteoblue", "key": "reliability", "meteoblue": 75, "meteomatics": 34, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "meteoblue", "key": "schema", "meteoblue": 77, "meteomatics": 71, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 14, "edge": "meteomatics", "key": "ergonomics", "meteoblue": 66, "meteomatics": 80, "name": "Agent ergonomics", "weight": 13 }, { "by": 3, "edge": "meteomatics", "key": "security", "meteoblue": 51, "meteomatics": 54, "name": "Security \u0026 auth", "weight": 14 }, { "by": 34, "edge": "meteoblue", "key": "payments", "meteoblue": 34, "meteomatics": 0, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "edge": "meteoblue", "key": "maintenance", "meteoblue": 57, "meteomatics": 42, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "edge": "meteoblue", "key": "transparency", "meteoblue": 61, "meteomatics": 59, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "meteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics. Both do weather current.", "verdicts": { "meteoblue": "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.", "meteomatics": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics", "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md", "slim": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.min.md" }, "markdown": "meteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics. Both do weather current.\n\n- meteoblue Weather API: grade C, 61.7/100, rank #360 of 722. Markdown https://www.anchorterminal.com/tools/meteoblue.md · JSON https://www.anchorterminal.com/api/v1/tools/meteoblue.json\n- Meteomatics Weather API: grade D, 49.6/100, rank #606 of 722. Markdown https://www.anchorterminal.com/tools/meteomatics.md · JSON https://www.anchorterminal.com/api/v1/tools/meteomatics.json\n\n## Which one, for what\n\n### meteoblue Weather API (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 75 against 34\n- Schema \u0026 documentation, 77 against 71\n- Payments \u0026 pricing, 34 against 0\n- Maintenance \u0026 community, 57 against 42\n\nWatch for: The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on\n\n### Meteomatics Weather API (D)\n\nGood 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.\n\nAhead on:\n- Agent ergonomics, 80 against 66\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n\n## Score by category\n\n| Category | Weight | meteoblue Weather API | Meteomatics Weather API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 34 | meteoblue Weather API +41 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 71 | meteoblue Weather API +6 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 80 | Meteomatics Weather API +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 54 | Meteomatics Weather API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 34 | 0 | meteoblue Weather API +34 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 57 | 42 | meteoblue Weather API +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 59 | meteoblue Weather API +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.7 · C** | **49.6 · D** | |\n\n## Facts side by side\n\n| Fact | meteoblue Weather API | Meteomatics Weather API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | meteoblue AG | Meteomatics AG |\n| Hosted endpoint | `https://my.meteoblue.com` | `https://api.meteomatics.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-22 | 2026-08-24 |\n| Terms last updated | 2018-05-24 | no date given |\n| Privacy policy last updated | 2024-05-15 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 8 stars, 512 PyPI/wk | 56 stars, 16k PyPI/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### meteoblue Weather API\n\n1. Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call\n2. 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\n3. Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has\n4. 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\n5. 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\n\n### Meteomatics Weather API\n\n1. 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\n2. 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\n3. 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\n4. Send credentials or the token in the `Authorization` header. Avoid the documented `access_token` query parameter, which puts the token in URLs and logs\n5. Read `/user_stats_json` before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent\n6. 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\n\n## Questions\n\n### Which is better for AI agents, meteoblue Weather API or Meteomatics Weather API?\n\nmeteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics.\n\n### Do meteoblue Weather API and Meteomatics Weather API need an API key?\n\nmeteoblue Weather API needs an API key. Meteomatics Weather API takes an API key or an OAuth sign-in.\n\n### Can an agent call meteoblue Weather API and Meteomatics Weather API without installing anything?\n\nYes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Meteomatics Weather API at https://api.meteomatics.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteoblue\", \"b\": \"meteomatics\"}`. From a terminal: `anchor compare meteoblue meteomatics`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteoblue.json and https://www.anchorterminal.com/api/v1/tools/meteomatics.json\n\n## Other comparisons with meteoblue Weather API or Meteomatics Weather API\n\n- [AccuWeather Core Weather API + MCP vs meteoblue Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.md)\n- [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md)\n- [Google Weather API (Maps Platform) vs meteoblue Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.md)\n- [Google Weather API (Maps Platform) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.md)\n- [Met Office Weather DataHub (Site Specific) vs meteoblue Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.md)\n- [Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.md)\n- [meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.md)\n- [meteoblue Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.md)\n- [meteoblue Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.md)\n- [meteoblue Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md)\n- [meteoblue Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)\n- [meteoblue Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.md)\n- [meteoblue Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.md)\n- [meteoblue Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-xweather.md)\n- [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md)\n- [Meteomatics Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md)\n- [Meteomatics Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.md)\n- [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md)\n- [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md)\n- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)\n- [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md)\n- [Meteomatics Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.md)\n- [Meteomatics Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-xweather.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "meteoblue Weather API vs Meteomatics Weather API", "url": "" } ], "description": "meteoblue Weather API scores 61.7 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 5 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics. Both do weather current. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "meteoblue Weather API C 61.7", "Meteomatics Weather API D 49.6", "scores" ], "h1": "meteoblue Weather API vs Meteomatics Weather API", "image": "https://www.anchorterminal.com/assets/og/compare-meteoblue-vs-meteomatics.png", "path": "/compare/meteoblue-vs-meteomatics", "published": "2026-10-01", "section": "tools", "title": "meteoblue Weather API vs Meteomatics Weather API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics" }, "tokens": { "markdown": 2850, "slim": 680 }, "version": 1 }