Head to head · Weather current · October 2026 research run
meteoblue Weather API vs Tomorrow.io Weather API
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.
Which one, for what
Good 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.
Ahead on
- Reliability, 75 against 55
- Security & auth, 51 against 34
- Payments & pricing, 34 against 20
- Maintenance & community, 57 against 27
Watch for
The key is accepted only as the apikey query parameter, so it appears in URLs and logs unless request signing is switched on
Good for Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.
Ahead on
- Agent ergonomics, 73 against 66
Watch for
No public price for paid use. The plan table lists Free and Enterprise, the second by quote
Score by category
| Category | Weight this run | meteoblue Weather API | Tomorrow.io Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 55 | meteoblue Weather API +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 75 | meteoblue Weather API +2 |
| Agent ergonomics | 13%16.2 | 66 | 73 | Tomorrow.io Weather API +7 |
| Security & auth | 14%17.5 | 51 | 34 | meteoblue Weather API +17 |
| Payments & pricing | 10%12.5 | 34 | 20 | meteoblue Weather API +14 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 57 | 27 | meteoblue Weather API +30 |
| Transparency & trust | 7%8.8 | 61 | 63 | Tomorrow.io Weather API +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 61.7 · C | 51.4 · D |
Facts side by side
| Fact | meteoblue Weather API | Tomorrow.io Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | meteoblue AG | The Tomorrow Companies Inc. |
| Hosted endpoint | https://my.meteoblue.com | https://api.tomorrow.io/v4 |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| 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 |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-22 | 2026-07-14 |
| Terms last updated | 2018-05-24 | couldn't be read |
| Privacy policy last updated | 2024-05-15 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 8 stars, 512 PyPI/wk | none |
Verdicts
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.
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.
Before you call either
meteoblue Weather API
- Pass
lat,lonandapikeytohttps://my.meteoblue.com/packages/<package>. Join packages with commas, such asbasic-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-Accountedon each response - Set
forecastDaysand 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
expireandsigif URLs may be seen by others
Tomorrow.io Weather API
- Send the key in the
apikeyheader, not the query string, so it stays out of URLs and logs - Request only the
fieldsandtimestepsneeded on POST /timelines. Free plans cover 24 hours back and 5 days ahead at1hand1d - 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-Afteris 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
Questions
Which is better for AI agents, meteoblue Weather API or Tomorrow.io Weather API?
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.
Do meteoblue Weather API and Tomorrow.io Weather API need an API key?
meteoblue Weather API needs an API key. Tomorrow.io Weather API takes an API key or an OAuth sign-in.
Can an agent call meteoblue Weather API and Tomorrow.io Weather API without installing anything?
Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Tomorrow.io Weather API at https://api.tomorrow.io/v4.
Other comparisons with meteoblue Weather API or Tomorrow.io Weather API
- AccuWeather Core Weather API + MCP vs meteoblue Weather API
- AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs meteoblue Weather API
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs meteoblue Weather API
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- meteoblue Weather API vs Meteomatics Weather API
- meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)
- meteoblue Weather API vs OpenWeather One Call API
- meteoblue Weather API vs Pirate Weather
- meteoblue Weather API vs Visual Crossing Weather API
- meteoblue Weather API vs The Weather Company Data APIs
- meteoblue Weather API vs WeatherAPI.com
- meteoblue Weather API vs Weatherbit API
- meteoblue Weather API vs Xweather Weather API
- Meteomatics Weather API vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- OpenWeather One Call API vs Tomorrow.io Weather API
- Pirate Weather vs Tomorrow.io Weather API
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs The Weather Company Data APIs
- Tomorrow.io Weather API vs WeatherAPI.com
- Tomorrow.io Weather API vs Weatherbit API
- Tomorrow.io Weather API vs Xweather Weather API
Machine-readable
- This page as Markdown
/compare/meteoblue-vs-tomorrow-io.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/meteoblue.json·/api/v1/tools/tomorrow-io.json - From a terminal
anchor compare meteoblue tomorrow-io(the CLI) - Over MCP
compare_tools {"a": "meteoblue", "b": "tomorrow-io"}at/mcp, no key