Head to head · Weather current · October 2026 research run

Tomorrow.io Weather API vs Weatherbit API

Weatherbit API scores 57.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics and maintenance & community. Both do weather current.

Which one, for what

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

  • Agent ergonomics, 73 against 61
  • Maintenance & community, 27 against 21

Watch for

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

Weatherbit API C

Good for An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.

Ahead on

  • Reliability, 91 against 55
  • Security & auth, 39 against 34
  • Payments & pricing, 30 against 20

Also in its favour

  • Free to start without a card

Watch for

The key is accepted only as the key query parameter, and the spec lists plain http as a scheme

Score by category

CategoryWeight this runTomorrow.io Weather APIWeatherbit APIEdge
Reliability16%205591Weatherbit API +36
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27572Tomorrow.io Weather API +3
Agent ergonomics13%16.27361Tomorrow.io Weather API +12
Security & auth14%17.53439Weatherbit API +5
Payments & pricing10%12.52030Weatherbit API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82721Tomorrow.io Weather API +6
Transparency & trust7%8.86363even
Negative events≤1500
Total51.4 · D57.7 · C

Facts side by side

FactTomorrow.io Weather APIWeatherbit API
KindHTTP APIHTTP API
VendorThe Tomorrow Companies Inc.Weatherbit LLC
Hosted endpointhttps://api.tomorrow.io/v4https://api.weatherbit.io/v2.0
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Tomorrow.io's subscription termsProprietary 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
Tools exposed11none
Read-only variant documentednono
llms.txtyesno
Last release2026-07-142025-08-01
Terms last updatedcouldn't be read2025-05-01
Privacy policy last updatedcouldn't be read2023-12-26
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone78 PyPI/wk

Verdicts

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.

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.

Before you call either

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

Weatherbit API

  1. 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
  2. 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
  3. Treat HTTP 204 with an empty body as no data found, not as an error
  4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
  5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0

Questions

Which is better for AI agents, Tomorrow.io Weather API or Weatherbit API?

Weatherbit API scores 57.7 (C) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics and maintenance & community.

Do Tomorrow.io Weather API and Weatherbit API need an API key?

Tomorrow.io Weather API takes an API key or an OAuth sign-in. Weatherbit API needs an API key.

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

Yes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and Weatherbit API at https://api.weatherbit.io/v2.0.

Other comparisons with Tomorrow.io Weather API or Weatherbit 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.