Get an audit

Head to head · Weather current · October 2026 research run

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.

Meteomatics Weather APIMeteomatics AG · HTTP API D49.6/100#606 of 722 Tomorrow.io Weather APIThe Tomorrow Companies Inc. · HTTP API D51.4/100#578 of 722

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

CategoryWeight this runMeteomatics Weather APITomorrow.io Weather APIEdge
Reliability16%203455Tomorrow.io Weather API +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27175Tomorrow.io Weather API +4
Agent ergonomics13%16.28073Meteomatics Weather API +7
Security & auth14%17.55434Meteomatics Weather API +20
Payments & pricing10%12.5020Tomorrow.io Weather API +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84227Meteomatics Weather API +15
Transparency & trust7%8.85963Tomorrow.io Weather API +4
Negative events≤1500
Total49.6 · D51.4 · D

Facts side by side

FactMeteomatics Weather APITomorrow.io Weather API
KindHTTP APIHTTP API
VendorMeteomatics AGThe Tomorrow Companies Inc.
Hosted endpointhttps://api.meteomatics.comhttps://api.tomorrow.io/v4
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MITProprietary service under Tomorrow.io's subscription terms
Tools exposed911
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-242026-07-14
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity56 stars, 16k PyPI/wknone

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.

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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report