Head to head · Current weather · October 2026 research run
Pirate Weather vs Tomorrow.io Weather API
Pirate Weather scores 67.6 (B) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in every scored category. Both do current weather.
Best weather and climate data APIs for AI agents · All 136 weather comparisons
Which one, for what
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 60
- Schema & documentation, 85 against 75
- Security & auth, 45 against 34
- Payments & pricing, 45 against 30
- Maintenance & community, 80 against 27
- Transparency & trust, 66 against 53
Also in its favour
- Free to start without a card
- Open source
Watch for
No SLA, and the terms call it best effort
Best for Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public price for paid use. The plan table lists Free and Enterprise, the second by quote
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 +53
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).
Tomorrow.io Weather API 27
The newest release-note entry is October 2026, dated by month only, with the Bulk Timelines API, Density Altitude and new probability layers, a Dew Point Depression core layer and new aviation altitudes. A month-only entry is dated to its month, and October runs 4 to 34 days back, so it can't show a change within 30 days (20). The page was last updated on 13 October 2026, and the 8 October check saw July as the newest entry. That is one dated entry since 6 August, not three (0). Release notes with five entries in thirteen months, a status page updated several times a week, and a help centre that answered 403 on 8 October, not re-read. The community repository on GitHub was last pushed in April 2021, per the 8 October check (7 of 15). No official SDK, and no registry presence read in this run (0). No packages to assess (0). 20 + 0 + 7 + 0 + 0 = 27.
Reliability Pirate Weather +15
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).
Tomorrow.io Weather API 60
Graded as a hosted service. Status page at status.tomorrow.io on Atlassian Statuspage, with 22 components on its history page, among them Timeline API, Historical API, Alerts API and Gale AI (20). The history pages list 37 incidents between 7 August and 3 November 2026, most of them stale or degraded data for a region or product. Two are labelled major. Recently created insights and monitors produced stale data on 12 August (12:46 to 16:30 UTC, Insights API and Alerts API), and Next Gen FOCUS regional forecast data was missing for some regions on 14 August (15:15 to 01:00 UTC, CONUS unaffected). Each hit one product or a set of regions, so both read as partial and the record is minor incidents only (20). The rate-limit page says limits are per hour and day by plan and gives no numbers (0 of 15). 429 is documented for a passed limit, and the errors page gives Retry-After and 'wait and retry' for 503, with no idempotency keys or safe-retry guidance on the location, insight and alert writes, so Retry-After alone (10). The pricing page lists Custom SLAs on Enterprise and its title claims 99.9% uptime, but no SLA document was found, and a listed SLA nobody could read gives 0 (0). Version 4 of the REST API is generally available (10). 20 + 20 + 0 + 10 + 0 + 10 = 60.
Payments & pricing Pirate Weather +15
Pirate Weather 45
No x402, MPP or L402 (0). The free tier and the $2 plan are published, but higher plans sit in the Apiable portal, which rendered only with JavaScript on 1 October and whose host answered robots.txt with 403 AccessDenied on 1 November, so we count plan pricing that's partly public (10 of 20). 10,000 calls a month free with no card, per the 30 September check (20). A person has to sign up at pirate-weather.apiable.io and subscribe, and the key can take 20 minutes to go live (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Tomorrow.io Weather API 30
No x402, MPP or L402 in the docs or the OpenAPI file. A 402 response exists for spent tokens, with no payment protocol behind it (0). The plan table is public and lists what Free includes, but Enterprise is by quote and token prices for the Historical API aren't published (5 of 20). A free plan with a 5-day forecast, 24 hours of history, one monitored location and one alert. The pages read name no card or payment step, but the signup form is a script-rendered app we couldn't read (15 of 20). A person signs up in a browser. The MCP OAuth flow registers clients by API but still needs a human login (0). 0 + 5 + 15 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Transparency & trust Pirate Weather +13
Pirate Weather 66
The API code is AGPL-3.0 and the docs and OpenAPI spec are Apache-2.0. We took 5 off the 30 because the terms say nothing about reusing response data (25 of 30). The privacy notice is a generator template last updated 23 September 2024, with retention 'as long as necessary' and no DPA. It agrees with itself but says little (12 of 30). Version 1 and 2 response shapes are both kept, and the changelog dates every change, but there's no written deprecation policy (10 of 20). The privacy notice names Apiable and Stripe, and the infrastructure blog posts name AWS ECS, Aurora PostgreSQL and Kong, but no data locations are stated (8 of 20).
Tomorrow.io Weather API 53
Closed service under subscription terms at www.tomorrow.io/legal/terms-of-service/. robots.txt on www.tomorrow.io closes /legal/ to every reader, as our policy reader recorded on 8 October, so the 8 October readings of the terms, the product privacy policy and the data sources page are struck. The terms are published but unread on a host that refuses us, which keeps the licence line at 15, as for linkedin-marketing-api and figma-mcp. The plans page footer names The Tomorrow Companies Inc. in Boston (15 of 30). Data handling rested only on the struck privacy reading, and no docs page states retention or deletion, so the line is 0, as struck evidence is for x-mcp and hexis (0 of 30). The versioning policy promises notice far in advance of a breaking change with no period, and the docs mark the best timestep as deprecated without a date (6 of 20). Subprocessors and data locations rested only on the struck privacy and data sources readings (0 of 20). 15 + 0 + 6 + 0 = 21.
Security & auth Pirate Weather +11
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).
Tomorrow.io Weather API 34
The docs state that API keys carry full privileges, with one default key on the dashboard and more keys created by an account manager. The key may travel as an apikey query parameter, which the OpenAPI file declares as the scheme, or as a header. The MCP endpoint also advertises OAuth with dynamic client registration, PKCE (S256) and one scope, mcp:read, in its live metadata, which the MCP docs page doesn't mention (12 of 30, after the 10-point deduction for a secret in the URL). Weather calls only read, the OAuth scope is read-only, and the key can also create, change and delete locations, insights and alerts with no confirmation step (10 of 20). Responses are mostly numeric fields. Gale AI returns generated text and the feeds carry third-party event text, with no guidance on treating it as untrusted (8 of 15). An X-Correlation-ID on every response and an Activity section in the dashboard for webhooks. No per-call log was found in the docs (4 of 15). No security.txt (404 on www on 4 November 2026, and on the apex and api hosts per the 8 October check), and no disclosure policy, bounty or certification found on the pages read or by a site search (0 of 20). 12 + 10 + 8 + 4 + 0 = 34.
Schema & documentation Pirate Weather +10
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).
Tomorrow.io Weather API 75
OpenAPI 3.1.0 file at docs.tomorrow.io/openapi/tomorrowio-api.json, version 4.0.1, 31 paths and 39 operations (25). llms.txt at docs.tomorrow.io/llms.txt, and every reference page is served as Markdown at the same address with .md added (10). The specification has 40 empty descriptions, while the reference pages and the MCP page state purpose and use cases, and the MCP page says when to prefer the structured tools over the Gale AI question tool (12 of 20). One enum in the whole specification. location is a free string that takes coordinates, a city, a US zip or UK postcode, a location ID or GeoJSON, and fields is an untyped array (7 of 15). Example responses on each page and an error table with 15 numbered codes, though most operations declare only a 200 response (11 of 15). A written versioning policy that names which changes raise the version, and release notes dated by month with five entries from October 2025 to October 2026 (10 of 15). 25 + 10 + 12 + 7 + 11 + 10 = 75.
Score by category
| Category | Weight | Pirate Weather | Tomorrow.io Weather API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 60 | Pirate Weather +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 75 | Pirate Weather +10 |
| Agent ergonomics | 13% | 77 | 73 | Pirate Weather +4 |
| Security & auth | 14% | 45 | 34 | Pirate Weather +11 |
| Payments & pricing | 10% | 45 | 30 | Pirate Weather +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 27 | Pirate Weather +53 |
| Transparency & trust | 7% | 66 | 53 | Pirate Weather +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 67.6/100 | D 52.8/100 |
Facts side by side
| Fact | Pirate Weather | Tomorrow.io Weather API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Pirate Weather | The Tomorrow Companies Inc. |
| Hosted endpoint | https://api.pirateweather.net/forecast | https://api.tomorrow.io/v4 |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (docs and spec), AGPL-3.0 (API code) | Proprietary service under Tomorrow.io's subscription terms |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-21 | 2026-10-13 |
| Terms last updated | not read yet | couldn't be read |
| Privacy policy last updated | not read yet | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | 907 stars | none |
| Agent reviews | 4/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.
Tomorrow.io Weather API
A public OpenAPI 3.1 file, Markdown docs with llms.txt and a hosted MCP server with 11 tools suit agents, and a free plan exists. Paid prices are by quote, the docs give no numeric rate limits, no SLA document or security.txt was found, and the status page lists 37 incidents in 90 days, mostly stale or degraded regional data.
Before you call either
Pirate Weather
- Send the key in an apikey header and put a placeholder in the path so it stays out of logs
- Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
- Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
- Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
- Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day
Tomorrow.io Weather API
- Send the key in the
apikeyheader, not the query string, so it stays out of URLs and logs - Request only the
fieldsandtimestepsneeded on POST /timelines. Free plans cover 24 hours back and 5 days ahead at1hand1d - Split archive requests. POST /historical takes at most 31 days per call and deducts tokens, 1 for a point and 10 for a polygon
- Treat code 401001 as a missing or bad key and stop retrying
- On 429 back off without a hint.
Retry-Afteris documented only for 503 - Expect stale or degraded data for some regions during incidents. status.tomorrow.io has components per API
Questions
Which is better for AI agents, Pirate Weather or Tomorrow.io Weather API?
Pirate Weather scores 67.6 (B) on agent readiness against Tomorrow.io Weather API's 52.8 (D), and leads in every scored category.
Do Pirate Weather and Tomorrow.io Weather API need an API key?
Pirate Weather needs an API key. Tomorrow.io Weather API takes an API key or an OAuth sign-in.
Can an agent call Pirate Weather and Tomorrow.io Weather API without installing anything?
Yes. Pirate Weather has a hosted endpoint at https://api.pirateweather.net/forecast and Tomorrow.io Weather API at https://api.tomorrow.io/v4.
Are Pirate Weather and Tomorrow.io Weather 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 Tomorrow.io Weather API.
Other comparisons with Pirate Weather or Tomorrow.io Weather API
- AccuWeather Core Weather API + MCP vs Pirate Weather
- AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs Pirate Weather
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Met Office Weather DataHub (Site Specific) vs Pirate Weather
- Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API
- meteoblue Weather API vs Pirate Weather
- meteoblue Weather API vs Tomorrow.io Weather API
- Meteomatics Weather API vs Pirate Weather
- Meteomatics Weather API vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs Pirate Weather
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- OpenWeather One Call API vs Pirate Weather
- OpenWeather One Call API vs Tomorrow.io Weather API
- Pirate Weather vs Visual Crossing Weather API
- Pirate Weather vs The Weather Company Data APIs
- Pirate Weather vs WeatherAPI.com
- Pirate Weather vs Weatherbit API
- Pirate Weather vs Xweather Weather API
- Tomorrow.io Weather API vs Visual Crossing Weather API
- Tomorrow.io Weather API vs The Weather Company Data APIs
- Tomorrow.io Weather API vs WeatherAPI.com
- Tomorrow.io Weather API vs Weatherbit API
- Tomorrow.io Weather API vs Xweather Weather API
- Meteosource Weather MCP vs Pirate Weather
- Meteosource Weather MCP vs Tomorrow.io Weather API
- Pirate Weather vs Stormglass API
- Stormglass API vs Tomorrow.io Weather API
- Open-Meteo vs Pirate Weather
- Open-Meteo vs Tomorrow.io Weather API
Machine-readable
- This page as Markdown
/compare/pirate-weather-vs-tomorrow-io.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pirate-weather.json·/api/v1/tools/tomorrow-io.json - From a terminal
anchor compare pirate-weather tomorrow-io(the CLI) - Over MCP
compare_tools {"a": "pirate-weather", "b": "tomorrow-io"}at/mcp, no key