Head to head · Current weather · October 2026 research run

OpenWeather One Call API vs Visual Crossing Weather API

Visual Crossing Weather API scores 65.7 (B) on agent readiness against OpenWeather One Call API's 59.2 (C), and leads in 4 of 7 scored categories. OpenWeather One Call 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

OpenWeather One Call API C

Best for Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key.

Ahead on

  • Payments & pricing, 90 against 83

Watch for

The main API takes the key only as the appid query parameter

Visual Crossing Weather API B

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

Ahead on

  • Reliability, 68 against 45
  • Schema & documentation, 74 against 68
  • Agent ergonomics, 78 against 73
  • Maintenance & community, 58 against 40

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.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.

Reliability Visual Crossing Weather API +23

OpenWeather One Call API 45

No public status page found, and status.openweathermap.org doesn't resolve (0). No incident history to read (5). Limits published with numbers, 1,000 One Call calls a day free, a default cap of 2,000 a day you can change, and 60 a minute on the Free plan (15). 429 is documented as quota exceeded, and the agent lane says its 429 names the interval to wait. All calls are GETs (10 of 15). The subscription table publishes uptime of 95 to 99.9 per cent for the Startup to Expert plans, but nothing for One Call by Call (5 of 10). One Call 4.0 is the current version (10). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

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.

Maintenance & community Visual Crossing Weather API +18

OpenWeather One Call API 40

The newest dated release is the MCP server's version 0.3.0, published to the official registry on 4 September 2026, 61 days before this check (20). In the 90 days from 6 August, MCP 0.2.0 and 0.3.0 on 4 September and the agent terms revision of 23 September, which isn't a release. Two releases, short of the three the line needs, and no dated API changelog (0). No public changelog for One Call. Support is through the help desk, which we didn't test (5 of 15). The MCP server is in the official registry as org.openweathermap/agents, a domain-verified namespace (15). No package to judge (0). 20 + 0 + 5 + 15 + 0 = 40.

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 OpenWeather One Call API +7

OpenWeather One Call API 90

No x402, MPP or L402. The agent lane's top-ups are card only and need a person (0). Per-call prices published without login, $0.0015 a call on One Call by Call and $0.001 a call on the agent lane (20). The agent lane gives every account 1,000 One Call credits a day with only an email (20). POST an email to agents.openweathermap.org/v1/accounts and the data key comes back in the response (20). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

Schema & documentation Visual Crossing Weather API +6

OpenWeather One Call API 68

No OpenAPI for the main REST API. The agent lane links an openapi.yaml and an errors.json dictionary, which we couldn't parse, so partial credit (12 of 25). llms.txt on openweathermap.org and on the agent lane, with a Markdown guide and llms-full.txt (10). Each response field is described, and the 3.0 page tells new integrations to use 4.0 (14 of 20). exclude and units values are listed in the docs, not in a contract (10 of 15). JSON examples for every endpoint, and errors documented as 400, 401, 404, 429 and 5xx with a cod, message and parameters body (15). Versioned paths, but no public changelog and no date for retiring 3.0 (7 of 15). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

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.

Agent ergonomics Visual Crossing Weather API +5

OpenWeather One Call API 73

exclude drops current, minutely, hourly, daily or alerts blocks on 3.0, and 4.0 splits the timeline by step (1 minute, 15 minutes, hour, day). The MCP server has six tools (20 of 25). 4.0 takes a start parameter to page through timelines (16 of 20). Error bodies carry a code and message, and the agent lane's errors.json gives each code with its HTTP status and the reaction to take (18 of 20). Read-only GETs, and the agent lane bills only 2xx responses. We didn't see MCP annotations (14 of 20). Three required parameters, but units defaults to Kelvin and there's no official SDK (5 of 15). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).

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.

Score by category

CategoryWeightOpenWeather One Call APIVisual Crossing Weather APIEdge
Reliability16%4568Visual Crossing Weather API +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6874Visual Crossing Weather API +6
Agent ergonomics13%7378Visual Crossing Weather API +5
Security & auth14%4240OpenWeather One Call API +2
Payments & pricing10%9083OpenWeather One Call API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4058Visual Crossing Weather API +18
Transparency & trust7%5957OpenWeather One Call API +2
Negative events≤1500
TotalC 59.2/100B 65.7/100

Facts side by side

FactOpenWeather One Call APIVisual Crossing Weather API
KindHTTP APIHTTP API
VendorOpenWeatherVisual Crossing
Hosted endpointhttps://api.openweathermap.org/data/3.0/onecallhttps://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Tools exposed61
Read-only variant documentednono
llms.txtyesyes
MCP registryorg.openweathermap/agentsnot listed
Terms last updatednot read yet2023-01-01
Privacy policy last updated2022-07-18no date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates 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

OpenWeather One Call API

1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.

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

OpenWeather One Call API

  1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once
  2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance
  3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop
  4. Pass units=metric. The default is Kelvin
  5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses

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, OpenWeather One Call API or Visual Crossing Weather API?

Visual Crossing Weather API scores 65.7 (B) on agent readiness against OpenWeather One Call API's 59.2 (C), and leads in 4 of 7 scored categories. OpenWeather One Call API leads on payments & pricing.

Do OpenWeather One Call API and Visual Crossing Weather API need an API key?

Both need an API key.

Can an agent call OpenWeather One Call API and Visual Crossing Weather API without installing anything?

Yes. OpenWeather One Call API has a hosted endpoint at https://api.openweathermap.org/data/3.0/onecall and Visual Crossing Weather API at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline.

Other comparisons with OpenWeather One Call API 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.