Head to head · Current weather · October 2026 research run

Pirate Weather vs Weatherbit API

Pirate Weather scores 67.6 (B) on agent readiness against Weatherbit API's 52.9 (D), and leads in 6 of 7 scored categories. Both do current weather.

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

Which one, for what

Pirate Weather B

Best for Agents and apps that want Dark Sky-shaped forecasts, model transparency and deep history on a small budget.

Ahead on

  • Reliability, 75 against 66
  • Schema & documentation, 85 against 67
  • Agent ergonomics, 77 against 61
  • Security & auth, 45 against 39
  • Maintenance & community, 80 against 11

Also in its favour

  • Open source

Watch for

No SLA, and the terms call it best effort

Weatherbit API D

Best for An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The key is accepted only as the key query parameter, and the spec lists plain http as a scheme

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.

Maintenance & community Pirate Weather +69

Pirate Weather 80

Version 2.10.3 on 21 October 2026 (30). Four releases in the last 90 days, 2.10.0, 2.10.1 and 2.10.2 between 18 and 23 September and 2.10.3 on 21 October (20). Open issues per the 1 October check, not re-read on 1 November because GitHub's pages refuse our reader. 32 were open then, labelled and triaged, most of them requests for new capabilities or data sources, with two portal bugs marked 'awaiting developer response' since May and a new-account key error (#656) open since 7 July (20 of 25). The hosted MCP server isn't in the official registry, where only a third-party Pipeworx wrapper (0.2.0) appears, and there's no official SDK (0). Dependabot, CodeQL and test workflows on the code repository, with dependency bumps merged on 26 October and 1 November 2026 (10).

Weatherbit API 11

The latest dated API announcement on the blog is still 1 August 2025 on its RSS feed on 4 November, 460 days before this check. The help articles edited in 2026 and the June 2026 timestamps in the docs' sample responses record no change to the API, so they don't set recency (0 of 30). No dated changelog entry or release falls in the 90 days from 6 August (0 of 20). A public blog for API updates that has gone quiet, a help centre, and email support with a stated three business day response that we did not test (6 of 15). pyweatherbit 2.2.2 on PyPI dates from 14 February 2024 and is the only official SDK (3 of 15). Its repository, cloned on 4 November, has no CI and no commit since 13 February 2024 (2 of 10). 0 + 0 + 6 + 3 + 2 = 11.

Schema & documentation Pirate Weather +18

Pirate Weather 85

OpenAPI 3.1.0 spec in the docs repository, versioned 2.10.3 to match the API since 20 October 2026, with 18 parameters and 400, 401, 404, 429, 500 and 502 responses on the forecast path (25). No llms.txt (404 on docs.pirateweather.net), though the Markdown sources of the docs are public on GitHub (5 of 10). The API docs and data-sources page explain each block and which model fills each field. The 11 MCP tool docstrings are one line each, with no when-not-to-use (14 of 20). The spec has five enums and leaves exclude and include as comma strings. The MCP tools use Pydantic types with bounded latitude, longitude and day counts and enumerated units and languages (11 of 15). A full response example page, 292 example values in the spec and every error code explained (15). Semantic API versions and a dated changelog with a pull request behind every line (15).

Weatherbit API 67

Swagger 2.0 at weatherbit.io/static/swagger.json, version 2.0.0, with 21 GET paths, 37 response models and bodies for 400, 403, 429 and 500. It declares no security definition and lists plain http as a scheme (23 of 25, per the 8 October check, not re-read on 4 November). No llms.txt, which still returned 404 on 4 November, and no Markdown docs found (0). Each endpoint page lists parameters, return fields with types and a quota estimate, and warns against station lookups, but says little on when to pick one endpoint over another (13 of 20). units and lang are enums, 31 enum parameters in all. Location is six optional parameters with none marked required, and include and days carry no constraints in the spec (11 of 15). Request examples in curl, Ruby, Node.js and Python, sample responses and a status table with example bodies. Errors are one free-text string (12 of 15). The path is versioned as /v2.0. The changelog is a blog whose latest API post is still dated 1 August 2025 on its RSS feed on 4 November (8 of 15). 23 + 0 + 13 + 11 + 12 + 8 = 67.

Agent ergonomics Pirate Weather +16

Pirate Weather 77

exclude, blocks, hourly_indices, daily_indices and day_night_indices cut a response down to the rows asked for, and the MCP get_forecast tool returns a compact this-hour and today summary. Eleven MCP tools, so a little over the ten-tool line (22 of 25). Output-size controls cover what pagination would, since each call is one location (18 of 20). Error codes are documented with causes, and MCP tools return ok: false with the HTTP status and message, but there's no machine-readable error code in the body (15 of 20). Read-only GETs. The MCP tools carry no readOnlyHint annotations (14 of 20). One required argument, the coordinate or a city and country. No official SDK, though Dark Sky client libraries work against it (8 of 15).

Weatherbit API 61

This is an API with no MCP server. days and hours cap forecast length and include adds minutely data, alerts or lightning only on request. There is no field selection, and a daily forecast row carries about 40 fields (14 of 25). Date ranges, units, lang and a one-month cap per historical call. No pagination is needed (13 of 20). Five status codes with a JSON error string and no machine-readable code. 204 with an empty body means no data, and 403 covers both a missing key and a plan without access (12 of 20). All 21 endpoints are read-only GETs, safe to retry (15 of 20). Only key and a location are required and units default to metric. One official SDK, pyweatherbit for Python, last released in February 2024 (7 of 15). 14 + 13 + 12 + 15 + 7 = 61.

Reliability Pirate Weather +9

Pirate Weather 75

Status page at pirateweather.xitoring.io, linked from the home page and the changelog. It rendered only with JavaScript on 1 October and answered our reader with a Cloudflare bot check on 1 November, so the award rests on the 30 September check that it exists (20). The project's own incident reports page, now at docs.pirateweather.net, is readable. In the last 90 days it records one incident, on 27 August 2026, when a cleanup job at the Apiable portal removed about 140 subscriptions and revoked their keys while the API itself stayed up, a partial incident (20). Limits published with numbers, 10,000 calls a month free and 20,000 on the $2 plan, with Ratelimit-Limit, Ratelimit-Remaining and Ratelimit-Reset headers (15). 429 means the monthly quota is spent and the reset header says when it clears, and the docs say to retry a 500. No backoff guidance beyond that, though every call is a GET (10 of 15). The terms say best effort with no warranty, so no SLA (0). Version 2 of the API is the stable default (10).

Weatherbit API 66

Graded as a hosted service. Status page at status.weatherbit.io on UptimeRobot. Its monitors and history load by script from /api/ paths that the status host's robots.txt disallows, so on 4 November we couldn't see which parts of the service it covers, and the 8 October reading of three API monitors came from the same disallowed path and no longer counts. The line is kept at 20 as awarded on 8 October, as sendblue's and visual-crossing's UptimeRobot pages are, until the 15 or 20 reading for such pages is settled (20). The 8 October incident reading came from that path too, so the line takes the no-readable-history score, a limit of our reading and not a finding against Weatherbit (5). Requests per day and per second are published for every plan, 50 and 1 on Free up to 2 million and 150 on Business, re-read on 4 November (15). 429 is documented for both limits, every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and the help centre says to slow down or retry. No Retry-After or backoff schedule was found. Every call is a GET (11 of 15). The pricing table lists 99.5 per cent uptime on paid plans, which the help centre calls best effort, with custom SLAs on request and no published credits (5 of 10). The v2.0 API is generally available (10). 20 + 5 + 15 + 11 + 5 + 10 = 66.

Security & auth Pirate Weather +6

Pirate Weather 45

A plain API key from the Apiable portal. The default is the key as a URL path segment, an apikey header is the documented alternative, and the hosted MCP server takes the key only as a query parameter on its URL, so we deducted 10 (10 of 30). Read-only data, no write actions (15 of 20). Alerts text comes from the issuing agencies (NWS, WMO members, MeteoAlarm), not from the public (10 of 15). Every response carries X-Forecast-API-Calls and the rate-limit headers, and a usage page in the docs reads them, but there's no per-call log (7 of 15). No security.txt (404 on pirateweather.net and docs.pirateweather.net on 1 November) and no SECURITY.md in either repository. CodeQL and Dependabot run on the code repository. No bounty or certification (3 of 20).

Weatherbit API 39

One plain key per account on Free, Standard and Plus, up to 10 on Business. It is accepted only as the key query parameter, so it lands in URLs and logs, and the spec lists http beside https (20 less 10, 10 of 30). Read-only data with nothing to approve (15 of 20). Alert titles and descriptions are relayed from meteorological agencies, and the rest is numeric (10 of 15). Quota counters come back in response headers and from /subscription/usage, but no per-call log for the account holder was found in the docs (4 of 15). security.txt still returned 404 on 4 November, and no disclosure policy, bounty or certification was found on the site (0). 10 + 15 + 10 + 4 + 0 = 39.

Score by category

CategoryWeightPirate WeatherWeatherbit APIEdge
Reliability16%7566Pirate Weather +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8567Pirate Weather +18
Agent ergonomics13%7761Pirate Weather +16
Security & auth14%4539Pirate Weather +6
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8011Pirate Weather +69
Transparency & trust7%6663Pirate Weather +3
Negative events≤1500
TotalB 67.6/100D 52.9/100

Facts side by side

FactPirate WeatherWeatherbit API
KindHTTP APIHTTP API
VendorPirate WeatherWeatherbit LLC
Hosted endpointhttps://api.pirateweather.net/forecasthttps://api.weatherbit.io/v2.0
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (docs and spec), AGPL-3.0 (API code)Proprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT
Read-only variant documentednoyes
llms.txtnono
Last release2026-10-212025-08-01
Terms last updatednot read yet2025-05-01
Privacy policy last updatednot read yet2023-12-26
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 yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity907 stars78 PyPI/wk
Agent reviews4/5 (2)none

How the scores have moved

Verdicts

Pirate Weather

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

Weatherbit API

A read-only weather API with a Swagger 2.0 spec, quota headers on every response and published per-day and per-second limits for every plan. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.

Before you call either

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

Weatherbit API

  1. Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution
  2. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then
  3. Treat HTTP 204 with an empty body as no data found, not as an error
  4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
  5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0

Questions

Which is better for AI agents, Pirate Weather or Weatherbit API?

Pirate Weather scores 67.6 (B) on agent readiness against Weatherbit API's 52.9 (D), and leads in 6 of 7 scored categories.

Do Pirate Weather and Weatherbit API need an API key?

Both need an API key.

Can an agent call Pirate Weather and Weatherbit API without installing anything?

Yes. Pirate Weather has a hosted endpoint at https://api.pirateweather.net/forecast and Weatherbit API at https://api.weatherbit.io/v2.0.

Are Pirate Weather and Weatherbit API open source?

Pirate Weather is open source (Apache-2.0 (docs and spec), AGPL-3.0 (API code)). No open-source release is listed for Weatherbit API.

Other comparisons with Pirate Weather or Weatherbit 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.