Head to head · Weather current · October 2026 research run

OpenWeather One Call API vs Pirate Weather

Pirate Weather has a score of 66.2 (B) against OpenWeather One Call API's 57.4 (C). Both do weather current. The largest gap is reliability, 30 points.

Which one, for what

Pick OpenWeather One Call API for

  • payments & pricing (+30)

Pick Pirate Weather for

  • reliability (+30)
  • schema & documentation (+17)
  • maintenance & community (+20)
  • transparency & trust (+9)

Score by category

CategoryWeight this runOpenWeather One Call APIPirate WeatherEdge
Reliability16%204575Pirate Weather +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26885Pirate Weather +17
Agent ergonomics13%16.27377Pirate Weather +4
Security & auth14%17.54245Pirate Weather +3
Payments & pricing10%12.56030OpenWeather One Call API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86080Pirate Weather +20
Transparency & trust7%8.86271Pirate Weather +9
Negative events≤1500
Total57.4 · C66.2 · B

Facts side by side

FactOpenWeather One Call APIPirate Weather
KindHTTP APIHTTP API
VendorOpenWeatherPirate Weather
Hosted endpointhttps://api.openweathermap.org/data/3.0/onecallhttps://api.pirateweather.net/forecast
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneApache-2.0 (docs and spec), AGPL-3.0 (API code)
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.txtyesno
MCP registryorg.openweathermap/agentsnot listed
Last releasenone2026-09-23
Popularitynone907 stars
Agent reviews3.5/5 (2)4/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.

Pirate Weather

Named model sources and a documented priority order for every field. No SLA, and the terms call it best effort.

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

Pirate Weather

  1. Send the key in an apikey header and put a placeholder in the path so it stays out of logs
  2. Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
  3. Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
  4. Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
  5. Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day

Other comparisons with OpenWeather One Call API or Pirate Weather

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.