{ "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": "Weatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "weatherbit", "name": "Weatherbit API", "vendor": "Weatherbit LLC", "vendorUrl": "https://www.weatherbit.io", "kind": "http-api", "category": "weather", "summary": "Weather data API from Weatherbit LLC of North Carolina. It returns current conditions, daily, hourly and minutely forecasts, severe weather alerts, historical weather, air quality and agricultural and energy datasets by coordinates, over HTTPS with an API key.", "url": "https://www.anchorterminal.com/tools/weatherbit", "markdownUrl": "https://www.anchorterminal.com/tools/weatherbit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/weatherbit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/weatherbit.json", "repo": "https://github.com/weatherbit/weatherbit-python", "license": "Proprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT", "transports": [ "http" ], "remoteUrl": "https://api.weatherbit.io/v2.0", "packages": [ { "registry": "pypi", "name": "pyweatherbit" } ], "auth": "api-key", "authNotes": "Self-serve key from a browser signup. The key goes in the `key` query parameter on every request, and no header option is documented. Free, Standard and Plus accounts have one key. Business has up to 10.", "pricing": "freemium", "pricingNotes": "Free plan at 50 requests a day for non-commercial use, and a 21-day Business trial with no card and up to 1,500 requests a day. Paid plans are monthly subscriptions with daily quotas and no overage price. The pricing page showed us pounds only, Standard £40, Plus £179 and Business £410 a month, Enterprise from £820. Billing can be in USD, EUR or GBP, and we did not see the dollar prices (https://www.weatherbit.io/pricing, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the Swagger spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 78, "asOf": "2026-10-08" }, "docsUrl": "https://www.weatherbit.io/api", "openapi": "https://www.weatherbit.io/static/swagger.json", "capabilities": [ "weather.current", "weather.forecast", "weather.alerts", "weather.historical", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "closed-source", "openapi", "python", "status-page", "us" ], "lastRelease": "2025-08-01", "graded": true, "anchor": { "graded": true, "score": 57.7, "grade": "C", "agentReady": false, "rank": 466, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 21, "payments": 30, "reliability": 91, "schema": 72, "security": 39, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.", "bestFor": "An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.", "strengths": [ "Status page with three API monitors, each at 100 per cent over the 90 days to 8 October 2026", "Swagger 2.0 spec at /static/swagger.json with 21 GET endpoints, typed response models and 400, 403, 429 and 500 bodies", "Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and /subscription/usage returns the same counters", "Daily and per-second limits published for every plan, from 50 a day on Free to 2 million a day on Business", "The privacy policy states that API request logs are kept for no more than two weeks" ], "weaknesses": [ "The key is accepted only as the `key` query parameter, and the spec lists plain http as a scheme", "Free plan is 50 requests a day, non-commercial, with a 7-day daily forecast and no hourly forecast or history", "The last dated API announcement on the blog is 1 August 2025, and the Python SDK was last released in February 2024", "No security.txt, disclosure policy, certification or DPA found on the site", "The terms let Weatherbit end access at any time without notice or reason, and no deprecation policy was found" ], "agentNotes": [ "Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution", "Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then", "Treat HTTP 204 with an empty body as no data found, not as an error", "Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota", "Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.7 } ], "editorialScores": { "ergonomics": 61, "maintenance": 21, "payments": 30, "reliability": 91, "schema": 72, "security": 39, "transparency": 42 }, "provenanceScore": 84 }, "connect": { "install": "pip install pyweatherbit", "http": "curl -s \"https://api.weatherbit.io/v2.0/forecast/daily?days=16\u0026key=API_KEY\u0026lat=35.7796\u0026lon=-78.6382\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/weatherbit" }, "area": "domain-data", "provenance": { "legalEntity": "Weatherbit LLC", "domain": "weatherbit.io", "domainRegistered": "2016-12-25", "endpointOnVendorDomain": true, "terms": "https://www.weatherbit.io/terms", "privacy": "https://www.weatherbit.io/privacy", "statusPage": "https://status.weatherbit.io", "changelog": "https://blog.weatherbit.io/tag/news/", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms (updated 1 May 2025) cover the Weatherbit API and the website in one document and name Weatherbit LLC, 921 Town Centre Blvd #1129, Clayton, NC 27520, under North Carolina law.", "The privacy policy (updated 26 December 2023) covers the site and the API, and says hosting is in the United States and Canada. The help centre says the API runs in North America and Europe, and our unauthenticated call answered with an api_region: EU header.", "www.weatherbit.io/.well-known/security.txt returns 404.", "status.weatherbit.io runs on UptimeRobot with three monitors, API Central, East and West.", "The changelog is the news tag of the vendor's blog. Its latest post is dated 1 August 2025.", "RDAP for weatherbit.io gives a registration date of 2016-12-25." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/weatherbit.json", "live": { "slug": "weatherbit", "probe": { "target": "https://api.weatherbit.io/v2.0", "method": "get", "lastAt": "2026-10-08T21:12:25.771503875Z", "lastOk": true, "lastStatus": 400, "lastMs": 93, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 95, "p95ms24h": 144, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-08", "probes": 41, "ok": 41 } ] }, "vendorStatus": { "page": "https://status.weatherbit.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:20.126331622Z" }, "pages": [ { "url": "https://blog.weatherbit.io/tag/news/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:15:50.177777534Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "427edce4e014" }, { "url": "https://www.weatherbit.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:33.789419573Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e20e5b8f5c6c" }, { "url": "https://www.weatherbit.io/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:35.93530729Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "05c1785284ba" }, { "url": "https://www.weatherbit.io/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:37.876349999Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5f7fdca11857" } ], "updatedAt": "2026-10-08T21:12:25.771503875Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Meteomatics AG", "b": "Weatherbit LLC", "name": "Vendor" }, { "a": "https://api.meteomatics.com", "b": "https://api.weatherbit.io/v2.0", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "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": "Proprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT", "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": "2025-08-01", "name": "Last release" }, { "a": "no date given", "b": "2025-05-01", "name": "Terms last updated" }, { "a": "no date given", "b": "2023-12-26", "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": "78 PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Weatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Meteomatics Weather API or Weatherbit API?" }, { "answer": "Meteomatics Weather API takes an API key or an OAuth sign-in. Weatherbit API needs an API key.", "question": "Do Meteomatics Weather API and Weatherbit API need an API key?" }, { "answer": "Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and Weatherbit API at https://api.weatherbit.io/v2.0.", "question": "Can an agent call Meteomatics Weather API and Weatherbit API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 80 against 61", "Security \u0026 auth, 54 against 39", "Maintenance \u0026 community, 42 against 21" ], "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, 91 against 34", "Payments \u0026 pricing, 30 against 0" ], "also": [ "Free to start without a card" ], "goodFor": "An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.", "slug": "weatherbit", "watchFor": "The key is accepted only as the `key` query parameter, and the spec lists plain http as a scheme" } ], "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-weatherbit.json", "title": "AccuWeather Core Weather API + MCP vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weatherbit" }, { "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-weatherbit.json", "title": "Google Weather API (Maps Platform) vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-weatherbit" }, { "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-weatherbit.json", "title": "Met Office Weather DataHub (Site Specific) vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weatherbit" }, { "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-weatherbit.json", "title": "meteoblue Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.json", "title": "Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.json", "title": "Meteomatics Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.json", "title": "Meteomatics Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json", "title": "Meteomatics Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.json", "title": "Meteomatics Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "title": "Meteomatics Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.json", "title": "Meteomatics Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-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-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/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/pirate-weather-vs-weatherbit.json", "title": "Pirate Weather vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.json", "title": "Tomorrow.io Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit.json", "title": "Visual Crossing Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit" }, { "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/weatherapi-com-vs-weatherbit.json", "title": "WeatherAPI.com vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/weatherapi-com-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/weatherbit-vs-xweather.json", "title": "Weatherbit API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/weatherbit-vs-xweather" } ], "scores": [ { "by": 57, "edge": "weatherbit", "key": "reliability", "meteomatics": 34, "name": "Reliability", "weatherbit": 91, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "weatherbit", "key": "schema", "meteomatics": 71, "name": "Schema \u0026 documentation", "weatherbit": 72, "weight": 13 }, { "by": 19, "edge": "meteomatics", "key": "ergonomics", "meteomatics": 80, "name": "Agent ergonomics", "weatherbit": 61, "weight": 13 }, { "by": 15, "edge": "meteomatics", "key": "security", "meteomatics": 54, "name": "Security \u0026 auth", "weatherbit": 39, "weight": 14 }, { "by": 30, "edge": "weatherbit", "key": "payments", "meteomatics": 0, "name": "Payments \u0026 pricing", "weatherbit": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 21, "edge": "meteomatics", "key": "maintenance", "meteomatics": 42, "name": "Maintenance \u0026 community", "weatherbit": 21, "weight": 7 }, { "by": 4, "edge": "weatherbit", "key": "transparency", "meteomatics": 59, "name": "Transparency \u0026 trust", "weatherbit": 63, "weight": 7 } ], "summary": "Weatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community. 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.", "weatherbit": "A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit", "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.md", "slim": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.min.md" }, "markdown": "Weatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community. 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- Weatherbit API: grade C, 57.7/100, rank #466 of 722. Markdown https://www.anchorterminal.com/tools/weatherbit.md · JSON https://www.anchorterminal.com/api/v1/tools/weatherbit.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 61\n- Security \u0026 auth, 54 against 39\n- Maintenance \u0026 community, 42 against 21\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n### Weatherbit API (C)\n\nGood for: An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.\n\nAhead on:\n- Reliability, 91 against 34\n- Payments \u0026 pricing, 30 against 0\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The key is accepted only as the `key` query parameter, and the spec lists plain http as a scheme\n\n\n## Score by category\n\n| Category | Weight | Meteomatics Weather API | Weatherbit API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 91 | Weatherbit API +57 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 72 | Weatherbit API +1 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 61 | Meteomatics Weather API +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 39 | Meteomatics Weather API +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 30 | Weatherbit API +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 21 | Meteomatics Weather API +21 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 63 | Weatherbit API +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.6 · D** | **57.7 · C** | |\n\n## Facts side by side\n\n| Fact | Meteomatics Weather API | Weatherbit API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Meteomatics AG | Weatherbit LLC |\n| Hosted endpoint | `https://api.meteomatics.com` | `https://api.weatherbit.io/v2.0` |\n| Transports | HTTP | 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 | Proprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT |\n| Tools exposed | 9 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-24 | 2025-08-01 |\n| Terms last updated | no date given | 2025-05-01 |\n| Privacy policy last updated | no date given | 2023-12-26 |\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 | 78 PyPI/wk |\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**Weatherbit API.** A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.\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### Weatherbit API\n\n1. Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution\n2. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then\n3. Treat HTTP 204 with an empty body as no data found, not as an error\n4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota\n5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0\n\n## Questions\n\n### Which is better for AI agents, Meteomatics Weather API or Weatherbit API?\n\nWeatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community.\n\n### Do Meteomatics Weather API and Weatherbit API need an API key?\n\nMeteomatics Weather API takes an API key or an OAuth sign-in. Weatherbit API needs an API key.\n\n### Can an agent call Meteomatics Weather API and Weatherbit API without installing anything?\n\nYes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and Weatherbit API at https://api.weatherbit.io/v2.0.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteomatics\", \"b\": \"weatherbit\"}`. From a terminal: `anchor compare meteomatics weatherbit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/weatherbit.json\n\n## Other comparisons with Meteomatics Weather API or Weatherbit 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 Weatherbit API](https://www.anchorterminal.com/compare/accuweather-api-vs-weatherbit.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 Weatherbit API](https://www.anchorterminal.com/compare/google-weather-api-vs-weatherbit.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 Weatherbit API](https://www.anchorterminal.com/compare/met-office-datahub-vs-weatherbit.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)\n- [meteoblue Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.md)\n- [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md)\n- [Meteomatics Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md)\n- [Meteomatics Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.md)\n- [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md)\n- [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md)\n- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)\n- [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md)\n- [Meteomatics Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-xweather.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Weatherbit API](https://www.anchorterminal.com/compare/nws-api-vs-weatherbit.md)\n- [OpenWeather One Call API vs Weatherbit API](https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherbit.md)\n- [Pirate Weather vs Weatherbit API](https://www.anchorterminal.com/compare/pirate-weather-vs-weatherbit.md)\n- [Tomorrow.io Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.md)\n- [Visual Crossing Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit.md)\n- [The Weather Company Data APIs vs Weatherbit API](https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.md)\n- [WeatherAPI.com vs Weatherbit API](https://www.anchorterminal.com/compare/weatherapi-com-vs-weatherbit.md)\n- [Weatherbit API vs Xweather Weather API](https://www.anchorterminal.com/compare/weatherbit-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 Weatherbit API", "url": "" } ], "description": "Weatherbit API scores 57.7 (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, security \u0026 auth and maintenance \u0026 community. Both do weather current. Category scores, facts…", "facts": [ "Meteomatics Weather API D 49.6", "Weatherbit API C 57.7", "scores" ], "h1": "Meteomatics Weather API vs Weatherbit API", "image": "https://www.anchorterminal.com/assets/og/compare-meteomatics-vs-weatherbit.png", "path": "/compare/meteomatics-vs-weatherbit", "published": "2026-10-01", "section": "tools", "title": "Meteomatics Weather API vs Weatherbit API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit" }, "tokens": { "markdown": 2800, "slim": 680 }, "version": 1 }