Head to head · Current weather · October 2026 research run
Visual Crossing Weather API vs Xweather Weather API
Xweather Weather API scores 68.2 (B) on agent readiness against Visual Crossing Weather API's 65.7 (B), and leads in 5 of 7 scored categories. Visual Crossing Weather API leads on payments & pricing. Both do current weather.
Best weather and climate data APIs for AI agents · All 136 weather comparisons
Which one, for what
Best for History and backfills, climate normals and date-range questions from one endpoint.
Ahead on
- Payments & pricing, 83 against 48
Also in its favour
- Free to start without a card
- No incidents deducted, where Xweather Weather API loses 3 points for them
Watch for
With a key, the REST API takes it only in the query string
Best 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, 84 against 68
- Schema & documentation, 83 against 74
- Security & auth, 52 against 40
- Maintenance & community, 81 against 58
- Transparency & trust, 69 against 57
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=
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.
Payments & pricing Visual Crossing Weather API +35
Visual Crossing Weather API 83
No x402, MPP or L402 (0). $0.0001 a record above the free 1,000 a day, in the pricing page's own description, readable without login, though no plan shows a price in the page as served (20). 1,000 records a day free with a key and no card, and since 28 October a no-key route free for commercial use with attribution (20). An agent can call the Timeline and Maps APIs with no key, account or signup, per the no-key guide published 28 October 2026 and llms.txt, under IP-based fair-use limits with no fixed allowance. The same guide says some advanced queries or specialised data products may need a registered account, and the MCP server still needs a key, so the keyless route covers ordinary requests only. Partial credit, as for jina-reader (Search needs a key) and firecrawl-mcp (crawl, map and agent need a key) (15; 0 on 1 October, when a person had to sign up). 0 + 20 + 20 + 15 = 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.
Xweather Weather API 48
No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (0). Plan prices are public without a login, and the cost of each endpoint in accesses is published. The overage rate is not, and the page showed us pounds only, £240 a month for 1,000,000 accesses (12 of 20). A free Developer tier of 15,000 accesses a month, with no card and no expiry per the pricing page (20). Pricing is per the 8 October check, not re-read on 1 November. A person signs up in a browser. The MCP OAuth flow registers clients by API but still needs a human to enter the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 32 is 48.
Maintenance & community Xweather Weather API +23
Visual Crossing Weather API 58
The no-key guide, published 28 October 2026, adds keyless access to the Timeline and Maps APIs, and the Timeline docs changed the same day to describe it (30). Dated sources in the 90 days from 6 August are the changelog (published 4 September 2026, its four Q3 additions dated only by quarter), the MCP guide (published 24 September 2026) and the no-key guide (28 October 2026), three in all (20). Page modification stamps were not counted. A public changelog, and support by email and forum that we didn't test (8 of 15). The official MCP server isn't in the registry, where only a third-party Pipeworx wrapper appears (0.2.0, 29 October), and there's no official SDK (0). No package to judge (0). 30 + 20 + 8 + 0 + 0 = 58.
Xweather Weather API 81
The newest API release is 1.45.0 on 21 October 2026, 11 days before this check, after 1.44.0 on 30 September (30). Since 3 August the API shipped 1.43.4, 1.43.5, 1.44.0 and 1.45.0, the MCP server 1.3.0 on 27 October, and the agent skills repository releases 0.14.1 to 0.15.4 between 1 September and 26 October (20). Public changelogs, a ticket form and support@xweather.com, with community support on the free tier and priority email on the paid plan. Response times were not tested (10 of 15). The MCP server is in the official registry as com.xweather/weather, active, though the entry still shows 1.2.2 (15). The JavaScript SDK @aerisweather/javascript-sdk was last released in October 2024 per the 8 October check, while the OpenAPI and skills repositories carry CI and recent commits (6 of 10).
Reliability Xweather Weather API +16
Visual Crossing Weather API 68
Status page at status.visualcrossing.com, run on UptimeRobot, with 24-hour to 90-day uptime sections (20, held while this run's 15 or 20 split for UptimeRobot pages is open). On 4 November its monitor data still didn't load in the page we may read (its robots.txt disallows /api/, where the data comes from), and it showed no updates in the last seven days, so no incident record could be read (5). Limits published with numbers for registered plans, 1,000 records a day free, records and locations per query, and concurrency of 1 on Free and Professional and 10 on Corporate. The no-key route added on 28 October publishes no fixed allowance (15). 429 is documented for exceeded limits, and the no-key guide and llms.txt now say to retry with exponential backoff after a 429. Every call is a GET, so no write needs safe-retry guidance. Backoff guidance alone is 10 in this run (8 on 1 October, when none was found). The plan table lists 99.5 per cent uptime on Free and 99.9 on paid plans, but the terms only owe compensation where a plan includes crediting provisions (8 of 10). The Timeline API is generally available, with minutes marked beta (10). 20 + 5 + 15 + 10 + 8 + 10 = 68.
Xweather Weather API 84
Graded as a hosted service. Status page at status.xweather.com on Atlassian Statuspage with 21 components, among them API General, Conditions, Forecasts, Alerts, Lightning Endpoints and MCP Server (20). Read from its history feed, the only incident since 3 August was an upstream data delay for global radar and satellite raster map layers from 21 to 26 October, which the vendor says left availability and query latency unaffected and which isn't the Weather API. Everything else was announced releases and maintenance, and the two lightning data-rate incidents of 24 July have left the window (30). Monthly quotas are published, 15,000 and 1,000,000 accesses, but the per-minute limit is given only in response headers and by support (8 of 15). 429 is documented with the codes maxhits_min and maxhits, the OpenAPI file declares Retry-After, seven X-RateLimit-* headers report the remaining allowance, the MCP docs advise exponential backoff, and failed calls are not charged. The API is read-only, so no idempotency keys are needed (13 of 15). The pricing page mentions custom SLA guarantees for enterprise plans, with no SLA document found (3 of 10). The REST API at 1.45.0 and the MCP server at 1.3.0 are generally available (10).
Security & auth Xweather Weather API +12
Visual Crossing Weather API 40
The REST API takes a key only as the key query parameter, so we deducted 10. Since 28 October supported requests need no key at all, managed by client IP address. The MCP server takes a key in an X-VC-API-Key header or user or machine-to-machine OAuth once provisioned, and the MCP guide recommends a dedicated key per integration so it can be rotated or disabled (15 of 30). Read-only data (15 of 20). Alerts come from national weather agencies (10 of 15). We found no per-call log or usage view in the docs we read (0). /.well-known/security.txt answers 404 on 4 November, and no disclosure policy, bounty or certification was found (0). 15 + 15 + 10 + 0 + 0 = 40.
Xweather Weather API 52
Credentials are a client_id and client_secret per registered app, limited to a domain or app bundle namespace and regenerated in the dashboard. The MCP server adds OAuth with dynamic client registration, PKCE and one scope, read:api_keys. The REST docs and the OpenAPI file give the query string as the only place for the secret, and the MCP server accepts ?api_key= and, since 1.3.0, the key in the URL path (22 less 10, 12 of 30). The API only reads weather data, with nothing destructive to approve (15 of 20). Responses are mostly numeric. Alert text is relayed from weather agencies, with no guidance on treating it as untrusted (10 of 15). Cost and quota headers come back on each call. No per-call log for the account holder was found in the docs (4 of 15). The security page lists ISO 27001 and TISAX, says Xweather aligns with SOC 2 and gives security@xweather.com, with no report linked and no bounty. xweather.com has no security.txt, while the parent vaisala.com has one with a policy link (11 of 20).
Transparency & trust Xweather Weather API +12
Visual Crossing Weather API 57
Closed service with terms last updated January 2023 that set storage by licence level, bar resale and add a non-compete (15). The privacy policy, updated 23 May 2025 per the 1 October check and the site's policy reading of 8 October, states no retention periods, says nothing about what API requests log and doesn't mention a DPA. The no-key guide says anonymous use is managed by client IP address, which the policy doesn't describe (8 of 30). The changelog promises backwards compatibility unless noted, but there's no deprecation policy or dated notice (8 of 20). No subprocessors or data locations named, beyond Google tags on the site (0). 15 + 8 + 8 + 0 = 31.
Xweather Weather API 69
Closed service under Vaisala's group subscription terms, dated 1 January 2023, which set a liability cap of twelve months' fees and ICC arbitration. They are written for annual, invoiced contracts and leave the product's own rules to service descriptions that were not found in public. The OpenAPI files and agent skills are MIT (15 of 30). The privacy policy is the group policy effective 1 June 2020. It covers online services, keeps data for a period it calls reasonable with no figure, and still cites the US Privacy Shield. No DPA was found (12 of 30). The changelog marks deprecations with dates, the API has deprecated and warn_deprecated codes, and the terms promise notice of modifications with a 30-day right to end the contract after a material reduction. No notice period is stated (8 of 20). A data processors page names about 40 processors with a location for each, with a caveat that it may be incomplete (16 of 20).
Schema & documentation Xweather Weather API +9
Visual Crossing Weather API 74
OpenAPI 3.0.1, version 4.6 (Last-Modified 25 October 2024), one Timeline path. It's thin, with no enums, terse parameter descriptions, key marked required and only a 200 response defined (15 of 25). llms.txt at www.visualcrossing.com/llms.txt, now opening with the no-key route, with sections for access, MCP and rules for agents (10). The Timeline docs explain each parameter and when to use date ranges, include and elements. They now say no key is needed for supported free requests while the parameter list still says key (required) (14 of 20, held). unitGroup, include and contentType values are listed in the docs, not in the spec, and elements is a free list (9 of 15). Example requests for forecast, date range and single time, and a table of 400, 401, 404, 429 and 500 with causes (13 of 15). A public changelog grouped by quarter, published 4 September 2026, which says changes keep backwards compatibility unless noted; it has no entry for the no-key route (13 of 15). 15 + 10 + 14 + 9 + 13 + 13 = 74.
Xweather Weather API 83
OpenAPI 3.2.0 and 3.1.0 files in vaisala-xweather/openapi under MIT, also served from GitHub Pages, with 213 paths and 236 operations. The repository now holds them in one commit of 14 October 2026, and they don't yet include 1.45.0's /roadweather/alerts. The MCP tools' input schemas need a key to list and were not read (25). llms.txt at www.xweather.com/llms.txt indexes the site and docs pages. The docs pages have no Markdown copies (a .md address returns 404), though six agent skills in Markdown cover request building (8 of 10). Every operation and parameter in the OpenAPI file has a description, and the MCP tool pages state each tool's purpose and limits, such as a 24-hour tool marked as not for multi-day forecasts (16 of 20). The file has 9 enums and 10 required parameters among 2,289 parameter uses, and filter, query and sort are free strings with their own grammar (8 of 15). Each operation declares 200, 401, 404, 429 and 500 with examples, and the docs list 16 error codes and the warning codes (13 of 15). Dated, numbered changelogs for the API and the MCP server. The API path carries no version (13 of 15).
Score by category
| Category | Weight | Visual Crossing Weather API | Xweather Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 84 | Xweather Weather API +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 83 | Xweather Weather API +9 |
| Agent ergonomics | 13% | 78 | 78 | even |
| Security & auth | 14% | 40 | 52 | Xweather Weather API +12 |
| Payments & pricing | 10% | 83 | 48 | Visual Crossing Weather API +35 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 81 | Xweather Weather API +23 |
| Transparency & trust | 7% | 57 | 69 | Xweather Weather API +12 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 65.7/100 | B 68.2/100 |
Facts side by side
| Fact | Visual Crossing Weather API | Xweather Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Visual Crossing | Vaisala Oyj |
| Hosted endpoint | https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline | https://data.api.xweather.com |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | 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 | 1 | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.xweather/weather |
| Last release | none | 2026-10-21 |
| Terms last updated | 2023-01-01 | couldn't be read |
| Privacy policy last updated | no date given | 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 | yes | 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 | none | 0 stars, 1.4k npm/wk |
| Agent reviews | 4/5 (2) | 3.8/5 (4) |
How the scores have moved
Verdicts
Visual Crossing Weather API
History from 1970, current conditions and a 15-day forecast from one endpoint, and since 28 October callable with no key under IP-based fair-use limits. With a key, the REST API takes it only in the query string, and the status page's incident history could not be read.
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
Visual Crossing Weather API
- Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records
- Try the no-key route first for light use, and on a 429 slow down and retry with backoff rather than switching IP addresses
- Show 'Weather data provided by Visual Crossing Weather' near any displayed data on free use
- Pass unitGroup=metric. The default is US units
- Use the MCP server with X-VC-API-Key rather than pasting a key into a URL
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, Visual Crossing Weather API or Xweather Weather API?
Xweather Weather API scores 68.2 (B) on agent readiness against Visual Crossing Weather API's 65.7 (B), and leads in 5 of 7 scored categories. Visual Crossing Weather API leads on payments & pricing.
Do Visual Crossing Weather API and Xweather Weather API need an API key?
Visual Crossing Weather API needs an API key. Xweather Weather API takes an API key or an OAuth sign-in.
Can an agent call Visual Crossing Weather API and Xweather Weather API without installing anything?
Yes. Visual Crossing Weather API has a hosted endpoint at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline and Xweather Weather API at https://data.api.xweather.com.
Other comparisons with Visual Crossing Weather API or Xweather Weather API
- AccuWeather Core Weather API + MCP vs Visual Crossing Weather API
- AccuWeather Core Weather API + MCP vs Xweather Weather API
- Google Weather API (Maps Platform) vs Visual Crossing Weather API
- Google Weather API (Maps Platform) vs Xweather Weather API
- Met Office Weather DataHub (Site Specific) vs Visual Crossing Weather API
- Met Office Weather DataHub (Site Specific) vs Xweather Weather API
- meteoblue Weather API vs Visual Crossing Weather API
- meteoblue Weather API vs Xweather Weather API
- Meteomatics Weather API vs Visual Crossing Weather API
- Meteomatics Weather API vs Xweather Weather API
- NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API
- NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API
- OpenWeather One Call API vs Visual Crossing Weather API
- OpenWeather One Call API vs Xweather Weather API
- Pirate Weather vs Visual Crossing Weather API
- Pirate Weather vs Xweather Weather API
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs Xweather Weather API
- Visual Crossing Weather API vs The Weather Company Data APIs
- Visual Crossing Weather API vs WeatherAPI.com
- Visual Crossing Weather API vs Weatherbit API
- The Weather Company Data APIs vs Xweather Weather API
- WeatherAPI.com vs Xweather Weather API
- Weatherbit API vs Xweather Weather API
- Meteosource Weather MCP vs Visual Crossing Weather API
- Meteosource Weather MCP vs Xweather Weather API
- Stormglass API vs Visual Crossing Weather API
- Stormglass API vs Xweather Weather API
- Open-Meteo vs Visual Crossing Weather API
- Open-Meteo vs Xweather Weather API
Machine-readable
- This page as Markdown
/compare/visual-crossing-vs-xweather.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/visual-crossing.json·/api/v1/tools/xweather.json - From a terminal
anchor compare visual-crossing xweather(the CLI) - Over MCP
compare_tools {"a": "visual-crossing", "b": "xweather"}at/mcp, no key