{ "data": { "a": { "slug": "tomorrow-io", "name": "Tomorrow.io Weather API", "vendor": "The Tomorrow Companies Inc.", "vendorUrl": "https://www.tomorrow.io", "kind": "http-api", "category": "weather", "summary": "Tomorrow.io's Weather API returns current conditions, forecasts, recent and archived history, map tiles, route weather and alert webhooks for a coordinate, place name or GeoJSON shape. It is a REST API with a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/tomorrow-io", "markdownUrl": "https://www.anchorterminal.com/tools/tomorrow-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomorrow-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json", "license": "Proprietary service under Tomorrow.io's subscription terms", "transports": [ "http" ], "remoteUrl": "https://api.tomorrow.io/v4", "packages": [], "auth": "mixed", "authNotes": "A person signs up in a browser and copies the key from the dashboard. The key goes in an `apikey` header or query parameter on REST calls and in `X-Api-Key` for the MCP server. The docs say keys carry full privileges, and more keys are created by an account manager. The MCP endpoint also advertises OAuth with dynamic client registration, PKCE and one scope, `mcp:read`.", "pricing": "freemium", "pricingNotes": "Free plan with no published price for anything above it. Free covers core data layers, a 5-day forecast, 24 hours of history, one monitored location and one alert, and the terms bar commercial use on self-generated accounts. Enterprise is by quote and adds the 14-day forecast, premium layers, routes, maps and the historical archive, which is metered in tokens with no public token price (https://www.tomorrow.io/weather-api/, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the plan table (checked 2026-10-08).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.tomorrow.io/reference/welcome", "llmsTxt": "https://docs.tomorrow.io/llms.txt", "openapi": "https://docs.tomorrow.io/openapi/tomorrowio-api.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "openapi", "llms-txt", "mcp", "webhooks", "status-page", "sales-led", "us" ], "lastRelease": "2026-07-14", "graded": true, "anchor": { "graded": true, "score": 51.4, "grade": "D", "agentReady": false, "rank": 578, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 27, "payments": 20, "reliability": 55, "schema": 75, "security": 34, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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 only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data.", "bestFor": "Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.", "strengths": [ "Public OpenAPI 3.1.0 file (version 4.0.1, 31 paths, 39 operations), plus llms.txt and a Markdown copy of every docs page", "Hosted MCP server at api.tomorrow.io/v4/tomorrow-weather/mcp with 11 documented tools, added in April 2026", "The `fields`, `timesteps`, `startTime` and `endTime` parameters size a Timelines response to what the task needs", "Six-digit error codes that the docs say stay fixed, and soft warnings returned beside partial data", "Alert webhooks signed with HMAC-SHA256 in an `X-Signature` header, retried up to two times" ], "weaknesses": [ "No public price for paid use. The plan table lists Free and Enterprise, the second by quote", "The subscription terms bar commercial use on self-generated accounts and forbid storing unaltered data without an order", "No numeric rate limits in the reviewed docs, and remaining-limit headers are documented for Enterprise accounts only", "Keys carry full privileges and may be sent as an `apikey` query parameter. More keys come through an account manager", "50 incidents on the status page between 15 July and 2 October 2026, 25 naming the Timeline or Historical API", "No official SDK, no security.txt, and no certification or disclosure policy found on the pages read" ], "agentNotes": [ "Send the key in the `apikey` header, not the query string, so it stays out of URLs and logs", "Request only the `fields` and `timesteps` needed on POST /timelines. Free plans cover 24 hours back and 5 days ahead at `1h` and `1d`", "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 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026", "On 429 back off without a hint. `Retry-After` is documented only for 503", "Check the plan's terms before storing or reselling responses. Free accounts are limited to non-commercial use with a Powered by Tomorrow.io link" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.4 } ], "editorialScores": { "ergonomics": 73, "maintenance": 27, "payments": 20, "reliability": 55, "schema": 75, "security": 34, "transparency": 42 }, "provenanceScore": 84 }, "connect": { "http": "curl --request GET --url 'https://api.tomorrow.io/v4/weather/realtime?location=42.3478,-71.0466' --header 'apikey: API_KEY'", "config": { "mcpServers": { "tomorrow-weather-mcp": { "headers": { "X-Api-Key": "${TOMORROW_API_KEY}" }, "type": "http", "url": "https://api.tomorrow.io/v4/tomorrow-weather/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/tomorrow-io" }, "area": "domain-data", "provenance": { "legalEntity": "The Tomorrow Companies Inc.", "domain": "tomorrow.io", "domainRegistered": "2012-02-15", "endpointOnVendorDomain": true, "terms": "https://www.tomorrow.io/legal/terms-of-service/", "privacy": "https://www.tomorrow.io/legal/product-privacy-policy/", "statusPage": "https://status.tomorrow.io", "changelog": "https://docs.tomorrow.io/reference/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The subscription terms (last updated 19 October 2023) name The Tomorrow Companies Inc., a Delaware corporation with its principal place of business in Boston, Massachusetts, and cover the API, the dashboard and the data portal.", "The product privacy policy (last updated 17 December 2024) covers the API and platform and names Tomorrow.io Inc. as operator. The website has a separate privacy policy and terms of use, which we did not use here.", "The API and the MCP server answer at api.tomorrow.io.", "www.tomorrow.io, tomorrow.io and api.tomorrow.io each return 404 for /.well-known/security.txt.", "RDAP gives a registration date of 2012-02-15 for tomorrow.io. The status page runs on Atlassian Statuspage." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomorrow-io.json", "live": { "slug": "tomorrow-io", "probe": { "target": "https://api.tomorrow.io/v4", "method": "get", "lastAt": "2026-10-08T21:12:23.748190463Z", "lastOk": true, "lastStatus": 404, "lastMs": 136, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 152, "p95ms24h": 185, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-08", "probes": 41, "ok": 41 } ] }, "vendorStatus": { "page": "https://status.tomorrow.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:28.336264349Z" }, "pages": [ { "url": "https://docs.tomorrow.io/reference/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:37.617241436Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5c08804d147f" }, { "url": "https://www.tomorrow.io/legal/product-privacy-policy/", "kind": "privacy", "status": 0, "checkedAt": "2026-10-08T18:31:01.004304542Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true }, { "url": "https://www.tomorrow.io/legal/terms-of-service/", "kind": "terms", "status": 0, "checkedAt": "2026-10-08T18:31:01.446636319Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-10-08T21:12:23.748190463Z" } }, "answer": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust.", "b": { "slug": "weather-company", "name": "The Weather Company Data APIs", "vendor": "The Weather Company, LLC", "vendorUrl": "https://www.weathercompany.com", "kind": "http-api", "category": "weather", "summary": "The Weather Company Data APIs return current conditions, forecasts to 15 days, historical data, government alerts, imagery and aviation weather from the company behind weather.com. Access is by API key at `api.weather.com`, sold in packages to businesses.", "url": "https://www.anchorterminal.com/tools/weather-company", "markdownUrl": "https://www.anchorterminal.com/tools/weather-company.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/weather-company.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/weather-company.json", "license": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "transports": [ "http" ], "remoteUrl": "https://api.weather.com", "packages": [], "auth": "api-key", "authNotes": "An API key is required and is sent as the `apiKey` query parameter on every request. No header option is documented. Keys are not self-serve. A person requests a 30-day trial by form or contacts sales, the company provisions the key, and the key is read in the API customer portal after an invitation. Each key is entitled to the endpoints in the customer's package, and an endpoint outside it returns 401.", "pricing": "paid", "pricingNotes": "Standard package $500 a month on an annual plan for 1 million API calls. Enterprise plans and add-on packages are by quote, and overage is charged as the contract defines. A free 30-day trial allows 50,000 calls a day at 100 a minute, is requested by form and is limited to enterprise customers, so an agent cannot start without a person and sales approval (checked 2026-10-08).", "priceSummary": "$500 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer documentation, the API references or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.weather.com/docs/home", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "paid", "enterprise", "sales-led", "closed-source", "status-page", "api-key", "aviation", "air-quality" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 52.6, "grade": "D", "agentReady": false, "rank": 565, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 73, "schema": 67, "security": 48, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, 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.", "bestFor": "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.", "strengths": [ "168 API reference sections on developer.weather.com are generated from OpenAPI documents, with enums, patterns, required fields, example responses and 13 response codes per operation.", "The Standard package covers current conditions, daily and hourly forecasts to 15 days, alerts from six national agencies, imagery, marine tiles, tides and air quality.", "History on Demand returns hourly gridded history at about 4 km from June 2015, in JSON, CSV or Parquet, with paging, field selection and a compact mode.", "The status page lists 16 components. Its feed shows nine incidents between 10 July and 8 October 2026, all rated minor or none.", "The Standard package price is public, $500 a month on an annual plan for 1 million calls, and the trial allows 50,000 calls a day for 30 days." ], "weaknesses": [ "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.", "The API key is accepted only as the `apiKey` query parameter, so it appears in every request URL. No header option is documented.", "The website terms of use say they do not apply to the data APIs and point to separate terms, which we did not find published.", "Exceeding a rate limit returns 401, the same status as a missing key. No 429, Retry-After or backoff guidance is documented.", "No llms.txt, no downloadable OpenAPI file, no official SDK and no MCP server were found. Only one dated changelog entry appeared in 42 API references sampled." ], "agentNotes": [ "Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.", "Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.", "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.", "Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.", "Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.6 } ], "editorialScores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 73, "schema": 67, "security": 48, "transparency": 20 }, "provenanceScore": 77 }, "connect": { "http": "curl --compressed \"https://api.weather.com/v3/wx/forecast/daily/3day?geocode=33.74,-84.39\u0026units=e\u0026language=en-US\u0026format=json\u0026apiKey=$TWC_API_KEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/weather-company" }, "area": "domain-data", "unitPrices": [ { "item": "Standard package, annual plan", "unit": "month", "usd": 500, "note": "1 million API calls a month" }, { "item": "Call on Standard, at the plan cap", "unit": "1k-requests", "usd": 0.5, "note": "$500 over 1 million calls" } ], "provenance": { "legalEntity": "The Weather Company, LLC", "domain": "weather.com", "domainRegistered": "1994-08-09", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://weather.com/privacy/privacy-policy", "statusPage": "https://theweathercompanyapis.statuspage.io", "changelog": "", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy policy, effective 30 April 2026, names The Weather Company, LLC, 1001 Summit Boulevard NE, Brookhaven, GA 30319. Its section on data collection outside consumer products covers developer.weather.com enquiries and business customers.", "No terms document is given. The website terms of use (updated 16 April 2026) say they do not apply to the business data APIs, and the separate terms they refer to were not found on the pricing, trial or documentation pages.", "The API answers at api.weather.com and the documentation at developer.weather.com. The company site is www.weathercompany.com (registered 1998-03-24).", "weather.com/.well-known/security.txt gives a security contact and expires on 31 December 2026. www.weathercompany.com and developer.weather.com return 404 for the same path.", "RDAP for weather.com gives a registration date of 1994-08-09 and CSC Corporate Domains, Inc. as registrar.", "There is no central changelog. Each API reference has its own changelog section, most of them empty." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/weather-company.json", "live": { "slug": "weather-company", "probe": { "target": "https://api.weather.com", "method": "get", "lastAt": "2026-10-08T21:12:25.691314952Z", "lastOk": true, "lastStatus": 401, "lastMs": 19, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 23, "p95ms24h": 64, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://theweathercompanyapis.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:30.225974996Z" }, "updatedAt": "2026-10-08T21:12:25.691314952Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "The Tomorrow Companies Inc.", "b": "The Weather Company, LLC", "name": "Vendor" }, { "a": "https://api.tomorrow.io/v4", "b": "https://api.weather.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Tomorrow.io's subscription terms", "b": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "name": "Licence" }, { "a": "11", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-07-14", "b": "2026-09-14", "name": "Last release" }, { "a": "couldn't be read", "b": "no document linked", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust.", "question": "Which is better for AI agents, Tomorrow.io Weather API or The Weather Company Data APIs?" }, { "answer": "Tomorrow.io Weather API takes an API key or an OAuth sign-in. The Weather Company Data APIs needs an API key.", "question": "Do Tomorrow.io Weather API and The Weather Company Data APIs need an API key?" }, { "answer": "Yes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and The Weather Company Data APIs at https://api.weather.com.", "question": "Can an agent call Tomorrow.io Weather API and The Weather Company Data APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 75 against 67", "Agent ergonomics, 73 against 54", "Transparency \u0026 trust, 63 against 49" ], "also": null, "goodFor": "Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.", "slug": "tomorrow-io", "watchFor": "No public price for paid use. The plan table lists Free and Enterprise, the second by quote" }, { "aheadOn": [ "Reliability, 73 against 55", "Security \u0026 auth, 48 against 34", "Maintenance \u0026 community, 36 against 27" ], "also": null, "goodFor": "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.", "slug": "weather-company", "watchFor": "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." } ], "job": { "capability": "weather.current", "name": "Weather current" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.json", "title": "AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.json", "title": "AccuWeather Core Weather API + MCP vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io.json", "title": "Google Weather API (Maps Platform) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company.json", "title": "Google Weather API (Maps Platform) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io.json", "title": "Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company.json", "title": "Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.json", "title": "meteoblue Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.json", "title": "meteoblue Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json", "title": "Meteomatics Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "title": "Meteomatics Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company.json", "title": "NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.json", "title": "OpenWeather One Call API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.json", "title": "OpenWeather One Call API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io.json", "title": "Pirate Weather vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company.json", "title": "Pirate Weather vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.json", "title": "Tomorrow.io Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.json", "title": "Tomorrow.io Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.json", "title": "Tomorrow.io Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather.json", "title": "Tomorrow.io Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.json", "title": "Visual Crossing Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.json", "title": "The Weather Company Data APIs vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.json", "title": "The Weather Company Data APIs vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-xweather.json", "title": "The Weather Company Data APIs vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-xweather" } ], "scores": [ { "by": 18, "edge": "weather-company", "key": "reliability", "name": "Reliability", "tomorrow-io": 55, "weather-company": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "tomorrow-io", "key": "schema", "name": "Schema \u0026 documentation", "tomorrow-io": 75, "weather-company": 67, "weight": 13 }, { "by": 19, "edge": "tomorrow-io", "key": "ergonomics", "name": "Agent ergonomics", "tomorrow-io": 73, "weather-company": 54, "weight": 13 }, { "by": 14, "edge": "weather-company", "key": "security", "name": "Security \u0026 auth", "tomorrow-io": 34, "weather-company": 48, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "tomorrow-io": 20, "weather-company": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "weather-company", "key": "maintenance", "name": "Maintenance \u0026 community", "tomorrow-io": 27, "weather-company": 36, "weight": 7 }, { "by": 14, "edge": "tomorrow-io", "key": "transparency", "name": "Transparency \u0026 trust", "tomorrow-io": 63, "weather-company": 49, "weight": 7 } ], "summary": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust. Both do weather current.", "verdicts": { "tomorrow-io": "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 only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data.", "weather-company": "A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, 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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company", "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.md", "slim": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.min.md" }, "markdown": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust. Both do weather current.\n\n- Tomorrow.io Weather API: grade D, 51.4/100, rank #578 of 722. Markdown https://www.anchorterminal.com/tools/tomorrow-io.md · JSON https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json\n- The Weather Company Data APIs: grade D, 52.6/100, rank #565 of 722. Markdown https://www.anchorterminal.com/tools/weather-company.md · JSON https://www.anchorterminal.com/api/v1/tools/weather-company.json\n\n## Which one, for what\n\n### Tomorrow.io Weather API (D)\n\nGood for: Teams that need minute-level and route or polygon forecasts, alert webhooks and a hosted MCP server, and will buy through sales.\n\nAhead on:\n- Schema \u0026 documentation, 75 against 67\n- Agent ergonomics, 73 against 54\n- Transparency \u0026 trust, 63 against 49\n\nWatch for: No public price for paid use. The plan table lists Free and Enterprise, the second by quote\n\n### The Weather Company Data APIs (D)\n\nGood 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.\n\nAhead on:\n- Reliability, 73 against 55\n- Security \u0026 auth, 48 against 34\n- Maintenance \u0026 community, 36 against 27\n\nWatch 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.\n\n\n## Score by category\n\n| Category | Weight | Tomorrow.io Weather API | The Weather Company Data APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 73 | The Weather Company Data APIs +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 67 | Tomorrow.io Weather API +8 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 54 | Tomorrow.io Weather API +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 34 | 48 | The Weather Company Data APIs +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 27 | 36 | The Weather Company Data APIs +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 49 | Tomorrow.io Weather API +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **51.4 · D** | **52.6 · D** | |\n\n## Facts side by side\n\n| Fact | Tomorrow.io Weather API | The Weather Company Data APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | The Tomorrow Companies Inc. | The Weather Company, LLC |\n| Hosted endpoint | `https://api.tomorrow.io/v4` | `https://api.weather.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Tomorrow.io's subscription terms | Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published |\n| Tools exposed | 11 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-07-14 | 2026-09-14 |\n| Terms last updated | couldn't be read | no document linked |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | |\n| Terms restrict automated access | couldn't be read | |\n| Terms restrict benchmarking | couldn't be read | |\n| Terms or service can change without notice | couldn't be read | |\n| Arbitration or class-action waiver | couldn't be read | |\n\n## Verdicts\n\n**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 only, free keys are barred from commercial use, the docs give no numeric rate limits, and the status page lists 50 incidents in 85 days, mostly stale or degraded data.\n\n**The Weather Company Data APIs.** A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, 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.\n\n## Before you call either\n\n### Tomorrow.io Weather API\n\n1. Send the key in the `apikey` header, not the query string, so it stays out of URLs and logs\n2. Request only the `fields` and `timesteps` needed on POST /timelines. Free plans cover 24 hours back and 5 days ahead at `1h` and `1d`\n3. Split archive requests. POST /historical takes at most 31 days per call and deducts tokens, 1 for a point and 10 for a polygon\n4. Treat 401 with code 401001 as a missing or bad key. The docs say 403, the live API answered 401 on 8 October 2026\n5. On 429 back off without a hint. `Retry-After` is documented only for 503\n6. Check the plan's terms before storing or reselling responses. Free accounts are limited to non-commercial use with a Powered by Tomorrow.io link\n\n### The Weather Company Data APIs\n\n1. Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.\n2. Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.\n3. 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.\n4. Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.\n5. Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call.\n\n## Questions\n\n### Which is better for AI agents, Tomorrow.io Weather API or The Weather Company Data APIs?\n\nThe Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust.\n\n### Do Tomorrow.io Weather API and The Weather Company Data APIs need an API key?\n\nTomorrow.io Weather API takes an API key or an OAuth sign-in. The Weather Company Data APIs needs an API key.\n\n### Can an agent call Tomorrow.io Weather API and The Weather Company Data APIs without installing anything?\n\nYes. Tomorrow.io Weather API has a hosted endpoint at https://api.tomorrow.io/v4 and The Weather Company Data APIs at https://api.weather.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tomorrow-io\", \"b\": \"weather-company\"}`. From a terminal: `anchor compare tomorrow-io weather-company`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tomorrow-io.json and https://www.anchorterminal.com/api/v1/tools/weather-company.json\n\n## Other comparisons with Tomorrow.io Weather API or The Weather Company Data APIs\n\n- [AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.md)\n- [AccuWeather Core Weather API + MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.md)\n- [Google Weather API (Maps Platform) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-tomorrow-io.md)\n- [Google Weather API (Maps Platform) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company.md)\n- [Met Office Weather DataHub (Site Specific) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-tomorrow-io.md)\n- [Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company.md)\n- [meteoblue Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)\n- [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md)\n- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.md)\n- [NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/nws-api-vs-weather-company.md)\n- [OpenWeather One Call API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-tomorrow-io.md)\n- [OpenWeather One Call API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.md)\n- [Pirate Weather vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/pirate-weather-vs-tomorrow-io.md)\n- [Pirate Weather vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company.md)\n- [Tomorrow.io Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.md)\n- [Tomorrow.io Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.md)\n- [Tomorrow.io Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherbit.md)\n- [Tomorrow.io Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-xweather.md)\n- [Visual Crossing Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.md)\n- [The Weather Company Data APIs vs WeatherAPI.com](https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.md)\n- [The Weather Company Data APIs vs Weatherbit API](https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.md)\n- [The Weather Company Data APIs vs Xweather Weather API](https://www.anchorterminal.com/compare/weather-company-vs-xweather.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Tomorrow.io Weather API vs The Weather Company Data APIs", "url": "" } ], "description": "The Weather Company Data APIs scores 52.6 (D) on agent readiness against Tomorrow.io Weather API's 51.4 (D), and leads in 3 of 7 scored categories. Tomorrow.io Weather API leads on schema \u0026 documentation, agent ergonomics and transparency \u0026 trust. Both do weather current.…", "facts": [ "Tomorrow.io Weather API D 51.4", "The Weather Company Data APIs D 52.6", "scores" ], "h1": "Tomorrow.io Weather API vs The Weather Company Data APIs", "image": "https://www.anchorterminal.com/assets/og/compare-tomorrow-io-vs-weather-company.png", "path": "/compare/tomorrow-io-vs-weather-company", "published": "2026-10-01", "section": "tools", "title": "Tomorrow.io Weather API vs The Weather Company Data APIs for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company" }, "tokens": { "markdown": 2800, "slim": 730 }, "version": 1 }