{ "data": { "a": { "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" } }, "answer": "OpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth.", "b": { "slug": "openweather-one-call", "name": "OpenWeather One Call API", "vendor": "OpenWeather", "vendorUrl": "https://openweathermap.org", "kind": "http-api", "category": "weather", "summary": "Current weather, minute, hourly and daily forecasts, government alerts and history back to 1979 in one call, billed per call with 1,000 free a day.", "url": "https://www.anchorterminal.com/tools/openweather-one-call", "markdownUrl": "https://www.anchorterminal.com/tools/openweather-one-call.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openweather-one-call.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openweather-one-call.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.openweathermap.org/data/3.0/onecall", "packages": [], "auth": "api-key", "authNotes": "The REST API takes the key as the appid query parameter, so it lands in request URLs and logs. The agent lane at agents.openweathermap.org issues a separate data key (bf_live_…) sent as a Bearer header to data.openweathermap.org and to the MCP server. The One Call by Call subscription has to be activated on the account before the key works on 3.0 or 4.0.", "pricing": "freemium", "pricingNotes": "One Call by Call. The first 1,000 calls a day are free, then $0.0015 a call, with a default daily cap of 2,000 you can raise or lower in the account (https://openweathermap.org/price). Charges are summed and billed at the end of the subscription month, and subscribing means filling in a billing form (https://openweathermap.org/faq). The agent lane gives every account 1,000 One Call credits a day, replaced each night UTC, then bills $0.001 a successful call from prepaid credit. Top-ups are card only, from $10, and a person completes them on the payment page (https://agents.openweathermap.org/llms.txt). The wider subscription plans (Startup $40, Developer $180, Professional $470, Expert $1,200 a month) cover the older per-product APIs, not One Call.", "priceSummary": "$1.50 / 1k req", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://openweathermap.org/api/one-call-3", "llmsTxt": "https://openweathermap.org/llms.txt", "registryName": "org.openweathermap/agents", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "llms-txt", "closed-source", "usage-priced", "uk" ], "graded": true, "anchor": { "graded": true, "score": 57.4, "grade": "C", "agentReady": false, "rank": 474, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 60, "payments": 60, "reliability": 45, "schema": 68, "security": 42, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.", "bestFor": "Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key.", "strengths": [ "1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane", "An agent can sign up with one POST and an email, and failed calls aren't billed on that lane", "Official hosted MCP server in the registry as org.openweathermap/agents", "History back to 1979-01-01 from the same API as the forecast", "llms.txt, a Markdown agent guide and an error dictionary with the reaction for each code" ], "weaknesses": [ "The main API takes the key only as the appid query parameter", "3.0 is marked deprecated with no shutdown date, and 4.0 needs new paths", "No status page, public changelog or OpenAPI for the main API", "No security.txt or disclosure policy found", "Agent top-ups are card only and need a person, and the lane is run by Extreme Electronics Ltd" ], "agentNotes": [ "Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once", "Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance", "On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop", "Pass units=metric. The default is Kelvin", "Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.4 } ], "editorialScores": { "ergonomics": 73, "maintenance": 60, "payments": 60, "reliability": 45, "schema": 68, "security": 42, "transparency": 53 }, "provenanceScore": 69, "dataQualityScore": 52 }, "connect": { "http": "curl \"https://api.openweathermap.org/data/3.0/onecall?lat=51.51\u0026lon=-0.13\u0026exclude=minutely\u0026units=metric\u0026appid=$OPENWEATHER_API_KEY\"", "claudeCode": "claude mcp add --transport http openweather https://mcp.openweathermap.org/mcp --header \"Authorization: Bearer $OPENWEATHER_DATA_KEY\"", "config": { "mcpServers": { "openweather": { "headers": { "Authorization": "Bearer ${OPENWEATHER_DATA_KEY}" }, "type": "http", "url": "https://mcp.openweathermap.org/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/openweather-one-call" }, "area": "domain-data", "unitPrices": [ { "item": "One Call by Call, above 1,000 a day", "unit": "1k-requests", "usd": 1.5, "note": "$0.0015 a call, first 1,000 a day free" }, { "item": "Agent lane, prepaid credit", "unit": "1k-requests", "usd": 1, "note": "1 credit = $0.001 a successful call, 1,000 free credits a day, $10 minimum top-up" } ], "provenance": { "legalEntity": "OpenWeather Ltd", "domain": "openweathermap.org", "domainRegistered": "2012-04-20", "endpointOnVendorDomain": true, "terms": "https://openweather.co.uk/storage/app/media/Terms/Openweather_terms_and_conditions_of_sale.pdf", "privacy": "https://openweather.co.uk/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The terms of sale and privacy policy sit on openweather.co.uk and name OpenWeather Ltd at 30 St Mary Axe, London EC3A 8BF, under the law of England and Wales.", "The agent lane is operated by Extreme Electronics Ltd, trading as The Bot Forum, with its own versioned terms at agents.openweathermap.org/tos.", "openweathermap.org/.well-known/security.txt returns 404.", "The company's GitHub organisation holds a storage engine (Deker) and an awesome list, no SDK or MCP source." ], "score": 69 }, "dataQuality": { "coverage": "Global, any coordinate, from OpenWeather's own model blend", "coverageRating": 4, "freshness": "Not stated for One Call by Call. The subscription table lists updates every 2 hours on Startup, hourly on Developer and every 10 minutes on Professional and Expert", "freshnessClass": "hourly", "history": "Timemachine from 1979-01-01", "historyYears": 47, "methodology": "", "sourcesDisclosed": false, "licence": "CC BY-SA 4.0 and ODbL per the terms of sale, with attribution on lower plans", "licenceClass": "clear", "standing": "", "standingClass": "none", "reuse": "The terms of sale put the data under CC BY-SA 4.0 and ODbL, so caching and redistribution are allowed with attribution and share-alike. The FAQ adds a required credit line, link and logo for Free to Professional plans.", "score": 52, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openweather-one-call.json", "live": { "slug": "openweather-one-call", "probe": { "target": "https://api.openweathermap.org/data/3.0/onecall", "method": "get", "lastAt": "2026-10-08T21:12:17.733542412Z", "lastOk": true, "lastStatus": 401, "lastMs": 87, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 86, "p95ms24h": 126, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "versions": [ { "registry": "mcp-registry", "name": "org.openweathermap/agents", "version": "0.3.0", "seenAt": "2026-10-08T02:42:52.272076636Z" } ], "securityTxt": { "url": "https://openweathermap.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:35.212356314Z" }, "llmsTxt": { "url": "https://openweathermap.org/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:43.800574256Z" }, "domain": { "domain": "openweathermap.org", "registered": "2012-04-20", "source": "https://rdap.publicinterestregistry.org/rdap/domain/openweathermap.org", "checkedAt": "2026-10-04T13:10:39.925519614Z" }, "pages": [ { "url": "https://openweathermap.org/price", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:22:41.570194601Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "688045af7eab" }, { "url": "https://openweather.co.uk/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:22:39.654222195Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "763a8b8a9767" } ], "updatedAt": "2026-10-08T21:12:17.733542412Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Meteomatics AG", "b": "OpenWeather", "name": "Vendor" }, { "a": "https://api.meteomatics.com", "b": "https://api.openweathermap.org/data/3.0/onecall", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT", "b": "none", "name": "Licence" }, { "a": "9", "b": "6", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "org.openweathermap/agents", "name": "MCP registry" }, { "a": "2026-08-24", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "", "name": "Terms last updated" }, { "a": "no date given", "b": "2022-07-18", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "56 stars, 16k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Meteomatics Weather API or OpenWeather One Call API?" }, { "answer": "Meteomatics Weather API takes an API key or an OAuth sign-in. OpenWeather One Call API needs an API key.", "question": "Do Meteomatics Weather API and OpenWeather One Call API need an API key?" }, { "answer": "Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and OpenWeather One Call API at https://api.openweathermap.org/data/3.0/onecall.", "question": "Can an agent call Meteomatics Weather API and OpenWeather One Call API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 80 against 73", "Security \u0026 auth, 54 against 42" ], "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" }, { "aheadOn": [ "Reliability, 45 against 34", "Payments \u0026 pricing, 60 against 0", "Maintenance \u0026 community, 60 against 42" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key.", "slug": "openweather-one-call", "watchFor": "The main API takes the key only as the appid query parameter" } ], "job": { "capability": "weather.current", "name": "Weather current" }, "others": [ { "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/accuweather-api-vs-openweather-one-call.json", "title": "AccuWeather Core Weather API + MCP vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-openweather-one-call" }, { "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/google-weather-api-vs-openweather-one-call.json", "title": "Google Weather API (Maps Platform) vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-openweather-one-call" }, { "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/met-office-datahub-vs-openweather-one-call.json", "title": "Met Office Weather DataHub (Site Specific) vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.json", "title": "meteoblue Weather API vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics" }, { "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/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-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" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-openweather-one-call.json", "title": "NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-pirate-weather.json", "title": "OpenWeather One Call API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.json", "title": "OpenWeather One Call API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing.json", "title": "OpenWeather One Call API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.json", "title": "OpenWeather One Call API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com.json", "title": "OpenWeather One Call API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherbit.json", "title": "OpenWeather One Call API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-xweather.json", "title": "OpenWeather One Call API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-xweather" } ], "scores": [ { "by": 11, "edge": "openweather-one-call", "key": "reliability", "meteomatics": 34, "name": "Reliability", "openweather-one-call": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "meteomatics", "key": "schema", "meteomatics": 71, "name": "Schema \u0026 documentation", "openweather-one-call": 68, "weight": 13 }, { "by": 7, "edge": "meteomatics", "key": "ergonomics", "meteomatics": 80, "name": "Agent ergonomics", "openweather-one-call": 73, "weight": 13 }, { "by": 12, "edge": "meteomatics", "key": "security", "meteomatics": 54, "name": "Security \u0026 auth", "openweather-one-call": 42, "weight": 14 }, { "by": 60, "edge": "openweather-one-call", "key": "payments", "meteomatics": 0, "name": "Payments \u0026 pricing", "openweather-one-call": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 18, "edge": "openweather-one-call", "key": "maintenance", "meteomatics": 42, "name": "Maintenance \u0026 community", "openweather-one-call": 60, "weight": 7 }, { "by": 2, "edge": "openweather-one-call", "key": "transparency", "meteomatics": 59, "name": "Transparency \u0026 trust", "openweather-one-call": 61, "weight": 7 } ], "summary": "OpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth. Both do weather current.", "verdicts": { "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.", "openweather-one-call": "1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call", "json": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md", "slim": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.min.md" }, "markdown": "OpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth. Both do weather current.\n\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- OpenWeather One Call API: grade C, 57.4/100, rank #474 of 722. Markdown https://www.anchorterminal.com/tools/openweather-one-call.md · JSON https://www.anchorterminal.com/api/v1/tools/openweather-one-call.json\n\n## Which one, for what\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 73\n- Security \u0026 auth, 54 against 42\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n### OpenWeather One Call API (C)\n\nGood for: Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key.\n\nAhead on:\n- Reliability, 45 against 34\n- Payments \u0026 pricing, 60 against 0\n- Maintenance \u0026 community, 60 against 42\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The main API takes the key only as the appid query parameter\n\n\n## Score by category\n\n| Category | Weight | Meteomatics Weather API | OpenWeather One Call API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 45 | OpenWeather One Call API +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 68 | Meteomatics Weather API +3 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 73 | Meteomatics Weather API +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 42 | Meteomatics Weather API +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 60 | OpenWeather One Call API +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 60 | OpenWeather One Call API +18 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 61 | OpenWeather One Call API +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.6 · D** | **57.4 · C** | |\n\n## Facts side by side\n\n| Fact | Meteomatics Weather API | OpenWeather One Call API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Meteomatics AG | OpenWeather |\n| Hosted endpoint | `https://api.meteomatics.com` | `https://api.openweathermap.org/data/3.0/onecall` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | none |\n| Tools exposed | 9 | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `org.openweathermap/agents` |\n| Last release | 2026-08-24 | none |\n| Terms last updated | no date given | |\n| Privacy policy last updated | no date given | 2022-07-18 |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 56 stars, 16k PyPI/wk | none |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\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**OpenWeather One Call API.** 1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.\n\n## Before you call either\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### OpenWeather One Call API\n\n1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once\n2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance\n3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop\n4. Pass units=metric. The default is Kelvin\n5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses\n\n## Questions\n\n### Which is better for AI agents, Meteomatics Weather API or OpenWeather One Call API?\n\nOpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth.\n\n### Do Meteomatics Weather API and OpenWeather One Call API need an API key?\n\nMeteomatics Weather API takes an API key or an OAuth sign-in. OpenWeather One Call API needs an API key.\n\n### Can an agent call Meteomatics Weather API and OpenWeather One Call API without installing anything?\n\nYes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and OpenWeather One Call API at https://api.openweathermap.org/data/3.0/onecall.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteomatics\", \"b\": \"openweather-one-call\"}`. From a terminal: `anchor compare meteomatics openweather-one-call`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/openweather-one-call.json\n\n## Other comparisons with Meteomatics Weather API or OpenWeather One Call API\n\n- [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md)\n- [AccuWeather Core Weather API + MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/accuweather-api-vs-openweather-one-call.md)\n- [Google Weather API (Maps Platform) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.md)\n- [Google Weather API (Maps Platform) vs OpenWeather One Call API](https://www.anchorterminal.com/compare/google-weather-api-vs-openweather-one-call.md)\n- [Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.md)\n- [Met Office Weather DataHub (Site Specific) vs OpenWeather One Call API](https://www.anchorterminal.com/compare/met-office-datahub-vs-openweather-one-call.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)\n- [meteoblue Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.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 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- [NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API](https://www.anchorterminal.com/compare/nws-api-vs-openweather-one-call.md)\n- [OpenWeather One Call API vs Pirate Weather](https://www.anchorterminal.com/compare/openweather-one-call-vs-pirate-weather.md)\n- [OpenWeather One Call API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.md)\n- [OpenWeather One Call API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing.md)\n- [OpenWeather One Call API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.md)\n- [OpenWeather One Call API vs WeatherAPI.com](https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com.md)\n- [OpenWeather One Call API vs Weatherbit API](https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherbit.md)\n- [OpenWeather One Call API vs Xweather Weather API](https://www.anchorterminal.com/compare/openweather-one-call-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": "Meteomatics Weather API vs OpenWeather One Call API", "url": "" } ], "description": "OpenWeather One Call API scores 57.4 (C) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics and security \u0026 auth. Both do weather current. Category scores, facts, verdicts and…", "facts": [ "Meteomatics Weather API D 49.6", "OpenWeather One Call API C 57.4", "scores" ], "h1": "Meteomatics Weather API vs OpenWeather One Call API", "image": "https://www.anchorterminal.com/assets/og/compare-meteomatics-vs-openweather-one-call.png", "path": "/compare/meteomatics-vs-openweather-one-call", "published": "2026-10-01", "section": "tools", "title": "Meteomatics Weather API vs OpenWeather One Call API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call" }, "tokens": { "markdown": 2800, "slim": 780 }, "version": 1 }