{ "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": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "weather-company", "name": "The Weather Company Data APIs", "vendor": "The Weather Company, LLC", "vendorUrl": "https://www.weathercompany.com", "kind": "http-api", "category": "weather", "summary": "The Weather Company Data APIs return current conditions, forecasts to 15 days, historical data, government alerts, imagery and aviation weather from the company behind weather.com. Access is by API key at `api.weather.com`, sold in packages to businesses.", "url": "https://www.anchorterminal.com/tools/weather-company", "markdownUrl": "https://www.anchorterminal.com/tools/weather-company.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/weather-company.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/weather-company.json", "license": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "transports": [ "http" ], "remoteUrl": "https://api.weather.com", "packages": [], "auth": "api-key", "authNotes": "An API key is required and is sent as the `apiKey` query parameter on every request. No header option is documented. Keys are not self-serve. A person requests a 30-day trial by form or contacts sales, the company provisions the key, and the key is read in the API customer portal after an invitation. Each key is entitled to the endpoints in the customer's package, and an endpoint outside it returns 401.", "pricing": "paid", "pricingNotes": "Standard package $500 a month on an annual plan for 1 million API calls. Enterprise plans and add-on packages are by quote, and overage is charged as the contract defines. A free 30-day trial allows 50,000 calls a day at 100 a minute, is requested by form and is limited to enterprise customers, so an agent cannot start without a person and sales approval (checked 2026-10-08).", "priceSummary": "$500 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer documentation, the API references or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.weather.com/docs/home", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "paid", "enterprise", "sales-led", "closed-source", "status-page", "api-key", "aviation", "air-quality" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 52.6, "grade": "D", "agentReady": false, "rank": 565, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 73, "schema": 67, "security": 48, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.", "bestFor": "A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales.", "strengths": [ "168 API reference sections on developer.weather.com are generated from OpenAPI documents, with enums, patterns, required fields, example responses and 13 response codes per operation.", "The Standard package covers current conditions, daily and hourly forecasts to 15 days, alerts from six national agencies, imagery, marine tiles, tides and air quality.", "History on Demand returns hourly gridded history at about 4 km from June 2015, in JSON, CSV or Parquet, with paging, field selection and a compact mode.", "The status page lists 16 components. Its feed shows nine incidents between 10 July and 8 October 2026, all rated minor or none.", "The Standard package price is public, $500 a month on an annual plan for 1 million calls, and the trial allows 50,000 calls a day for 30 days." ], "weaknesses": [ "No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.", "The API key is accepted only as the `apiKey` query parameter, so it appears in every request URL. No header option is documented.", "The website terms of use say they do not apply to the data APIs and point to separate terms, which we did not find published.", "Exceeding a rate limit returns 401, the same status as a missing key. No 429, Retry-After or backoff guidance is documented.", "No llms.txt, no downloadable OpenAPI file, no official SDK and no MCP server were found. Only one dated changelog entry appeared in 42 API references sampled." ], "agentNotes": [ "Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.", "Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.", "Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.", "Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.", "Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call." ], "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": 52.6 } ], "editorialScores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 73, "schema": 67, "security": 48, "transparency": 20 }, "provenanceScore": 77 }, "connect": { "http": "curl --compressed \"https://api.weather.com/v3/wx/forecast/daily/3day?geocode=33.74,-84.39\u0026units=e\u0026language=en-US\u0026format=json\u0026apiKey=$TWC_API_KEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/weather-company" }, "area": "domain-data", "unitPrices": [ { "item": "Standard package, annual plan", "unit": "month", "usd": 500, "note": "1 million API calls a month" }, { "item": "Call on Standard, at the plan cap", "unit": "1k-requests", "usd": 0.5, "note": "$500 over 1 million calls" } ], "provenance": { "legalEntity": "The Weather Company, LLC", "domain": "weather.com", "domainRegistered": "1994-08-09", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://weather.com/privacy/privacy-policy", "statusPage": "https://theweathercompanyapis.statuspage.io", "changelog": "", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy policy, effective 30 April 2026, names The Weather Company, LLC, 1001 Summit Boulevard NE, Brookhaven, GA 30319. Its section on data collection outside consumer products covers developer.weather.com enquiries and business customers.", "No terms document is given. The website terms of use (updated 16 April 2026) say they do not apply to the business data APIs, and the separate terms they refer to were not found on the pricing, trial or documentation pages.", "The API answers at api.weather.com and the documentation at developer.weather.com. The company site is www.weathercompany.com (registered 1998-03-24).", "weather.com/.well-known/security.txt gives a security contact and expires on 31 December 2026. www.weathercompany.com and developer.weather.com return 404 for the same path.", "RDAP for weather.com gives a registration date of 1994-08-09 and CSC Corporate Domains, Inc. as registrar.", "There is no central changelog. Each API reference has its own changelog section, most of them empty." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/weather-company.json", "live": { "slug": "weather-company", "probe": { "target": "https://api.weather.com", "method": "get", "lastAt": "2026-10-08T21:12:25.691314952Z", "lastOk": true, "lastStatus": 401, "lastMs": 19, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 23, "p95ms24h": 64, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://theweathercompanyapis.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:30.225974996Z" }, "updatedAt": "2026-10-08T21:12:25.691314952Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Meteomatics AG", "b": "The Weather Company, LLC", "name": "Vendor" }, { "a": "https://api.meteomatics.com", "b": "https://api.weather.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "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": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "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-09-14", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "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" } ], "faq": [ { "answer": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Meteomatics Weather API or The Weather Company Data APIs?" }, { "answer": "Meteomatics Weather API takes an API key or an OAuth sign-in. The Weather Company Data APIs needs an API key.", "question": "Do Meteomatics Weather API and The Weather Company Data APIs need an API key?" }, { "answer": "Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and The Weather Company Data APIs at https://api.weather.com.", "question": "Can an agent call Meteomatics Weather API and The Weather Company Data APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 80 against 54", "Security \u0026 auth, 54 against 48", "Maintenance \u0026 community, 42 against 36", "Transparency \u0026 trust, 59 against 49" ], "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, 73 against 34", "Payments \u0026 pricing, 20 against 0" ], "also": null, "goodFor": "A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales.", "slug": "weather-company", "watchFor": "No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form." } ], "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-weather-company.json", "title": "AccuWeather Core Weather API + MCP vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company" }, { "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-weather-company.json", "title": "Google Weather API (Maps Platform) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company" }, { "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-weather-company.json", "title": "Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company" }, { "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-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/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-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-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/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/pirate-weather-vs-weather-company.json", "title": "Pirate Weather vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.json", "title": "Tomorrow.io Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.json", "title": "Visual Crossing Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.json", "title": "The Weather Company Data APIs vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.json", "title": "The Weather Company Data APIs vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-xweather.json", "title": "The Weather Company Data APIs vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-xweather" } ], "scores": [ { "by": 39, "edge": "weather-company", "key": "reliability", "meteomatics": 34, "name": "Reliability", "weather-company": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "meteomatics", "key": "schema", "meteomatics": 71, "name": "Schema \u0026 documentation", "weather-company": 67, "weight": 13 }, { "by": 26, "edge": "meteomatics", "key": "ergonomics", "meteomatics": 80, "name": "Agent ergonomics", "weather-company": 54, "weight": 13 }, { "by": 6, "edge": "meteomatics", "key": "security", "meteomatics": 54, "name": "Security \u0026 auth", "weather-company": 48, "weight": 14 }, { "by": 20, "edge": "weather-company", "key": "payments", "meteomatics": 0, "name": "Payments \u0026 pricing", "weather-company": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "meteomatics", "key": "maintenance", "meteomatics": 42, "name": "Maintenance \u0026 community", "weather-company": 36, "weight": 7 }, { "by": 10, "edge": "meteomatics", "key": "transparency", "meteomatics": 59, "name": "Transparency \u0026 trust", "weather-company": 49, "weight": 7 } ], "summary": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. 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.", "weather-company": "A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company", "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md", "slim": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.min.md" }, "markdown": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. 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- The Weather Company Data APIs: grade D, 52.6/100, rank #565 of 722. Markdown https://www.anchorterminal.com/tools/weather-company.md · JSON https://www.anchorterminal.com/api/v1/tools/weather-company.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 54\n- Security \u0026 auth, 54 against 48\n- Maintenance \u0026 community, 42 against 36\n- Transparency \u0026 trust, 59 against 49\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n### The Weather Company Data APIs (D)\n\nGood for: A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales.\n\nAhead on:\n- Reliability, 73 against 34\n- Payments \u0026 pricing, 20 against 0\n\nWatch for: No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.\n\n\n## Score by category\n\n| Category | Weight | Meteomatics Weather API | The Weather Company Data APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 73 | The Weather Company Data APIs +39 |\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 | 54 | Meteomatics Weather API +26 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 48 | Meteomatics Weather API +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 20 | The Weather Company Data APIs +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 36 | Meteomatics Weather API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 49 | Meteomatics Weather API +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.6 · D** | **52.6 · D** | |\n\n## Facts side by side\n\n| Fact | Meteomatics Weather API | The Weather Company Data APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Meteomatics AG | The Weather Company, LLC |\n| Hosted endpoint | `https://api.meteomatics.com` | `https://api.weather.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published |\n| Tools exposed | 9 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-24 | 2026-09-14 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | couldn't be read |\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\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**The Weather Company Data APIs.** A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.\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### The Weather Company Data APIs\n\n1. Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.\n2. Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.\n3. Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.\n4. Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.\n5. Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call.\n\n## Questions\n\n### Which is better for AI agents, Meteomatics Weather API or The Weather Company Data APIs?\n\nThe Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Meteomatics Weather API and The Weather Company Data APIs need an API key?\n\nMeteomatics Weather API takes an API key or an OAuth sign-in. The Weather Company Data APIs needs an API key.\n\n### Can an agent call Meteomatics Weather API and The Weather Company Data APIs without installing anything?\n\nYes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and The Weather Company Data APIs at https://api.weather.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteomatics\", \"b\": \"weather-company\"}`. From a terminal: `anchor compare meteomatics weather-company`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/weather-company.json\n\n## Other comparisons with Meteomatics Weather API or The Weather Company Data APIs\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 The Weather Company Data APIs](https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.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 The Weather Company Data APIs](https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company.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 The Weather Company Data APIs](https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.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 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 The Weather Company Data APIs](https://www.anchorterminal.com/compare/nws-api-vs-weather-company.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- [Pirate Weather vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company.md)\n- [Tomorrow.io Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.md)\n- [Visual Crossing Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.md)\n- [The Weather Company Data APIs vs WeatherAPI.com](https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.md)\n- [The Weather Company Data APIs vs Weatherbit API](https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.md)\n- [The Weather Company Data APIs vs Xweather Weather API](https://www.anchorterminal.com/compare/weather-company-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 The Weather Company Data APIs", "url": "" } ], "description": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Meteomatics Weather API's 49.6 (D), and leads in 2 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do…", "facts": [ "Meteomatics Weather API D 49.6", "The Weather Company Data APIs D 52.6", "scores" ], "h1": "Meteomatics Weather API vs The Weather Company Data APIs", "image": "https://www.anchorterminal.com/assets/og/compare-meteomatics-vs-weather-company.png", "path": "/compare/meteomatics-vs-weather-company", "published": "2026-10-01", "section": "tools", "title": "Meteomatics Weather API vs The Weather Company Data APIs for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, "tokens": { "markdown": 2900, "slim": 780 }, "version": 1 }