Head to head · Weather current · October 2026 research run
Tomorrow.io Weather API vs Xweather Weather API
Xweather Weather API scores 67.1 (B) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in every scored category. Both do weather current.
Which one, for what
Good 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
Good for Teams that need lightning, hail, road weather or tropical data beside ordinary conditions and forecasts, with an MCP server and an OpenAPI file ready for agents.
Ahead on
- Reliability, 74 against 55
- Schema & documentation, 83 against 75
- Agent ergonomics, 78 against 73
- Security & auth, 52 against 34
- Payments & pricing, 32 against 20
- Maintenance & community, 81 against 27
- Transparency & trust, 68 against 63
Watch for
The REST API documents client_id and client_secret only as query parameters, and the MCP server also accepts the key as ?api_key=
Score by category
| Category | Weight this run | Tomorrow.io Weather API | Xweather Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 74 | Xweather Weather API +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 83 | Xweather Weather API +8 |
| Agent ergonomics | 13%16.2 | 73 | 78 | Xweather Weather API +5 |
| Security & auth | 14%17.5 | 34 | 52 | Xweather Weather API +18 |
| Payments & pricing | 10%12.5 | 20 | 32 | Xweather Weather API +12 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 27 | 81 | Xweather Weather API +54 |
| Transparency & trust | 7%8.8 | 63 | 68 | Xweather Weather API +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 51.4 · D | 67.1 · B |
Facts side by side
| Fact | Tomorrow.io Weather API | Xweather Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | The Tomorrow Companies Inc. | Vaisala Oyj |
| Hosted endpoint | https://api.tomorrow.io/v4 | https://data.api.xweather.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Tomorrow.io's subscription terms | Proprietary service under the General Conditions of Subscription Services of Vaisala Group. The OpenAPI files and the agent skills on GitHub are MIT |
| Tools exposed | 11 | 19 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.xweather/weather |
| Last release | 2026-07-14 | 2026-09-14 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | 2020-06-01 |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | none | 0 stars, 1.4k npm/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.
Xweather Weather API
A public OpenAPI file with 236 operations, a hosted MCP server in the official registry and a free tier of 15,000 accesses a month suit agents. REST credentials travel only in the query string, per-minute limits are unpublished, and the group terms bar commercial use of free plans and passing data to third parties unless a service description allows it.
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 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026
- On 429 back off without a hint.
Retry-Afteris documented only for 503 - 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
Xweather Weather API
- Check
successanderror.codeon every response. Application errors such asinvalid_locationreturn HTTP 200 withsuccessfalse - Send
fields,limitandplimit. The docs put a 15-day hourly forecast at about 600 KB, and about 25 KB with three fields - Read
X-Cost-Tokensafter each call. Cost is the endpoint multiplier times the intervals requested, so narrowfromandto - For MCP, send
Authorization: Bearer <client_id>_<client_secret>and avoid theapi_keyquery parameter, which puts the secret in the URL - Add
include_tagsorinclude_toolsto the MCP URL to load only the tool groups the task needs - On 429 read
Retry-Afterand theX-RateLimit-Reset-*headers.maxhits_minclears at the next minute,maxhitsat the period reset
Questions
Which is better for AI agents, Tomorrow.io Weather API or Xweather Weather API?
Xweather Weather API scores 67.1 (B) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in every scored category.
Do Tomorrow.io Weather API and Xweather Weather API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Tomorrow.io Weather API and Xweather Weather API without installing anything?
Yes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and Xweather Weather API at https://data.api.xweather.com.
Other comparisons with Tomorrow.io Weather API or Xweather Weather API
- AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API
- AccuWeather Core Weather API + MCP vs Xweather Weather API
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs Xweather Weather API
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs Xweather Weather API
- meteoblue Weather API vs Tomorrow.io Weather API
- meteoblue Weather API vs Xweather Weather API
- Meteomatics Weather API vs Tomorrow.io Weather API
- Meteomatics Weather API vs Xweather Weather API
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API
- OpenWeather One Call API vs Tomorrow.io Weather API
- OpenWeather One Call API vs Xweather Weather API
- Pirate Weather vs Tomorrow.io Weather API
- Pirate Weather vs Xweather Weather API
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs The Weather Company Data APIs
- Tomorrow.io Weather API vs WeatherAPI.com
- Tomorrow.io Weather API vs Weatherbit API
- Visual Crossing Weather API vs Xweather Weather API
- The Weather Company Data APIs vs Xweather Weather API
- WeatherAPI.com vs Xweather Weather API
- Weatherbit API vs Xweather Weather API
Machine-readable
- This page as Markdown
/compare/tomorrow-io-vs-xweather.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/tomorrow-io.json·/api/v1/tools/xweather.json - From a terminal
anchor compare tomorrow-io xweather(the CLI) - Over MCP
compare_tools {"a": "tomorrow-io", "b": "xweather"}at/mcp, no key