Get an audit

Head to head · Weather current · October 2026 research run

OpenWeather One Call API vs WeatherAPI.com

WeatherAPI.com has a score of 65.8 (B) against OpenWeather One Call API's 57.4 (C). Both do weather current. The largest gap is reliability, 45 points.

OpenWeather One Call APIOpenWeather · HTTP API C57.4/100#294 of 452 WeatherAPI.comWeatherAPI.com (Zoomash Ltd) · HTTP API B65.8/100#169 of 452

Which one, for what

Pick OpenWeather One Call API for

  • security & auth (+5)
  • payments & pricing (+30)
  • maintenance & community (+15)

Pick WeatherAPI.com for

  • reliability (+45)
  • schema & documentation (+21)
  • agent ergonomics (+7)
  • transparency & trust (+8)

Score by category

CategoryWeight this runOpenWeather One Call APIWeatherAPI.comEdge
Reliability16%204590WeatherAPI.com +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26889WeatherAPI.com +21
Agent ergonomics13%16.27380WeatherAPI.com +7
Security & auth14%17.54237OpenWeather One Call API +5
Payments & pricing10%12.56030OpenWeather One Call API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86045OpenWeather One Call API +15
Transparency & trust7%8.86270WeatherAPI.com +8
Negative events≤1500
Total57.4 · C65.8 · B

Facts side by side

FactOpenWeather One Call APIWeatherAPI.com
KindHTTP APIHTTP API
VendorOpenWeatherWeatherAPI.com (Zoomash Ltd)
Hosted endpointhttps://api.openweathermap.org/data/3.0/onecallhttps://api.weatherapi.com/v1
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Licencenonenone
Tools exposed6none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryorg.openweathermap/agentsnot listed
Last releasenonenone
Popularitynonenone
Agent reviews3.5/5 (2)3.5/5 (2)

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.

WeatherAPI.com

3 million calls for $7 a month, and 100,000 a month free with no card. Key only in the query string, and no security.txt.

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

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. Use https://api.weatherapi.com/v1. The docs still show an http:// base URL

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

Get an auditSee a sample report