{ "data": { "a": { "slug": "meteoblue", "name": "meteoblue Weather API", "vendor": "meteoblue AG", "vendorUrl": "https://www.meteoblue.com", "kind": "http-api", "category": "weather", "summary": "Weather data APIs from meteoblue AG of Basel, Switzerland. The Forecast API returns point forecasts in packages by coordinates, with History, Warnings, Dataset, Image and Maps APIs beside it, over HTTPS with an API key.", "url": "https://www.anchorterminal.com/tools/meteoblue", "markdownUrl": "https://www.anchorterminal.com/tools/meteoblue.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteoblue.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteoblue.json", "repo": "https://github.com/meteoblue/python-dataset-sdk", "license": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "transports": [ "http" ], "remoteUrl": "https://my.meteoblue.com", "packages": [ { "registry": "pypi", "name": "meteoblue-dataset-sdk" } ], "auth": "api-key", "authNotes": "Self-serve key from a meteoblue account, created in a browser and managed in the Weather API Manager. The key goes in the `apikey` query parameter on every request, and no header option is documented. An account can hold several keys, each with a daily credit limit, an IP allow list, a referrer allow list and an optional shared secret for HMAC-SHA256 signed URLs. Paid plans start with an enquiry.", "pricing": "freemium", "pricingNotes": "Free Weather API with 10 million credits for one year from a free account, covering nine forecast packages, so an agent's owner can start without a contract. Calls cost 4,000 to 96,000 credits by package. The Premium Weather API is shown at EUR 2,400 a year for 40,000 calls a month, with larger tiers by enquiry. Prepaid credit prices are shown only after login (https://business.meteoblue.com/pricing, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI specs or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 8, "npmWeekly": null, "pypiWeekly": 512, "asOf": "2026-10-08" }, "docsUrl": "https://docs.meteoblue.com/en/weather-apis/introduction/overview", "llmsTxt": "https://business.meteoblue.com/llms.txt", "openapi": "https://my.meteoblue.com/packages/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "openapi", "llms-txt", "python", "status-page", "europe" ], "lastRelease": "2026-08-22", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 360, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 57, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.", "bestFor": "Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.", "strengths": [ "OpenAPI 3.1 specs for the Forecast (54 paths), History, Dataset, Image, Warnings, Measurements, Accounting and Model-Run Archive APIs, each at `openapi.json` beside its ReDoc page", "The Forecast API spec lists credits per package, 4,000 for `basic-day` and `current`, 8,000 for `basic-1h`, and each response carries an `MB-Credits-Accounted` header", "Free Weather API with 10 million credits for one year from a self-serve account, with no purchase obligation stated", "Keys can be limited by daily credits, IP range and referrer, or tied to an HMAC-SHA256 signature with an expiry time", "Pingdom status page with 15 monitors and monthly history. The Forecast API monitor shows one 2-minute outage in the 90 days to 8 October 2026" ], "weaknesses": [ "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on", "The free trial covers nine forecast packages at hourly or coarser steps. Current conditions, sea, history, warnings and the Dataset API need a paid plan", "No security.txt, disclosure policy, SOC 2 or ISO 27001 was found. The only certificate published is ISO 9001:2015", "The general terms date from 24 May 2018, give no API-specific clauses and let meteoblue change or revoke them at any time", "The History API monitor shows an outage of 1 hour 26 minutes on 1 September 2026, and the status page is served over plain http only" ], "agentNotes": [ "Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call", "Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read `MB-Credits-Accounted` on each response", "Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has", "Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute", "Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send `expire` and `sig` if URLs may be seen by others" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 66, "maintenance": 57, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 35 }, "provenanceScore": 87 }, "connect": { "install": "pip install meteoblue-dataset-sdk", "http": "curl \"https://my.meteoblue.com/packages/basic-1h?lat=47.5596\u0026lon=7.5886\u0026tz=utc\u0026apikey=YOUR_APIKEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/meteoblue" }, "area": "domain-data", "provenance": { "legalEntity": "meteoblue AG", "domain": "meteoblue.com", "domainRegistered": "2005-11-15", "endpointOnVendorDomain": true, "terms": "https://business.meteoblue.com/terms-conditions", "privacy": "https://business.meteoblue.com/privacy-policy", "statusPage": "http://status.meteoblue.com/", "changelog": "https://business.meteoblue.com/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms and conditions (last revised 24 May 2018) are meteoblue's general terms for all services, products and data, the API included. They name meteoblue AG, Basel, under Swiss law with Basel as forum. No separate API agreement is published, and commercial terms are agreed in writing.", "The privacy policy (last revised 15 May 2024) states that it applies to all meteoblue services however they are used, and names the website, apps and API. The same two texts are also served at content.meteoblue.com/en/about-us/legal/.", "The imprint gives meteoblue AG, Greifengasse 38, CH-4058 Basel, commercial register number CHE-113.182.626.", "The APIs answer at my.meteoblue.com, warnings-api.meteoblue.com and measurements-api.meteoblue.com, behind Cloudflare.", "/.well-known/security.txt returns 404 on www.meteoblue.com, my.meteoblue.com, business.meteoblue.com and docs.meteoblue.com, and 403 on content.meteoblue.com.", "status.meteoblue.com is a Pingdom public report with 15 monitors. It answers over http. Over https the certificate does not match the host name.", "The changelog is on the business site, 19 dated entries from 11 August 2025 to 22 August 2026, mostly data and model additions.", "RDAP for meteoblue.com gives a registration date of 2005-11-15." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteoblue.json", "live": { "slug": "meteoblue", "probe": { "target": "https://my.meteoblue.com", "method": "get", "lastAt": "2026-10-08T21:12:15.476668876Z", "lastOk": true, "lastStatus": 404, "lastMs": 68, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 68, "p95ms24h": 164, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "http://status.meteoblue.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:46.956747067Z" }, "updatedAt": "2026-10-08T21:12:15.476668876Z" } }, "answer": "meteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics.", "b": { "slug": "tomorrow-io", "name": "Tomorrow.io Weather API", "vendor": "The Tomorrow Companies Inc.", "vendorUrl": "https://www.tomorrow.io", "kind": "http-api", "category": "weather", "summary": "Tomorrow.io's Weather API returns current conditions, forecasts, recent and archived history, map tiles, route weather and alert webhooks for a coordinate, place name or GeoJSON shape. It is a REST API with a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/tomorrow-io", "markdownUrl": "https://www.anchorterminal.com/tools/tomorrow-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomorrow-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json", "license": "Proprietary service under Tomorrow.io's subscription terms", "transports": [ "http" ], "remoteUrl": "https://api.tomorrow.io/v4", "packages": [], "auth": "mixed", "authNotes": "A person signs up in a browser and copies the key from the dashboard. The key goes in an `apikey` header or query parameter on REST calls and in `X-Api-Key` for the MCP server. The docs say keys carry full privileges, and more keys are created by an account manager. The MCP endpoint also advertises OAuth with dynamic client registration, PKCE and one scope, `mcp:read`.", "pricing": "freemium", "pricingNotes": "Free plan with no published price for anything above it. Free covers core data layers, a 5-day forecast, 24 hours of history, one monitored location and one alert, and the terms bar commercial use on self-generated accounts. Enterprise is by quote and adds the 14-day forecast, premium layers, routes, maps and the historical archive, which is metered in tokens with no public token price (https://www.tomorrow.io/weather-api/, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the plan table (checked 2026-10-08).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.tomorrow.io/reference/welcome", "llmsTxt": "https://docs.tomorrow.io/llms.txt", "openapi": "https://docs.tomorrow.io/openapi/tomorrowio-api.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "openapi", "llms-txt", "mcp", "webhooks", "status-page", "sales-led", "us" ], "lastRelease": "2026-07-14", "graded": true, "anchor": { "graded": true, "score": 51.4, "grade": "D", "agentReady": false, "rank": 578, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 27, "payments": 20, "reliability": 55, "schema": 75, "security": 34, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public OpenAPI 3.1 file, Markdown docs with llms.txt and a hosted MCP server with 11 tools suit agents, and a free plan exists. Paid prices are by quote only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data.", "bestFor": "Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.", "strengths": [ "Public OpenAPI 3.1.0 file (version 4.0.1, 31 paths, 39 operations), plus llms.txt and a Markdown copy of every docs page", "Hosted MCP server at api.tomorrow.io/v4/tomorrow-weather/mcp with 11 documented tools, added in April 2026", "The `fields`, `timesteps`, `startTime` and `endTime` parameters size a Timelines response to what the task needs", "Six-digit error codes that the docs say stay fixed, and soft warnings returned beside partial data", "Alert webhooks signed with HMAC-SHA256 in an `X-Signature` header, retried up to two times" ], "weaknesses": [ "No public price for paid use. The plan table lists Free and Enterprise, the second by quote", "The subscription terms bar commercial use on self-generated accounts and forbid storing unaltered data without an order", "No numeric rate limits in the reviewed docs, and remaining-limit headers are documented for Enterprise accounts only", "Keys carry full privileges and may be sent as an `apikey` query parameter. More keys come through an account manager", "50 incidents on the status page between 15 July and 2 October 2026, 25 naming the Timeline or Historical API", "No official SDK, no security.txt, and no certification or disclosure policy found on the pages read" ], "agentNotes": [ "Send the key in the `apikey` header, not the query string, so it stays out of URLs and logs", "Request only the `fields` and `timesteps` needed on POST /timelines. Free plans cover 24 hours back and 5 days ahead at `1h` and `1d`", "Split archive requests. POST /historical takes at most 31 days per call and deducts tokens, 1 for a point and 10 for a polygon", "Treat 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026", "On 429 back off without a hint. `Retry-After` is documented only for 503", "Check the plan's terms before storing or reselling responses. Free accounts are limited to non-commercial use with a Powered by Tomorrow.io link" ], "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": 51.4 } ], "editorialScores": { "ergonomics": 73, "maintenance": 27, "payments": 20, "reliability": 55, "schema": 75, "security": 34, "transparency": 42 }, "provenanceScore": 84 }, "connect": { "http": "curl --request GET --url 'https://api.tomorrow.io/v4/weather/realtime?location=42.3478,-71.0466' --header 'apikey: API_KEY'", "config": { "mcpServers": { "tomorrow-weather-mcp": { "headers": { "X-Api-Key": "${TOMORROW_API_KEY}" }, "type": "http", "url": "https://api.tomorrow.io/v4/tomorrow-weather/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/tomorrow-io" }, "area": "domain-data", "provenance": { "legalEntity": "The Tomorrow Companies Inc.", "domain": "tomorrow.io", "domainRegistered": "2012-02-15", "endpointOnVendorDomain": true, "terms": "https://www.tomorrow.io/legal/terms-of-service/", "privacy": "https://www.tomorrow.io/legal/product-privacy-policy/", "statusPage": "https://status.tomorrow.io", "changelog": "https://docs.tomorrow.io/reference/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The subscription terms (last updated 19 October 2023) name The Tomorrow Companies Inc., a Delaware corporation with its principal place of business in Boston, Massachusetts, and cover the API, the dashboard and the data portal.", "The product privacy policy (last updated 17 December 2024) covers the API and platform and names Tomorrow.io Inc. as operator. The website has a separate privacy policy and terms of use, which we did not use here.", "The API and the MCP server answer at api.tomorrow.io.", "www.tomorrow.io, tomorrow.io and api.tomorrow.io each return 404 for /.well-known/security.txt.", "RDAP gives a registration date of 2012-02-15 for tomorrow.io. The status page runs on Atlassian Statuspage." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomorrow-io.json", "live": { "slug": "tomorrow-io", "probe": { "target": "https://api.tomorrow.io/v4", "method": "get", "lastAt": "2026-10-08T21:12:23.748190463Z", "lastOk": true, "lastStatus": 404, "lastMs": 136, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 152, "p95ms24h": 185, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-08", "probes": 41, "ok": 41 } ] }, "vendorStatus": { "page": "https://status.tomorrow.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:28.336264349Z" }, "pages": [ { "url": "https://docs.tomorrow.io/reference/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:37.617241436Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5c08804d147f" }, { "url": "https://www.tomorrow.io/legal/product-privacy-policy/", "kind": "privacy", "status": 0, "checkedAt": "2026-10-08T18:31:01.004304542Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true }, { "url": "https://www.tomorrow.io/legal/terms-of-service/", "kind": "terms", "status": 0, "checkedAt": "2026-10-08T18:31:01.446636319Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-10-08T21:12:23.748190463Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "meteoblue AG", "b": "The Tomorrow Companies Inc.", "name": "Vendor" }, { "a": "https://my.meteoblue.com", "b": "https://api.tomorrow.io/v4", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "b": "Proprietary service under Tomorrow.io's subscription terms", "name": "Licence" }, { "a": "none", "b": "11", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-22", "b": "2026-07-14", "name": "Last release" }, { "a": "2018-05-24", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2024-05-15", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "8 stars, 512 PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "meteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics.", "question": "Which is better for AI agents, meteoblue Weather API or Tomorrow.io Weather API?" }, { "answer": "meteoblue Weather API needs an API key. Tomorrow.io Weather API takes an API key or an OAuth sign-in.", "question": "Do meteoblue Weather API and Tomorrow.io Weather API need an API key?" }, { "answer": "Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Tomorrow.io Weather API at https://api.tomorrow.io/v4.", "question": "Can an agent call meteoblue Weather API and Tomorrow.io Weather API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 55", "Security \u0026 auth, 51 against 34", "Payments \u0026 pricing, 34 against 20", "Maintenance \u0026 community, 57 against 27" ], "also": null, "goodFor": "Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.", "slug": "meteoblue", "watchFor": "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on" }, { "aheadOn": [ "Agent ergonomics, 73 against 66" ], "also": null, "goodFor": "Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.", "slug": "tomorrow-io", "watchFor": "No public price for paid use. The plan table lists Free and Enterprise, the second by quote" } ], "job": { "capability": "weather.current", "name": "Weather current" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.json", "title": "AccuWeather Core Weather API + MCP vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.json", "title": "AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.json", "title": "Google Weather API (Maps Platform) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io.json", "title": "Google Weather API (Maps Platform) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.json", "title": "Met Office Weather DataHub (Site Specific) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io.json", "title": "Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io" }, { "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/meteoblue-vs-openweather-one-call.json", "title": "meteoblue Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.json", "title": "meteoblue Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.json", "title": "meteoblue Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.json", "title": "meteoblue Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.json", "title": "meteoblue Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.json", "title": "meteoblue Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-xweather.json", "title": "meteoblue Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-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/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/openweather-one-call-vs-tomorrow-io.json", "title": "OpenWeather One Call API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io.json", "title": "Pirate Weather vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.json", "title": "Tomorrow.io Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing" }, { "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/tomorrow-io-vs-weatherapi-com.json", "title": "Tomorrow.io Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com" }, { "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/tomorrow-io-vs-xweather.json", "title": "Tomorrow.io Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather" } ], "scores": [ { "by": 20, "edge": "meteoblue", "key": "reliability", "meteoblue": 75, "name": "Reliability", "tomorrow-io": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "meteoblue", "key": "schema", "meteoblue": 77, "name": "Schema \u0026 documentation", "tomorrow-io": 75, "weight": 13 }, { "by": 7, "edge": "tomorrow-io", "key": "ergonomics", "meteoblue": 66, "name": "Agent ergonomics", "tomorrow-io": 73, "weight": 13 }, { "by": 17, "edge": "meteoblue", "key": "security", "meteoblue": 51, "name": "Security \u0026 auth", "tomorrow-io": 34, "weight": 14 }, { "by": 14, "edge": "meteoblue", "key": "payments", "meteoblue": 34, "name": "Payments \u0026 pricing", "tomorrow-io": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "meteoblue", "key": "maintenance", "meteoblue": 57, "name": "Maintenance \u0026 community", "tomorrow-io": 27, "weight": 7 }, { "by": 2, "edge": "tomorrow-io", "key": "transparency", "meteoblue": 61, "name": "Transparency \u0026 trust", "tomorrow-io": 63, "weight": 7 } ], "summary": "meteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics. Both do weather current.", "verdicts": { "meteoblue": "Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.", "tomorrow-io": "A public OpenAPI 3.1 file, Markdown docs with llms.txt and a hosted MCP server with 11 tools suit agents, and a free plan exists. Paid prices are by quote only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io", "json": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md", "slim": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.min.md" }, "markdown": "meteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics. Both do weather current.\n\n- meteoblue Weather API: grade C, 61.7/100, rank #360 of 722. Markdown https://www.anchorterminal.com/tools/meteoblue.md · JSON https://www.anchorterminal.com/api/v1/tools/meteoblue.json\n- Tomorrow.io Weather API: grade D, 51.4/100, rank #578 of 722. Markdown https://www.anchorterminal.com/tools/tomorrow-io.md · JSON https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json\n\n## Which one, for what\n\n### meteoblue Weather API (C)\n\nGood for: Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.\n\nAhead on:\n- Reliability, 75 against 55\n- Security \u0026 auth, 51 against 34\n- Payments \u0026 pricing, 34 against 20\n- Maintenance \u0026 community, 57 against 27\n\nWatch for: The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on\n\n### Tomorrow.io Weather API (D)\n\nGood for: Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.\n\nAhead on:\n- Agent ergonomics, 73 against 66\n\nWatch for: No public price for paid use. The plan table lists Free and Enterprise, the second by quote\n\n\n## Score by category\n\n| Category | Weight | meteoblue Weather API | Tomorrow.io Weather API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 55 | meteoblue Weather API +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 75 | meteoblue Weather API +2 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 73 | Tomorrow.io Weather API +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 34 | meteoblue Weather API +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 34 | 20 | meteoblue Weather API +14 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 57 | 27 | meteoblue Weather API +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 63 | Tomorrow.io Weather API +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.7 · C** | **51.4 · D** | |\n\n## Facts side by side\n\n| Fact | meteoblue Weather API | Tomorrow.io Weather API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | meteoblue AG | The Tomorrow Companies Inc. |\n| Hosted endpoint | `https://my.meteoblue.com` | `https://api.tomorrow.io/v4` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT | Proprietary service under Tomorrow.io's subscription terms |\n| Tools exposed | none | 11 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-22 | 2026-07-14 |\n| Terms last updated | 2018-05-24 | couldn't be read |\n| Privacy policy last updated | 2024-05-15 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 8 stars, 512 PyPI/wk | none |\n\n## Verdicts\n\n**meteoblue Weather API.** Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.\n\n**Tomorrow.io Weather API.** A public OpenAPI 3.1 file, Markdown docs with llms.txt and a hosted MCP server with 11 tools suit agents, and a free plan exists. Paid prices are by quote only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data.\n\n## Before you call either\n\n### meteoblue Weather API\n\n1. Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call\n2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read `MB-Credits-Accounted` on each response\n3. Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has\n4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute\n5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send `expire` and `sig` if URLs may be seen by others\n\n### Tomorrow.io Weather API\n\n1. Send the key in the `apikey` header, not the query string, so it stays out of URLs and logs\n2. Request only the `fields` and `timesteps` needed on POST /timelines. Free plans cover 24 hours back and 5 days ahead at `1h` and `1d`\n3. Split archive requests. POST /historical takes at most 31 days per call and deducts tokens, 1 for a point and 10 for a polygon\n4. Treat 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026\n5. On 429 back off without a hint. `Retry-After` is documented only for 503\n6. Check the plan's terms before storing or reselling responses. Free accounts are limited to non-commercial use with a Powered by Tomorrow.io link\n\n## Questions\n\n### Which is better for AI agents, meteoblue Weather API or Tomorrow.io Weather API?\n\nmeteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics.\n\n### Do meteoblue Weather API and Tomorrow.io Weather API need an API key?\n\nmeteoblue Weather API needs an API key. Tomorrow.io Weather API takes an API key or an OAuth sign-in.\n\n### Can an agent call meteoblue Weather API and Tomorrow.io Weather API without installing anything?\n\nYes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Tomorrow.io Weather API at https://api.tomorrow.io/v4.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteoblue\", \"b\": \"tomorrow-io\"}`. From a terminal: `anchor compare meteoblue tomorrow-io`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteoblue.json and https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json\n\n## Other comparisons with meteoblue Weather API or Tomorrow.io Weather API\n\n- [AccuWeather Core Weather API + MCP vs meteoblue Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.md)\n- [AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.md)\n- [Google Weather API (Maps Platform) vs meteoblue Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.md)\n- [Google Weather API (Maps Platform) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io.md)\n- [Met Office Weather DataHub (Site Specific) vs meteoblue Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.md)\n- [Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io.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- [meteoblue Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.md)\n- [meteoblue Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.md)\n- [meteoblue Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)\n- [meteoblue Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.md)\n- [meteoblue Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.md)\n- [meteoblue Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-xweather.md)\n- [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.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- [OpenWeather One Call API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.md)\n- [Pirate Weather vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io.md)\n- [Tomorrow.io Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.md)\n- [Tomorrow.io Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.md)\n- [Tomorrow.io Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.md)\n- [Tomorrow.io Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.md)\n- [Tomorrow.io Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "meteoblue Weather API vs Tomorrow.io Weather API", "url": "" } ], "description": "meteoblue Weather API scores 61.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 5 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics. Both do weather current. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "meteoblue Weather API C 61.7", "Tomorrow.io Weather API D 51.4", "scores" ], "h1": "meteoblue Weather API vs Tomorrow.io Weather API", "image": "https://www.anchorterminal.com/assets/og/compare-meteoblue-vs-tomorrow-io.png", "path": "/compare/meteoblue-vs-tomorrow-io", "published": "2026-10-01", "section": "tools", "title": "meteoblue Weather API vs Tomorrow.io Weather API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io" }, "tokens": { "markdown": 2750, "slim": 730 }, "version": 1 }