Head to head · Current weather · October 2026 research run

AccuWeather Core Weather API + MCP vs Visual Crossing Weather API

Visual Crossing Weather API scores 65.7 (B) on agent readiness against AccuWeather Core Weather API + MCP's 50.8 (D), and leads in 6 of 7 scored categories. AccuWeather Core Weather API + MCP leads on reliability. Both do current weather.

Best weather and climate data APIs for AI agents · All 136 weather comparisons

Which one, for what

AccuWeather Core Weather API + MCP D

Best for Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user.

Ahead on

  • Reliability, 75 against 68

Watch for

Terms forbid using the data to train, validate or otherwise inform any AI system

Visual Crossing Weather API B

Best for History and backfills, climate normals and date-range questions from one endpoint.

Ahead on

  • Schema & documentation, 74 against 60
  • Agent ergonomics, 78 against 60
  • Payments & pricing, 83 against 38
  • Maintenance & community, 58 against 3
  • Transparency & trust, 57 against 51

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

With a key, the REST API takes it only in the query string

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 Visual Crossing Weather API +55

AccuWeather Core Weather API + MCP 3

No release notes or changelog on the portal, re-read on 4 November. The API terms update of 28 April 2026 was the only dated change on 1 October, and a terms date isn't an API change in this run's reading; it is also now 190 days old (0). The MCP server grew from 26 to 27 tools with no dated entry (0). No dated changes in the last 90 days (0). Support through a contact form, with no public changelog or community channel (3 of 15). The official MCP server isn't in the registry, per the 1 October check, and there's no official SDK (0). No package to judge (0). 0 + 0 + 3 + 0 + 0 = 3.

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.

Payments & pricing Visual Crossing Weather API +45

AccuWeather Core Weather API + MCP 38

No x402, MPP or L402 (0). Package prices and per-1,000 overage rates are public, from $2 a month for 15,000 calls with $0.25 per 1,000 over (15 of 20). A 14-day trial at 500 Core Weather calls a day. Neither the FAQ nor llms-full.txt says whether it needs a card, so we gave half (10 of 20, the earlier partial kept). A person signs up in a browser (0). 0 + 15 + 10 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Agent ergonomics Visual Crossing Weather API +18

AccuWeather Core Weather API + MCP 60

27 MCP tools covering all 106 Core Weather GET endpoints, with no toolsets or subset option found. REST responses shrink a little with details=false and by choosing the 1, 5, 10 or 15-day endpoint (15 of 25). No field selection or paging (10 of 20). RFC 7807 errors with a trace id and a documented status table (16 of 20). Read-only GETs, and the docs describe the MCP server as read-only (15 of 20). Every weather call needs a location key from a separate search call first, and there's no official SDK (4 of 15). 15 + 10 + 16 + 15 + 4 = 60.

Visual Crossing Weather API 78

include picks days, hours, current, alerts or stats and elements trims columns, so a call can be cut to a few fields. The MCP server has one tool (24 of 25). Date ranges, include, elements, options=nonulls and per-query record caps control output (18 of 20). Error codes come with causes and the body carries a message, but no machine-readable error key (15 of 20). Read-only GETs. The MCP guide doesn't mention tool annotations (14 of 20). Only a location is required, but unitGroup defaults to US units and the GitHub repository holds sample code, not an SDK (7 of 15). Per the 1 October reading, with the Timeline parameters and error table confirmed on 4 November. 24 + 18 + 15 + 14 + 7 = 78.

Schema & documentation Visual Crossing Weather API +14

AccuWeather Core Weather API + MCP 60

No OpenAPI or other machine-readable contract found. The Core Weather, MinuteCast and Lightning references are drawn from OpenAPI documents, but no page we read links a spec as a download. The MCP tools page lists each tool's arguments, which we couldn't check as JSON Schema without a key. The earlier partial is kept (8 of 25). llms.txt, llms-full.txt and a .md twin for every docs page (10). The MCP tools page says what each tool returns and where coverage stops, such as MinuteCast and Lightning staying on REST (14 of 20). Parameters are documented, mostly location keys, language codes and booleans (10 of 15). Quick-start examples and an 11-row status code table, with RFC 7807 problem bodies carrying type, title, status and trace (13 of 15). Versioned /v1 paths, but no changelog or release notes anywhere on the portal, re-read on 4 November (5 of 15). 8 + 10 + 14 + 10 + 13 + 5 = 60.

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.

Reliability AccuWeather Core Weather API + MCP +7

AccuWeather Core Weather API + MCP 75

Status page at status.accuweather.com with Enterprise API and Developer Portal API components (20). Its history feed, read in full on 4 November, lists in the 90 days from 6 August intermittent degraded performance with 'our APIs' on 20 August (1 hour 22 minutes) and from 21 to 23 August, the Historical and Lightning APIs on 19 October and MinuteCast on 2 November. All four are degraded performance, three name one or two products, and none reports the API down, so they read as partial and the record is minor incidents only. The 26 August and 23 September entries were announced maintenance with windows (20 of 30). Call quotas published per package, 500 a day on the trial up to 2.4 million a month on Elite, but no per-second limit (15). 429 and 503 are defined in the status code table, and the MCP troubleshooting table says to 'Wait and retry' on 429, with no Retry-After header documented. Every call is a read. Backoff guidance alone (10). No SLA, and the terms cap liability at $100 (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

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.

Transparency & trust Visual Crossing Weather API +6

AccuWeather Core Weather API + MCP 51

Closed service with API terms last updated 28 April 2026, re-read on 4 November (15). The API terms let AccuWeather collect, store and use request data such as locations and IP addresses and point to the privacy policy on www.accuweather.com. That host's robots.txt answered Access Denied on 4 November, so the 1 October reading of the privacy policy (retention tied to the account) is struck. No DPA found. The terms clause partly meets the line, so the earlier partial is kept (12 of 30). The terms say AccuWeather 'may change the APIs at any time without notice' (0). The provider list and the United States processing statement came from the privacy policy and are struck (0 of 20). 15 + 12 + 0 + 0 = 27.

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.

Score by category

CategoryWeightAccuWeather Core Weather API + MCPVisual Crossing Weather APIEdge
Reliability16%7568AccuWeather Core Weather API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6074Visual Crossing Weather API +14
Agent ergonomics13%6078Visual Crossing Weather API +18
Security & auth14%3940Visual Crossing Weather API +1
Payments & pricing10%3883Visual Crossing Weather API +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%358Visual Crossing Weather API +55
Transparency & trust7%5157Visual Crossing Weather API +6
Negative events≤1500
TotalD 50.8/100B 65.7/100

Facts side by side

FactAccuWeather Core Weather API + MCPVisual Crossing Weather API
KindHTTP APIHTTP API
VendorAccuWeatherVisual Crossing
Hosted endpointhttps://dataservice.accuweather.comhttps://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Tools exposed271
Read-only variant documentedyesno
llms.txtyesyes
Terms last updated2026-04-282023-01-01
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Visual Crossing Weather API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

AccuWeather Core Weather API + MCP

An official hosted MCP server exposes all 106 Core Weather GET endpoints as 27 read-only tools on the same key as the REST API, and the status page shows only partial incidents since August. There is no changelog, the terms allow API changes without notice, and they forbid using the data to train or inform any AI system.

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.

Before you call either

AccuWeather Core Weather API + MCP

  1. Cache location keys. They don't change, and the lookup is the call worth saving
  2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns
  3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs
  4. On 429 wait and retry. On the trial it usually means the 500-call daily allowance is spent until it resets
  5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

Visual Crossing Weather API

  1. Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records
  2. Try the no-key route first for light use, and on a 429 slow down and retry with backoff rather than switching IP addresses
  3. Show 'Weather data provided by Visual Crossing Weather' near any displayed data on free use
  4. Pass unitGroup=metric. The default is US units
  5. Use the MCP server with X-VC-API-Key rather than pasting a key into a URL

Questions

Which is better for AI agents, AccuWeather Core Weather API + MCP or Visual Crossing Weather API?

Visual Crossing Weather API scores 65.7 (B) on agent readiness against AccuWeather Core Weather API + MCP's 50.8 (D), and leads in 6 of 7 scored categories. AccuWeather Core Weather API + MCP leads on reliability.

Do AccuWeather Core Weather API + MCP and Visual Crossing Weather API need an API key?

Both need an API key.

Can an agent call AccuWeather Core Weather API + MCP and Visual Crossing Weather API without installing anything?

Yes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and Visual Crossing Weather API at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline.

Other comparisons with AccuWeather Core Weather API + MCP or Visual Crossing Weather API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.