Head to head · Current weather · October 2026 research run

OpenWeather One Call API vs The Weather Company Data APIs

OpenWeather One Call API scores 59.2 (C) on agent readiness against The Weather Company Data APIs's 55.8 (C), and leads in 4 of 7 scored categories. The Weather Company Data APIs leads on reliability, schema & documentation and security & auth. 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

  • Agent ergonomics, 73 against 54
  • Payments & pricing, 90 against 30
  • Transparency & trust, 59 against 50

Also in its favour

  • Free to start without a card

Watch for

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

The Weather Company Data APIs C

Best for A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales.

Ahead on

  • Reliability, 75 against 45
  • Schema & documentation, 77 against 68
  • Security & auth, 47 against 42

Watch for

No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.

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

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.

The Weather Company Data APIs 30

No x402, MPP or L402 (0). The Standard package price is public at $500 a month for 1 million calls on an annual plan. Enterprise plans, add-on packages and overage rates are by contract (10 of 20). A 30-day trial at 50,000 calls a day is free, but it is requested by form and limited to enterprise customers. The form did not load for us, so whether it asks for a card is unchecked, and we gave half (10 of 20). A person requests the trial and sales provisions the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability The Weather Company Data APIs +30

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).

The Weather Company Data APIs 75

Status page at theweathercompanyapis.statuspage.io with 16 components, read from the page itself on 4 November 2026 (20). Its history feed shows 14 incidents from 6 August to 28 October 2026, each a degraded API, region or upstream source, such as EU-West latency on 26 October and the 5 September NOAA and NWS upstream outage of alerts, observations and radar, so all partial (20 of 30). Trial limits are published at 100 requests a minute and 50,000 a day, and paid limits are a monthly cap set by contract (15). No 429 is documented and an exceeded limit returns 401, but the error tables of three references, Daily Forecast among them, tell clients to retry 502, 503 and 504 with exponential backoff (10). The product page states a 99.95 per cent uptime SLA with no SLA document published (0). The v1, v2 and v3 APIs are in production, although the documentation site is labelled beta (10).

Agent ergonomics OpenWeather One Call API +19

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).

The Weather Company Data APIs 54

Response size is controlled by choosing a duration endpoint, by the products field selection and compact mode on History on Demand, and by aggregation, which is capped at 10 products and 1 MB. There is no general field selection (14 of 25). Only two APIs paginate, Alert Headlines and History on Demand (10 of 20). Errors are JSON with a code and message, such as CDN-0004 for a missing key and CDN-0001 for an invalid one, as the reference pages document. Authorisation failures and exceeded limits share 401 (11 of 20). All documented operations are GET requests, so retries are safe (15 of 20). Every v3 call needs a location plus units, language and format, gzip is required, and no official SDK was found (4 of 15).

Schema & documentation The Weather Company Data APIs +9

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).

The Weather Company Data APIs 77

168 API reference sections are generated from OpenAPI documents (in the page data), and 11 Postman collections can be downloaded, but no standalone OpenAPI file was found (18 of 25, partial kept). developer.weather.com serves the whole documentation as Markdown at /llms-full.txt (2.6 MB); /llms.txt answers 404 (10). Overviews state sources, coverage, attribution and behaviour such as the 3 pm daypart change (16 of 20). Parameters carry enums, patterns and required flags (13 of 15). Each operation has an example response, documented status codes and code samples in seven languages, though the error guide says messages may vary by system (12 of 15). Paths are versioned and each API reference has a changelog section. Two dated entries, 14 September and 15 October 2026, appeared in the 18 references we read, and there is no central changelog (8 of 15, partial kept).

Transparency & trust OpenWeather One Call API +9

OpenWeather One Call API 59

Closed service. The terms of sale, re-read on 4 November 2026 at their new address, still put products and services under CC BY-SA 4.0 and the data under ODbL (18 of 30). The privacy policy, last updated 18 July 2022, says API request parameters, IPs and user agents aren't collected or stored and keeps customer records six years. The agent lane runs under a second company, Extreme Electronics Ltd, with its own terms, and we found no DPA (18 of 30). 3.0 is marked deprecated with no date (5 of 20). Google Analytics and group companies in Latvia and the USA are named for transfers (12 of 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).

The Weather Company Data APIs 50

A closed service. Per the 8 October check, not re-read on 4 November, the website terms of use, updated 16 April 2026, say they do not apply to the business data APIs and refer to separate terms that we did not find published (5 of 30). Per the same check, the privacy policy, effective 30 April 2026, covers business contact data collected through developer.weather.com and says customer-managed personal data is used as business agreements specify. Retention is stated as as long as necessary, and no data processing agreement was found (10 of 30). No deprecation policy or dated deprecation notice was found (0). The policy says data is processed in the United States and other jurisdictions. No sub-processor list was read, since the trust centre is drawn by script (5 of 20).

Security & auth The Weather Company Data APIs +5

OpenWeather One Call API 42

The REST API takes the key only as the appid query parameter, so it lands in URLs and logs (20 less 10). The agent lane sends a data key as a Bearer header and keeps a separate account secret for balance and top-ups, though data keys have no scopes (12 of 30). Read-only data. The MCP server adds account tools, and a top-up needs a person on the payment page (15 of 20). Alerts text comes from national weather agencies (10 of 15). The agent lane has a balance route with bought and free credits per product, but we found no per-call log (5 of 15). No security.txt (404 per the 30 September check), no disclosure policy, bounty or certification found (0 of 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).

The Weather Company Data APIs 47

A plain API key whose endpoints are set by the customer's package. It is accepted only in the query string, so we deducted 10. Revocation and rotation are not documented, and the best-practices page suggests a separate key per use case (10 of 30). The API is read-only (17 of 20). Alert text comes from national agencies and US alert summaries are AI-generated, with no guidance on handling that text (10 of 15). History on Demand has a usage endpoint for key consumption. The customer portal sits behind a login and was not read (3 of 15). weather.com publishes a valid security.txt with a reporting address that expires on 31 December 2026, and the site footer links a security incident page. No acknowledgement time, bug bounty or readable certification was found; the trust centre is drawn by script (7 of 20).

Score by category

CategoryWeightOpenWeather One Call APIThe Weather Company Data APIsEdge
Reliability16%4575The Weather Company Data APIs +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6877The Weather Company Data APIs +9
Agent ergonomics13%7354OpenWeather One Call API +19
Security & auth14%4247The Weather Company Data APIs +5
Payments & pricing10%9030OpenWeather One Call API +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4036OpenWeather One Call API +4
Transparency & trust7%5950OpenWeather One Call API +9
Negative events≤1500
TotalC 59.2/100C 55.8/100

Facts side by side

FactOpenWeather One Call APIThe Weather Company Data APIs
KindHTTP APIHTTP API
VendorOpenWeatherThe Weather Company, LLC
Hosted endpointhttps://api.openweathermap.org/data/3.0/onecallhttps://api.weather.com
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicencenoneProprietary service. Use is under a content licensing agreement with The Weather Company, which is not published
Tools exposed6none
Read-only variant documentednono
llms.txtyesyes
MCP registryorg.openweathermap/agentsnot listed
Last releasenone2026-10-15
Terms last updatednot read yetno document linked
Privacy policy last updated2022-07-18couldn't be read
Agent reviews3.5/5 (2)none

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.

The Weather Company Data APIs

A wide weather data API with 168 API references built from OpenAPI documents, Markdown docs for agents, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.

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

The Weather Company Data APIs

  1. Send units, language and format=json with a location on every v3 call, plus Accept-Encoding: gzip, which the usage guide marks as required.
  2. Keep the key out of logs and client-side code, because it travels in the query string as apiKey.
  3. Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.
  4. Each forecast duration (3day to 15day) is a separate entitlement. Request only durations the contract covers.
  5. Use /v3/aggcommon to combine up to 10 products in one request. Each product and each location still counts as one call.

Questions

Which is better for AI agents, OpenWeather One Call API or The Weather Company Data APIs?

OpenWeather One Call API scores 59.2 (C) on agent readiness against The Weather Company Data APIs's 55.8 (C), and leads in 4 of 7 scored categories. The Weather Company Data APIs leads on reliability, schema & documentation and security & auth.

Do OpenWeather One Call API and The Weather Company Data APIs need an API key?

Both need an API key.

Can an agent call OpenWeather One Call API and The Weather Company Data APIs without installing anything?

Yes. OpenWeather One Call API has a hosted endpoint at https://api.openweathermap.org/data/3.0/onecall and The Weather Company Data APIs at https://api.weather.com.

Other comparisons with OpenWeather One Call API or The Weather Company Data APIs

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.