{ "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": "Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing.", "b": { "slug": "nws-api", "name": "NOAA National Weather Service API (api.weather.gov)", "vendor": "National Weather Service", "vendorUrl": "https://www.weather.gov/documentation/services-web-api", "kind": "http-api", "category": "weather", "summary": "The US government's own forecast, alert and observation feed, free, keyless and public domain.", "url": "https://www.anchorterminal.com/tools/nws-api", "markdownUrl": "https://www.anchorterminal.com/tools/nws-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nws-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nws-api.json", "repo": "https://github.com/weather-gov/api", "license": "Public domain (data)", "transports": [ "http" ], "remoteUrl": "https://api.weather.gov", "packages": [], "auth": "none", "authNotes": "No key. A User-Agent header that identifies the application, ideally with a contact email, is required and requests without one are refused.", "pricing": "free", "pricingNotes": "Free. The rate limit isn't published but is described as generous for typical use, and a throttled request can be retried after about five seconds (https://www.weather.gov/documentation/services-web-api).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 310, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://www.weather.gov/documentation/services-web-api", "openapi": "https://api.weather.gov/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.alerts", "data.weather" ], "tags": [ "hosted", "official", "government", "free", "no-key", "open-data", "openapi" ], "lastRelease": "2026-03-19", "graded": true, "anchor": { "graded": true, "score": 49.6, "grade": "D", "agentReady": false, "rank": 605, "ranked": true, "rankOf": 722, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 8, "payments": 60, "reliability": 25, "schema": 67, "security": 53, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Free, no key and no account, with public domain data. US and territories only.", "bestFor": "The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.", "strengths": [ "Free, no key and no account, with public domain data", "Official watches, warnings and text products from the issuing agency, filterable by point, zone, event and severity", "OpenAPI 3.0 document and RFC 7807 error bodies", "Cache-Control and Last-Modified on every response, so conditional requests work" ], "weaknesses": [ "US and territories only", "Rate limit not published, and no status page or SLA", "No dated API change since 17 March 2026, and several 2026 forum questions unanswered", "No SDK, MCP server, llms.txt or security.txt" ], "agentNotes": [ "Set User-Agent to your app name and a contact email or the request is refused with 403", "Cache the /points response per coordinate. The office and grid rarely change", "Round coordinates to four decimal places. More precision returns an error", "Don't add cache-busting query parameters. Unknown parameters return 400", "Back off about five seconds after a throttled request and reuse the last good response" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4.5, "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": 66, "maintenance": 8, "payments": 60, "reliability": 25, "schema": 67, "security": 53, "transparency": 53 }, "provenanceScore": 72, "dataQualityScore": 67 }, "connect": { "http": "curl -H \"User-Agent: (myagent.example, ops@myagent.example)\" -H \"Accept: application/geo+json\" \"https://api.weather.gov/points/38.8894,-77.0352\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/nws-api" }, "area": "domain-data", "provenance": { "legalEntity": "National Weather Service, NOAA, U.S. Department of Commerce", "domain": "weather.gov", "domainRegistered": "1999-04-30", "official": true, "endpointOnVendorDomain": true, "terms": "https://www.weather.gov/disclaimer", "privacy": "https://www.weather.gov/privacy", "statusPage": "", "changelog": "https://www.weather.gov/documentation/services-web-api", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The disclaimer says NWS information is public domain unless noted, is supplied as is, and that the NWS name and identifier are trademarked.", "The privacy policy says the date, time and originating IP of each request are logged and may be kept indefinitely for security.", "www.weather.gov/.well-known/security.txt returns 404. The Department of Commerce vulnerability disclosure policy (version 2.0, 25 February 2026) covers internet-facing DOC systems and takes reports through Bugcrowd.", "The docs page carries a dated list of API changes. Wider service changes go out as NWS Service Change Notices and Public Information Statements.", "There's no status page. Outages are reported to NCO Tech Control, and the NCEP Senior Duty Meteorologist messages are the nearest public log." ], "score": 72 }, "dataQuality": { "coverage": "United States and its territories, on each forecast office's 2.5 km grid", "coverageRating": 2, "freshness": "Not stated per endpoint. Responses carry Cache-Control and Last-Modified so clients can see the age", "freshnessClass": "hourly", "history": "Recent station observations only. Climate records are at NOAA's NCEI, not this API", "historyYears": 0, "methodology": "https://www.weather.gov/documentation/services-web-api", "sourcesDisclosed": true, "licence": "Public domain", "licenceClass": "open", "standing": "The US federal weather service, issuer of official US watches and warnings", "standingClass": "statutory", "reuse": "Public domain and free for any lawful purpose. Cache and redistribute as you like, don't imply NWS endorsement, and note that works built mostly on NWS material can't claim copyright over it.", "score": 67, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nws-api.json", "live": { "slug": "nws-api", "probe": { "target": "https://api.weather.gov", "method": "get", "lastAt": "2026-10-08T21:12:17.09250558Z", "lastOk": true, "lastStatus": 200, "lastMs": 203, "authRequired": false, "uptime24h": 100, "uptime30d": 99.95, "p50ms24h": 199, "p95ms24h": 391, "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": 271 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "githubStars": 311, "securityTxt": { "url": "https://weather.gov/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:42.708901288Z" }, "pages": [ { "url": "https://www.weather.gov/documentation/services-web-api", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:31:32.323689074Z", "changedAt": "2026-10-08T18:31:32.323689074Z", "fingerprint": "de49bea1e355" }, { "url": "https://www.weather.gov/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:34.482708851Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "00331ba8517d" }, { "url": "https://www.weather.gov/disclaimer", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:30.140998287Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f32d8c8c8de4" } ], "updatedAt": "2026-10-08T21:12:17.09250558Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Meteomatics AG", "b": "National Weather Service", "name": "Vendor" }, { "a": "https://api.meteomatics.com", "b": "https://api.weather.gov", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Paid", "b": "Free", "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": "Public domain (data)", "name": "Licence" }, { "a": "9", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-03-19", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "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": "56 stars, 16k PyPI/wk", "b": "310 stars", "name": "Popularity" }, { "a": "none", "b": "4.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Meteomatics Weather API or NOAA National Weather Service API (api.weather.gov)?" }, { "answer": "Meteomatics Weather API takes an API key or an OAuth sign-in. NOAA National Weather Service API (api.weather.gov) needs no key.", "question": "Do Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) need an API key?" }, { "answer": "Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.", "question": "Can an agent call Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 34 against 25", "Agent ergonomics, 80 against 66", "Maintenance \u0026 community, 42 against 8" ], "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": [ "Payments \u0026 pricing, 60 against 0" ], "also": [ "No key needed to call it" ], "goodFor": "The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.", "slug": "nws-api", "watchFor": "US and territories only" } ], "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-nws-api.json", "title": "AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api" }, { "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-nws-api.json", "title": "Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-nws-api" }, { "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-nws-api.json", "title": "Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-nws-api" }, { "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-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/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" }, { "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/nws-api-vs-pirate-weather.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/nws-api-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-visual-crossing.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company.json", "title": "NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.json", "title": "NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weatherbit.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-xweather.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-xweather" } ], "scores": [ { "by": 9, "edge": "meteomatics", "key": "reliability", "meteomatics": 34, "name": "Reliability", "nws-api": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "meteomatics", "key": "schema", "meteomatics": 71, "name": "Schema \u0026 documentation", "nws-api": 67, "weight": 13 }, { "by": 14, "edge": "meteomatics", "key": "ergonomics", "meteomatics": 80, "name": "Agent ergonomics", "nws-api": 66, "weight": 13 }, { "by": 1, "edge": "meteomatics", "key": "security", "meteomatics": 54, "name": "Security \u0026 auth", "nws-api": 53, "weight": 14 }, { "by": 60, "edge": "nws-api", "key": "payments", "meteomatics": 0, "name": "Payments \u0026 pricing", "nws-api": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 34, "edge": "meteomatics", "key": "maintenance", "meteomatics": 42, "name": "Maintenance \u0026 community", "nws-api": 8, "weight": 7 }, { "by": 4, "edge": "nws-api", "key": "transparency", "meteomatics": 59, "name": "Transparency \u0026 trust", "nws-api": 63, "weight": 7 } ], "summary": "Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing. 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.", "nws-api": "Free, no key and no account, with public domain data. US and territories only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api", "json": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md", "slim": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.min.md" }, "markdown": "Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing. 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- NOAA National Weather Service API (api.weather.gov): grade D, 49.6/100, rank #605 of 722. Markdown https://www.anchorterminal.com/tools/nws-api.md · JSON https://www.anchorterminal.com/api/v1/tools/nws-api.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- Reliability, 34 against 25\n- Agent ergonomics, 80 against 66\n- Maintenance \u0026 community, 42 against 8\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n### NOAA National Weather Service API (api.weather.gov) (D)\n\nGood for: The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 0\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: US and territories only\n\n\n## Score by category\n\n| Category | Weight | Meteomatics Weather API | NOAA National Weather Service API (api.weather.gov) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 25 | Meteomatics Weather API +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 67 | Meteomatics Weather API +4 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 66 | Meteomatics Weather API +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 53 | Meteomatics Weather API +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 60 | NOAA National Weather Service API (api.weather.gov) +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 8 | Meteomatics Weather API +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 63 | NOAA National Weather Service API (api.weather.gov) +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.6 · D** | **49.6 · D** | |\n\n## Facts side by side\n\n| Fact | Meteomatics Weather API | NOAA National Weather Service API (api.weather.gov) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Meteomatics AG | National Weather Service |\n| Hosted endpoint | `https://api.meteomatics.com` | `https://api.weather.gov` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | None |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | Public domain (data) |\n| Tools exposed | 9 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-24 | 2026-03-19 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | no date given | 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 | 56 stars, 16k PyPI/wk | 310 stars |\n| Agent reviews | none | 4.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**NOAA National Weather Service API (api.weather.gov).** Free, no key and no account, with public domain data. US and territories only.\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### NOAA National Weather Service API (api.weather.gov)\n\n1. Set User-Agent to your app name and a contact email or the request is refused with 403\n2. Cache the /points response per coordinate. The office and grid rarely change\n3. Round coordinates to four decimal places. More precision returns an error\n4. Don't add cache-busting query parameters. Unknown parameters return 400\n5. Back off about five seconds after a throttled request and reuse the last good response\n\n## Questions\n\n### Which is better for AI agents, Meteomatics Weather API or NOAA National Weather Service API (api.weather.gov)?\n\nMeteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing.\n\n### Do Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) need an API key?\n\nMeteomatics Weather API takes an API key or an OAuth sign-in. NOAA National Weather Service API (api.weather.gov) needs no key.\n\n### Can an agent call Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) without installing anything?\n\nYes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteomatics\", \"b\": \"nws-api\"}`. From a terminal: `anchor compare meteomatics nws-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/nws-api.json\n\n## Other comparisons with Meteomatics Weather API or NOAA National Weather Service API (api.weather.gov)\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 NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api.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 NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/google-weather-api-vs-nws-api.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 NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/met-office-datahub-vs-nws-api.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-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- [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- [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- [NOAA National Weather Service API (api.weather.gov) vs Pirate Weather](https://www.anchorterminal.com/compare/nws-api-vs-pirate-weather.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/nws-api-vs-visual-crossing.md)\n- [NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/nws-api-vs-weather-company.md)\n- [NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com](https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Weatherbit API](https://www.anchorterminal.com/compare/nws-api-vs-weatherbit.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API](https://www.anchorterminal.com/compare/nws-api-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 NOAA National Weather Service API (api.weather.gov)", "url": "" } ], "description": "Meteomatics Weather API and NOAA National Weather Service API (api.weather.gov) score within a point of each other on agent readiness, 49.6 (D) and 49.6 (D). NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing. Both do weather current. Category…", "facts": [ "Meteomatics Weather API D 49.6", "NOAA National Weather Service API (api.weather.gov) D 49.6", "scores" ], "h1": "Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)", "image": "https://www.anchorterminal.com/assets/og/compare-meteomatics-vs-nws-api.png", "path": "/compare/meteomatics-vs-nws-api", "published": "2026-10-01", "section": "tools", "title": "Meteomatics Weather API vs NOAA National Weather Service API…", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api" }, "tokens": { "markdown": 2850, "slim": 680 }, "version": 1 }