Head to head · Current weather · October 2026 research run
Tomorrow.io Weather API vs The Weather Company Data APIs
The Weather Company Data APIs scores 55.8 (C) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in 4 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics. 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.
Ahead on
- Agent ergonomics, 73 against 54
Watch for
No public price for paid use. The plan table lists Free and Enterprise, the second by quote
The Weather Company Data APIs C
Best for A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales.
Ahead on
- Reliability, 75 against 60
- Security & auth, 47 against 34
- Maintenance & community, 36 against 27
Watch for
No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.
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.
Agent ergonomics Tomorrow.io Weather API +19
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.
The Weather Company Data APIs 54
Response size is controlled by choosing a duration endpoint, by the products field selection and compact mode on History on Demand, and by aggregation, which is capped at 10 products and 1 MB. There is no general field selection (14 of 25). Only two APIs paginate, Alert Headlines and History on Demand (10 of 20). Errors are JSON with a code and message, such as CDN-0004 for a missing key and CDN-0001 for an invalid one, as the reference pages document. Authorisation failures and exceeded limits share 401 (11 of 20). All documented operations are GET requests, so retries are safe (15 of 20). Every v3 call needs a location plus units, language and format, gzip is required, and no official SDK was found (4 of 15).
Reliability The Weather Company Data APIs +15
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.
The Weather Company Data APIs 75
Status page at theweathercompanyapis.statuspage.io with 16 components, read from the page itself on 4 November 2026 (20). Its history feed shows 14 incidents from 6 August to 28 October 2026, each a degraded API, region or upstream source, such as EU-West latency on 26 October and the 5 September NOAA and NWS upstream outage of alerts, observations and radar, so all partial (20 of 30). Trial limits are published at 100 requests a minute and 50,000 a day, and paid limits are a monthly cap set by contract (15). No 429 is documented and an exceeded limit returns 401, but the error tables of three references, Daily Forecast among them, tell clients to retry 502, 503 and 504 with exponential backoff (10). The product page states a 99.95 per cent uptime SLA with no SLA document published (0). The v1, v2 and v3 APIs are in production, although the documentation site is labelled beta (10).
Security & auth The Weather Company Data APIs +13
Tomorrow.io Weather API 34
The docs state that API keys carry full privileges, with one default key on the dashboard and more keys created by an account manager. The key may travel as an apikey query parameter, which the OpenAPI file declares as the scheme, or as a header. The MCP endpoint also advertises OAuth with dynamic client registration, PKCE (S256) and one scope, mcp:read, in its live metadata, which the MCP docs page doesn't mention (12 of 30, after the 10-point deduction for a secret in the URL). Weather calls only read, the OAuth scope is read-only, and the key can also create, change and delete locations, insights and alerts with no confirmation step (10 of 20). Responses are mostly numeric fields. Gale AI returns generated text and the feeds carry third-party event text, with no guidance on treating it as untrusted (8 of 15). An X-Correlation-ID on every response and an Activity section in the dashboard for webhooks. No per-call log was found in the docs (4 of 15). No security.txt (404 on www on 4 November 2026, and on the apex and api hosts per the 8 October check), and no disclosure policy, bounty or certification found on the pages read or by a site search (0 of 20). 12 + 10 + 8 + 4 + 0 = 34.
The Weather Company Data APIs 47
A plain API key whose endpoints are set by the customer's package. It is accepted only in the query string, so we deducted 10. Revocation and rotation are not documented, and the best-practices page suggests a separate key per use case (10 of 30). The API is read-only (17 of 20). Alert text comes from national agencies and US alert summaries are AI-generated, with no guidance on handling that text (10 of 15). History on Demand has a usage endpoint for key consumption. The customer portal sits behind a login and was not read (3 of 15). weather.com publishes a valid security.txt with a reporting address that expires on 31 December 2026, and the site footer links a security incident page. No acknowledgement time, bug bounty or readable certification was found; the trust centre is drawn by script (7 of 20).
Maintenance & community The Weather Company Data APIs +9
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.
The Weather Company Data APIs 36
The Hourly Forecast Enterprise reference records a specification change on 15 October 2026 (a new windSpeedKnots field released on 22 October), 20 days before the check (30). Two dated changelog entries in the 90 days from 6 August (14 September and 15 October) in the 18 references we read, short of three (0). Support is by email and a ServiceNow customer portal, and the status page is updated during incidents. No public community channel was found (6 of 15). No official SDK was found (0). No package to assess (0).
Score by category
| Category | Weight | Tomorrow.io Weather API | The Weather Company Data APIs | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 75 | The Weather Company Data APIs +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 75 | 77 | The Weather Company Data APIs +2 |
| Agent ergonomics | 13% | 73 | 54 | Tomorrow.io Weather API +19 |
| Security & auth | 14% | 34 | 47 | The Weather Company Data APIs +13 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 27 | 36 | The Weather Company Data APIs +9 |
| Transparency & trust | 7% | 53 | 50 | Tomorrow.io Weather API +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.8/100 | C 55.8/100 |
Facts side by side
| Fact | Tomorrow.io Weather API | The Weather Company Data APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | The Tomorrow Companies Inc. | The Weather Company, LLC |
| Hosted endpoint | https://api.tomorrow.io/v4 | https://api.weather.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under Tomorrow.io's subscription terms | Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-13 | 2026-10-15 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
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.
The Weather Company Data APIs
A wide weather data API with 168 API references built from OpenAPI documents, Markdown docs for agents, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.
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
The Weather Company Data APIs
- Send
units,languageandformat=jsonwith a location on every v3 call, plusAccept-Encoding: gzip, which the usage guide marks as required. - Keep the key out of logs and client-side code, because it travels in the query string as
apiKey. - Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.
- Each forecast duration (
3dayto15day) is a separate entitlement. Request only durations the contract covers. - Use
/v3/aggcommonto combine up to 10 products in one request. Each product and each location still counts as one call.
Questions
Which is better for AI agents, Tomorrow.io Weather API or The Weather Company Data APIs?
The Weather Company Data APIs scores 55.8 (C) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in 4 of 7 scored categories. Tomorrow.io Weather API leads on agent ergonomics.
Do Tomorrow.io Weather API and The Weather Company Data APIs need an API key?
Tomorrow.io Weather API takes an API key or an OAuth sign-in. The Weather Company Data APIs needs an API key.
Can an agent call Tomorrow.io Weather API and The Weather Company Data APIs without installing anything?
Yes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and The Weather Company Data APIs at https://api.weather.com.
Other comparisons with Tomorrow.io Weather API or The Weather Company Data APIs
- AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API
- AccuWeather Core Weather API + MCP vs The Weather Company Data APIs
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs The Weather Company Data APIs
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs
- meteoblue Weather API vs Tomorrow.io Weather API
- meteoblue Weather API vs The Weather Company Data APIs
- Meteomatics Weather API vs Tomorrow.io Weather API
- Meteomatics Weather API vs The Weather Company Data APIs
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs
- OpenWeather One Call API vs Tomorrow.io Weather API
- OpenWeather One Call API vs The Weather Company Data APIs
- Pirate Weather vs Tomorrow.io Weather API
- Pirate Weather vs The Weather Company Data APIs
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs WeatherAPI.com
- Tomorrow.io Weather API vs Weatherbit API
- Tomorrow.io Weather API vs Xweather Weather API
- Visual Crossing Weather API vs The Weather Company Data APIs
- The Weather Company Data APIs vs WeatherAPI.com
- The Weather Company Data APIs vs Weatherbit API
- The Weather Company Data APIs vs Xweather Weather API
- Meteosource Weather MCP vs Tomorrow.io Weather API
- Meteosource Weather MCP vs The Weather Company Data APIs
- Stormglass API vs Tomorrow.io Weather API
- Stormglass API vs The Weather Company Data APIs
- Open-Meteo vs Tomorrow.io Weather API
- Open-Meteo vs The Weather Company Data APIs
Machine-readable
- This page as Markdown
/compare/tomorrow-io-vs-weather-company.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/tomorrow-io.json·/api/v1/tools/weather-company.json - From a terminal
anchor compare tomorrow-io weather-company(the CLI) - Over MCP
compare_tools {"a": "tomorrow-io", "b": "weather-company"}at/mcp, no key