Head to head · Current weather · October 2026 research run
Tomorrow.io Weather API vs WeatherAPI.com
WeatherAPI.com scores 66.5 (B) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in every scored category. Both do current weather.
Best weather and climate data APIs for AI agents · All 136 weather comparisons
Which one, for what
Best for Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public price for paid use. The plan table lists Free and Enterprise, the second by quote
Best for Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.
Ahead on
- Reliability, 80 against 60
- Schema & documentation, 89 against 75
- Agent ergonomics, 80 against 73
- Payments & pricing, 45 against 30
- Maintenance & community, 60 against 27
- Transparency & trust, 65 against 53
Also in its favour
- Free to start without a card
Watch for
Key only in the query string, keys can't be scoped, and no security.txt
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community WeatherAPI.com +33
Tomorrow.io Weather API 27
The newest release-note entry is October 2026, dated by month only, with the Bulk Timelines API, Density Altitude and new probability layers, a Dew Point Depression core layer and new aviation altitudes. A month-only entry is dated to its month, and October runs 4 to 34 days back, so it can't show a change within 30 days (20). The page was last updated on 13 October 2026, and the 8 October check saw July as the newest entry. That is one dated entry since 6 August, not three (0). Release notes with five entries in thirteen months, a status page updated several times a week, and a help centre that answered 403 on 8 October, not re-read. The community repository on GitHub was last pushed in April 2021, per the 8 October check (7 of 15). No official SDK, and no registry presence read in this run (0). No packages to assess (0). 20 + 0 + 7 + 0 + 0 = 27.
WeatherAPI.com 60
The changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60.
Reliability WeatherAPI.com +20
Tomorrow.io Weather API 60
Graded as a hosted service. Status page at status.tomorrow.io on Atlassian Statuspage, with 22 components on its history page, among them Timeline API, Historical API, Alerts API and Gale AI (20). The history pages list 37 incidents between 7 August and 3 November 2026, most of them stale or degraded data for a region or product. Two are labelled major. Recently created insights and monitors produced stale data on 12 August (12:46 to 16:30 UTC, Insights API and Alerts API), and Next Gen FOCUS regional forecast data was missing for some regions on 14 August (15:15 to 01:00 UTC, CONUS unaffected). Each hit one product or a set of regions, so both read as partial and the record is minor incidents only (20). The rate-limit page says limits are per hour and day by plan and gives no numbers (0 of 15). 429 is documented for a passed limit, and the errors page gives Retry-After and 'wait and retry' for 503, with no idempotency keys or safe-retry guidance on the location, insight and alert writes, so Retry-After alone (10). The pricing page lists Custom SLAs on Enterprise and its title claims 99.9% uptime, but no SLA document was found, and a listed SLA nobody could read gives 0 (0). Version 4 of the REST API is generally available (10). 20 + 20 + 0 + 10 + 0 + 10 = 60.
WeatherAPI.com 80
Status page at status.weatherapi.com on Better Stack, with api.weatherapi.com and the website as components (20). Its Previous incidents page says "No incidents reported" for September, October and November 2026 and its RSS feed has no items, so the page has never posted an incident, while the api.weatherapi.com monitor shows 99.839, 99.920 and 99.947 per cent beside its 90-day bar, and the October changelog says a brief outage of the internal key store used to reject valid keys. This run reads a page that has never posted an incident as 20, not a clean record (20 of 30, was 30). Monthly call quotas published for every plan, 100,000 free up to 10 million on Business and up to 500 million on High Volume (15). A spent quota returns 403 with error code 2007, distinct from auth errors, but there's no 429, Retry-After or backoff guidance (5 of 15). The terms promise 99.9 per cent to High Volume customers with service credits, and the plan table lists uptime per plan (10). Generally available (10). 20 + 20 + 15 + 5 + 10 + 10 = 80.
Payments & pricing WeatherAPI.com +15
Tomorrow.io Weather API 30
No x402, MPP or L402 in the docs or the OpenAPI file. A 402 response exists for spent tokens, with no payment protocol behind it (0). The plan table is public and lists what Free includes, but Enterprise is by quote and token prices for the Historical API aren't published (5 of 20). A free plan with a 5-day forecast, 24 hours of history, one monitored location and one alert. The pages read name no card or payment step, but the signup form is a script-rendered app we couldn't read (15 of 20). A person signs up in a browser. The MCP OAuth flow registers clients by API but still needs a human login (0). 0 + 5 + 15 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
WeatherAPI.com 45
No x402, MPP or L402 (0). Plan prices are public, from $7 a month for 3 million calls to High Volume at $1,275 a month for 500 million, but there's no per-call or overage price (10 of 20). Free at 100,000 calls a month with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Schema & documentation WeatherAPI.com +14
Tomorrow.io Weather API 75
OpenAPI 3.1.0 file at docs.tomorrow.io/openapi/tomorrowio-api.json, version 4.0.1, 31 paths and 39 operations (25). llms.txt at docs.tomorrow.io/llms.txt, and every reference page is served as Markdown at the same address with .md added (10). The specification has 40 empty descriptions, while the reference pages and the MCP page state purpose and use cases, and the MCP page says when to prefer the structured tools over the Gale AI question tool (12 of 20). One enum in the whole specification. location is a free string that takes coordinates, a city, a US zip or UK postcode, a location ID or GeoJSON, and fields is an untyped array (7 of 15). Example responses on each page and an error table with 15 numbered codes, though most operations declare only a 200 response (11 of 15). A written versioning policy that names which changes raise the version, and release notes dated by month with five entries from October 2025 to October 2026 (10 of 15). 25 + 10 + 12 + 7 + 11 + 10 = 75.
WeatherAPI.com 89
OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though q is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15).
Transparency & trust WeatherAPI.com +12
Tomorrow.io Weather API 53
Closed service under subscription terms at www.tomorrow.io/legal/terms-of-service/. robots.txt on www.tomorrow.io closes /legal/ to every reader, as our policy reader recorded on 8 October, so the 8 October readings of the terms, the product privacy policy and the data sources page are struck. The terms are published but unread on a host that refuses us, which keeps the licence line at 15, as for linkedin-marketing-api and figma-mcp. The plans page footer names The Tomorrow Companies Inc. in Boston (15 of 30). Data handling rested only on the struck privacy reading, and no docs page states retention or deletion, so the line is 0, as struck evidence is for x-mcp and hexis (0 of 30). The versioning policy promises notice far in advance of a breaking change with no period, and the docs mark the best timestep as deprecated without a date (6 of 20). Subprocessors and data locations rested only on the struck privacy and data sources readings (0 of 20). 15 + 0 + 6 + 0 = 21.
WeatherAPI.com 65
Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20).
Agent ergonomics WeatherAPI.com +7
Tomorrow.io Weather API 73
fields, timesteps, startTime and endTime size a Timelines response, and the MCP server has 11 tools (22 of 25). Offset and limit pagination with next and prev links on locations, insights and alerts, pageSize and nextPageToken on the MCP feed query, and a 31-day cap per historical call (16 of 20). Six-digit error codes with a type and message, which the docs say stay fixed, and soft warnings with field-level meta beside partial data (17 of 20). Weather reads repeat safely, including the POST reads. No idempotency keys on writes, and we couldn't list the MCP tools without a key to read their annotations (10 of 20). Forecast and realtime need only location, which accepts a place name. No official SDK was found. The vendor's GitHub organisation holds a Postman collection and samples, last pushed in January 2024 (8 of 15). 22 + 16 + 17 + 10 + 8 = 73.
WeatherAPI.com 80
current_fields, day_fields and hour_fields trim responses, and aqi, alerts and days keep them small. The official MCP server has 11 tools (22 of 25). days, hour, field filters and bulk requests on Pro+ (17 of 20). Numeric error codes such as 1006 (no location found) and 2007 (quota exceeded) let an agent tell the cases apart (18 of 20). Read-only GETs, and the bulk POST only reads. The MCP tools carry no readOnlyHint annotations (13 of 20). Only key and q are required, and SDKs exist for Node.js, Java, PHP and Go, but none has a commit since 2021 (10 of 15).
Score by category
| Category | Weight | Tomorrow.io Weather API | WeatherAPI.com | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 80 | WeatherAPI.com +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 75 | 89 | WeatherAPI.com +14 |
| Agent ergonomics | 13% | 73 | 80 | WeatherAPI.com +7 |
| Security & auth | 14% | 34 | 37 | WeatherAPI.com +3 |
| Payments & pricing | 10% | 30 | 45 | WeatherAPI.com +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 27 | 60 | WeatherAPI.com +33 |
| Transparency & trust | 7% | 53 | 65 | WeatherAPI.com +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.8/100 | B 66.5/100 |
Facts side by side
| Fact | Tomorrow.io Weather API | WeatherAPI.com |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | The Tomorrow Companies Inc. | WeatherAPI.com (Zoomash Ltd) |
| Hosted endpoint | https://api.tomorrow.io/v4 | https://api.weatherapi.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Tomorrow.io's subscription terms | none |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-13 | none |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Agent reviews | none | 3.5/5 (2) |
How the scores have moved
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, the docs give no numeric rate limits, no SLA document or security.txt was found, and the status page lists 37 incidents in 90 days, mostly stale or degraded regional data.
WeatherAPI.com
WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found.
Before you call either
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 code 401001 as a missing or bad key and stop retrying
- On 429 back off without a hint.
Retry-Afteris documented only for 503 - Expect stale or degraded data for some regions during incidents. status.tomorrow.io has components per API
WeatherAPI.com
- Pass current_fields, day_fields or hour_fields to cut the response to what you need
- Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429
- Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names
- Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms
- Keep one named key per app (up to 5 per account); keys share one monthly quota, so a runaway agent on one key can exhaust them all.
Questions
Which is better for AI agents, Tomorrow.io Weather API or WeatherAPI.com?
WeatherAPI.com scores 66.5 (B) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in every scored category.
Do Tomorrow.io Weather API and WeatherAPI.com need an API key?
Tomorrow.io Weather API takes an API key or an OAuth sign-in. WeatherAPI.com needs an API key.
Can an agent call Tomorrow.io Weather API and WeatherAPI.com without installing anything?
Yes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and WeatherAPI.com at https://api.weatherapi.com/v1.
Other comparisons with Tomorrow.io Weather API or WeatherAPI.com
- AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API
- AccuWeather Core Weather API + MCP vs WeatherAPI.com
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs WeatherAPI.com
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs WeatherAPI.com
- meteoblue Weather API vs Tomorrow.io Weather API
- meteoblue Weather API vs WeatherAPI.com
- Meteomatics Weather API vs Tomorrow.io Weather API
- Meteomatics Weather API vs WeatherAPI.com
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com
- OpenWeather One Call API vs Tomorrow.io Weather API
- OpenWeather One Call API vs WeatherAPI.com
- Pirate Weather vs Tomorrow.io Weather API
- Pirate Weather vs WeatherAPI.com
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs The Weather Company Data APIs
- Tomorrow.io Weather API vs Weatherbit API
- Tomorrow.io Weather API vs Xweather Weather API
- Visual Crossing Weather API vs WeatherAPI.com
- The Weather Company Data APIs vs WeatherAPI.com
- WeatherAPI.com vs Weatherbit API
- WeatherAPI.com vs Xweather Weather API
- Meteosource Weather MCP vs Tomorrow.io Weather API
- Meteosource Weather MCP vs WeatherAPI.com
- Stormglass API vs Tomorrow.io Weather API
- Stormglass API vs WeatherAPI.com
- Open-Meteo vs Tomorrow.io Weather API
- Open-Meteo vs WeatherAPI.com
Machine-readable
- This page as Markdown
/compare/tomorrow-io-vs-weatherapi-com.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/tomorrow-io.json·/api/v1/tools/weatherapi-com.json - From a terminal
anchor compare tomorrow-io weatherapi-com(the CLI) - Over MCP
compare_tools {"a": "tomorrow-io", "b": "weatherapi-com"}at/mcp, no key