Head to head · Current weather · October 2026 research run

The Weather Company Data APIs vs WeatherAPI.com

WeatherAPI.com scores 66.5 (B) on agent readiness against The Weather Company Data APIs's 55.8 (C), and leads in 6 of 7 scored categories. The Weather Company Data APIs leads on security & auth. Both do current weather.

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

Which one, for what

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

  • Security & auth, 47 against 37

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.

WeatherAPI.com B

Best for Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.

Ahead on

  • Reliability, 80 against 75
  • Schema & documentation, 89 against 77
  • Agent ergonomics, 80 against 54
  • Payments & pricing, 45 against 30
  • Maintenance & community, 60 against 36
  • Transparency & trust, 65 against 50

Also in its favour

  • Free to start without a card

Watch for

Key only in the query string, keys can't be scoped, and no security.txt

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.

Agent ergonomics WeatherAPI.com +26

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

WeatherAPI.com 80

current_fields, day_fields and hour_fields trim responses, and aqi, alerts and days keep them small. The official MCP server has 11 tools (22 of 25). days, hour, field filters and bulk requests on Pro+ (17 of 20). Numeric error codes such as 1006 (no location found) and 2007 (quota exceeded) let an agent tell the cases apart (18 of 20). Read-only GETs, and the bulk POST only reads. The MCP tools carry no readOnlyHint annotations (13 of 20). Only key and q are required, and SDKs exist for Node.js, Java, PHP and Go, but none has a commit since 2021 (10 of 15).

Maintenance & community WeatherAPI.com +24

The Weather Company Data APIs 36

The Hourly Forecast Enterprise reference records a specification change on 15 October 2026 (a new windSpeedKnots field released on 22 October), 20 days before the check (30). Two dated changelog entries in the 90 days from 6 August (14 September and 15 October) in the 18 references we read, short of three (0). Support is by email and a ServiceNow customer portal, and the status page is updated during incidents. No public community channel was found (6 of 15). No official SDK was found (0). No package to assess (0).

WeatherAPI.com 60

The changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60.

Payments & pricing WeatherAPI.com +15

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.

WeatherAPI.com 45

No x402, MPP or L402 (0). Plan prices are public, from $7 a month for 3 million calls to High Volume at $1,275 a month for 500 million, but there's no per-call or overage price (10 of 20). Free at 100,000 calls a month with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust WeatherAPI.com +15

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

WeatherAPI.com 65

Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20).

Schema & documentation WeatherAPI.com +12

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

WeatherAPI.com 89

OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though q is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15).

Security & auth The Weather Company Data APIs +10

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

WeatherAPI.com 37

The key goes only in the key query parameter, so it lands in URLs and logs (20 less 10). Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, but none can be scoped, and Business adds IP blocking (12 of 30). Read-only data (15 of 20). Alerts come from government agencies (10 of 15). Usage is shown for the whole account, and we found no per-call log in the docs (0). No security.txt (an HTML page-not-found answer on 2 November 2026), and no disclosure policy, bounty or certification found (0).

Score by category

CategoryWeightThe Weather Company Data APIsWeatherAPI.comEdge
Reliability16%7580WeatherAPI.com +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7789WeatherAPI.com +12
Agent ergonomics13%5480WeatherAPI.com +26
Security & auth14%4737The Weather Company Data APIs +10
Payments & pricing10%3045WeatherAPI.com +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3660WeatherAPI.com +24
Transparency & trust7%5065WeatherAPI.com +15
Negative events≤1500
TotalC 55.8/100B 66.5/100

Facts side by side

FactThe Weather Company Data APIsWeatherAPI.com
KindHTTP APIHTTP API
VendorThe Weather Company, LLCWeatherAPI.com (Zoomash Ltd)
Hosted endpointhttps://api.weather.comhttps://api.weatherapi.com/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicenceProprietary service. Use is under a content licensing agreement with The Weather Company, which is not publishednone
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-15none
Terms last updatedno document linkedno date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Agent reviewsnone3.5/5 (2)

How the scores have moved

Verdicts

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.

WeatherAPI.com

WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found.

Before you call either

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.

WeatherAPI.com

  1. Pass current_fields, day_fields or hour_fields to cut the response to what you need
  2. Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429
  3. Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names
  4. Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms
  5. Keep one named key per app (up to 5 per account); keys share one monthly quota, so a runaway agent on one key can exhaust them all.

Questions

Which is better for AI agents, The Weather Company Data APIs or WeatherAPI.com?

WeatherAPI.com scores 66.5 (B) on agent readiness against The Weather Company Data APIs's 55.8 (C), and leads in 6 of 7 scored categories. The Weather Company Data APIs leads on security & auth.

Do The Weather Company Data APIs and WeatherAPI.com need an API key?

Both need an API key.

Can an agent call The Weather Company Data APIs and WeatherAPI.com without installing anything?

Yes. The Weather Company Data APIs has a hosted endpoint at https://api.weather.com and WeatherAPI.com at https://api.weatherapi.com/v1.

Other comparisons with The Weather Company Data APIs or WeatherAPI.com

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.