Head to head · Weather current · October 2026 research run
Weatherbit API vs Xweather Weather API
Xweather Weather API scores 67.1 (B) on agent readiness against Weatherbit API's 57.7 (C), and leads in 6 of 7 scored categories. Weatherbit API leads on reliability. Both do weather current.
Which one, for what
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 74
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
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
- Schema & documentation, 83 against 72
- Agent ergonomics, 78 against 61
- Security & auth, 52 against 39
- Maintenance & community, 81 against 21
- 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 | Weatherbit API | Xweather Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 91 | 74 | Weatherbit API +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 83 | Xweather Weather API +11 |
| Agent ergonomics | 13%16.2 | 61 | 78 | Xweather Weather API +17 |
| Security & auth | 14%17.5 | 39 | 52 | Xweather Weather API +13 |
| Payments & pricing | 10%12.5 | 30 | 32 | Xweather Weather API +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 21 | 81 | Xweather Weather API +60 |
| Transparency & trust | 7%8.8 | 63 | 68 | Xweather Weather API +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 57.7 · C | 67.1 · B |
Facts side by side
| Fact | Weatherbit API | Xweather Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Weatherbit LLC | Vaisala Oyj |
| Hosted endpoint | https://api.weatherbit.io/v2.0 | https://data.api.xweather.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary 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 | 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 | none | 19 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.xweather/weather |
| Last release | 2025-08-01 | 2026-09-14 |
| Terms last updated | 2025-05-01 | couldn't be read |
| Privacy policy last updated | 2023-12-26 | 2020-06-01 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 78 PyPI/wk | 0 stars, 1.4k npm/wk |
Verdicts
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.
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
Weatherbit API
- 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
- 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
- Treat HTTP 204 with an empty body as no data found, not as an error
- Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
- Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0
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, Weatherbit API or Xweather Weather API?
Xweather Weather API scores 67.1 (B) on agent readiness against Weatherbit API's 57.7 (C), and leads in 6 of 7 scored categories. Weatherbit API leads on reliability.
Do Weatherbit API and Xweather Weather API need an API key?
Weatherbit API needs an API key. Xweather Weather API takes an API key or an OAuth sign-in.
Can an agent call Weatherbit API and Xweather Weather API without installing anything?
Yes. Weatherbit API has a hosted endpoint at https://api.weatherbit.io/v2.0 and Xweather Weather API at https://data.api.xweather.com.
Other comparisons with Weatherbit API or Xweather Weather API
- AccuWeather Core Weather API + MCP vs Weatherbit API
- AccuWeather Core Weather API + MCP vs Xweather Weather API
- Google Weather API (Maps Platform) vs Weatherbit API
- Google Weather API (Maps Platform) vs Xweather Weather API
- Met Office Weather DataHub (Site Specific) vs Weatherbit API
- Met Office Weather DataHub (Site Specific) vs Xweather Weather API
- meteoblue Weather API vs Weatherbit API
- meteoblue Weather API vs Xweather Weather API
- Meteomatics Weather API vs Weatherbit API
- Meteomatics Weather API vs Xweather Weather API
- NOAA National Weather Service API (api.weather.gov) vs Weatherbit API
- NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API
- OpenWeather One Call API vs Weatherbit API
- OpenWeather One Call API vs Xweather Weather API
- Pirate Weather vs Weatherbit API
- Pirate Weather vs Xweather Weather API
- Tomorrow.io Weather API vs Weatherbit API
- Tomorrow.io Weather API vs Xweather Weather API
- Visual Crossing Weather API vs Weatherbit API
- Visual Crossing Weather API vs Xweather Weather API
- The Weather Company Data APIs vs Weatherbit API
- The Weather Company Data APIs vs Xweather Weather API
- WeatherAPI.com vs Weatherbit API
- WeatherAPI.com vs Xweather Weather API
Machine-readable
- This page as Markdown
/compare/weatherbit-vs-xweather.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/weatherbit.json·/api/v1/tools/xweather.json - From a terminal
anchor compare weatherbit xweather(the CLI) - Over MCP
compare_tools {"a": "weatherbit", "b": "xweather"}at/mcp, no key