# Meteomatics Weather API vs Tomorrow.io Weather API

> Tomorrow.io Weather API scores 51.4 (D) 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 & auth and maintenance & community. Both do weather current. Category scores…

- Canonical: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io
- Markdown: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md (~2,850 tokens)
- Slim: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Tomorrow.io Weather API scores 51.4 (D) 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 & auth and maintenance & community. Both do weather current.

- 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
- 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

## Which one, for what

### Meteomatics Weather API (D)

Good 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.

Ahead on:
- Agent ergonomics, 80 against 73
- Security & auth, 54 against 34
- Maintenance & community, 42 against 27

Watch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation

### Tomorrow.io Weather API (D)

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:
- Reliability, 55 against 34
- Payments & pricing, 20 against 0

Watch for: No public price for paid use. The plan table lists Free and Enterprise, the second by quote


## Score by category

| Category | Weight | Meteomatics Weather API | Tomorrow.io Weather API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 34 | 55 | Tomorrow.io Weather API +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 75 | Tomorrow.io Weather API +4 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 73 | Meteomatics Weather API +7 |
| Security & auth | 14% (17.5 this run) | 54 | 34 | Meteomatics Weather API +20 |
| Payments & pricing | 10% (12.5 this run) | 0 | 20 | Tomorrow.io Weather API +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 42 | 27 | Meteomatics Weather API +15 |
| Transparency & trust | 7% (8.8 this run) | 59 | 63 | Tomorrow.io Weather API +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **49.6 · D** | **51.4 · D** | |

## Facts side by side

| Fact | Meteomatics Weather API | Tomorrow.io Weather API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Meteomatics AG | The Tomorrow Companies Inc. |
| Hosted endpoint | `https://api.meteomatics.com` | `https://api.tomorrow.io/v4` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | Proprietary service under Tomorrow.io's subscription terms |
| Tools exposed | 9 | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-24 | 2026-07-14 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | 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 | 56 stars, 16k PyPI/wk | none |

## Verdicts

**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.

**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

### Meteomatics Weather API

1. 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
2. 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
3. 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
4. Send credentials or the token in the `Authorization` header. Avoid the documented `access_token` query parameter, which puts the token in URLs and logs
5. Read `/user_stats_json` before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent
6. 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

### Tomorrow.io Weather API

1. Send the key in the `apikey` header, not the query string, so it stays out of URLs and logs
2. Request only the `fields` and `timesteps` needed on POST /timelines. Free plans cover 24 hours back and 5 days ahead at `1h` and `1d`
3. Split archive requests. POST /historical takes at most 31 days per call and deducts tokens, 1 for a point and 10 for a polygon
4. Treat 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026
5. On 429 back off without a hint. `Retry-After` is documented only for 503
6. 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, Meteomatics Weather API or Tomorrow.io Weather API?

Tomorrow.io Weather API scores 51.4 (D) 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 & auth and maintenance & community.

### Do Meteomatics Weather API and Tomorrow.io Weather API need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Meteomatics Weather API and Tomorrow.io Weather API without installing anything?

Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and Tomorrow.io Weather API at https://api.tomorrow.io/v4.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "meteomatics", "b": "tomorrow-io"}`. From a terminal: `anchor compare meteomatics tomorrow-io`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json

## Other comparisons with Meteomatics Weather API or Tomorrow.io Weather API

- [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md)
- [AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.md)
- [Google Weather API (Maps Platform) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.md)
- [Google Weather API (Maps Platform) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io.md)
- [Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.md)
- [Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io.md)
- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)
- [meteoblue Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md)
- [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md)
- [Meteomatics Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md)
- [Meteomatics Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.md)
- [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md)
- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)
- [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md)
- [Meteomatics Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.md)
- [Meteomatics Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-xweather.md)
- [NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.md)
- [OpenWeather One Call API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.md)
- [Pirate Weather vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io.md)
- [Tomorrow.io Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.md)
- [Tomorrow.io Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.md)
- [Tomorrow.io Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.md)
- [Tomorrow.io Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.md)
- [Tomorrow.io Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather.md)