Tomorrow.io
Tomorrow.io is a weather and climate intelligence platform exposing a unified v4 HTTP API. The API combines real-time observations, hyperlocal forecast timelines (minutely / hourly / daily), 20+ years of historical data, climate normals, weather-on-routes, configurable insights and event detection, per-location alerts with webhook delivery, and raster map tiles. 60+ data layers cover core weather, air quality, pollen, fire, flood, soil, solar, aviation, maritime, and lightning.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tomorrow.io the way a machine reads it — 125 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Tomorrow.io scores 39.9/100 (developing), with a separate agent-readiness read of 25/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Tomorrow.io's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tomorrow/"
title="Tomorrow.io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tomorrow.svg"
alt="Tomorrow.io Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tomorrow/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tomorrow/"
title="Tomorrow.io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tomorrow/card.svg"
alt="Tomorrow.io Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Tomorrow.io
Each block below is one kind of artifact we hold for Tomorrow.io. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Tomorrow.io Alerts API
Persistent alerts linked to one or more locations with webhook delivery.
Tomorrow.io Climate API
30-year climate normals for a location.
Tomorrow.io Events API
Query events matching insights at a location or buffered geometry.
Tomorrow.io Forecast API
Hourly and daily forecast timelines via a simple GET interface.
Tomorrow.io Historical API
Historical weather data for a point or polygon, up to 20 years back.
Tomorrow.io Insights API
Define threshold rules over weather fields to detect business-significant events.
Tomorrow.io Locations API
CRUD over monitored point / polygon / polyline locations with tags.
Tomorrow.io Map Tiles API
Raster tile endpoint for weather field overlays.
Tomorrow.io Realtime API
Current-conditions snapshot for a single location.
Tomorrow.io Routes API
Weather along a polyline / list of waypoints with arrival-time interpolation.
Tomorrow.io Timelines API
Advanced multi-step (minutely / hourly / daily / current) forecast and historical timelines.
Scroll within the panel for all 11 ·
Postman Collections 11
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 11 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONTomorrow.io Weather Alerts API
OPEN COLLECTIONTomorrow.io Weather Alerts Climate API
OPEN COLLECTIONTomorrow.io Weather Alerts Events API
OPEN COLLECTIONTomorrow.io Weather Alerts Forecast API
OPEN COLLECTIONTomorrow.io Weather Alerts Historical API
OPEN COLLECTIONTomorrow.io Weather Alerts Insights API
OPEN COLLECTIONTomorrow.io Weather Alerts Locations API
OPEN COLLECTIONTomorrow.io Weather Alerts Map Tiles API
OPEN COLLECTIONTomorrow.io Weather Alerts Realtime API
OPEN COLLECTIONTomorrow.io Weather Alerts Routes API
OPEN COLLECTIONTomorrow.io Weather Alerts Timelines API
OPEN COLLECTIONTomorrow.io Weather API
OPEN COLLECTIONScroll within the panel for all 13 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Tomorrow Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tomorrow Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Tomorrow Weather Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Tomorrow.io API Rules
SPECTRALTomorrow.io API Rules
SPECTRALJSON Schema 27
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AlertCreateRequest
JSON SCHEMAAlertLocationLinkRequest
JSON SCHEMAAlert
JSON SCHEMAClimateNormalsRequest
JSON SCHEMAClimateNormalsResponse
JSON SCHEMAEvent
JSON SCHEMAEventsRequest
JSON SCHEMAEventsResponse
JSON SCHEMAForecastResponse
JSON SCHEMAGeoJSONGeometry
JSON SCHEMAHistoricalRequest
JSON SCHEMAInsightCondition
JSON SCHEMAInsightCreateRequest
JSON SCHEMAInsight
JSON SCHEMALocationCreateRequest
JSON SCHEMALocation
JSON SCHEMALocationTagsRequest
JSON SCHEMALocationUpdateRequest
JSON SCHEMARealtimeWeatherResponse
JSON SCHEMARouteRequest
JSON SCHEMARouteResponse
JSON SCHEMARouteWaypoint
JSON SCHEMATimelineInterval
JSON SCHEMATimeline
JSON SCHEMATimelinesRequest
JSON SCHEMATimelinesResponse
JSON SCHEMAWeatherValues
JSON SCHEMAScroll within the panel for all 27 ·
JSON Structure 27
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Alert Create Request Structure
JSON STRUCTUREAlert Location Link Request Structure
JSON STRUCTUREAlert Structure
JSON STRUCTUREClimate Normals Request Structure
JSON STRUCTUREClimate Normals Response Structure
JSON STRUCTUREEvent Structure
JSON STRUCTUREEvents Request Structure
JSON STRUCTUREEvents Response Structure
JSON STRUCTUREForecast Response Structure
JSON STRUCTUREGeo Jsongeometry Structure
JSON STRUCTUREHistorical Request Structure
JSON STRUCTUREInsight Condition Structure
JSON STRUCTUREInsight Create Request Structure
JSON STRUCTUREInsight Structure
JSON STRUCTURELocation Create Request Structure
JSON STRUCTURELocation Structure
JSON STRUCTURELocation Tags Request Structure
JSON STRUCTURELocation Update Request Structure
JSON STRUCTURERealtime Weather Response Structure
JSON STRUCTURERoute Request Structure
JSON STRUCTURERoute Response Structure
JSON STRUCTURERoute Waypoint Structure
JSON STRUCTURETimeline Interval Structure
JSON STRUCTURETimeline Structure
JSON STRUCTURETimelines Request Structure
JSON STRUCTURETimelines Response Structure
JSON STRUCTUREWeather Values Structure
JSON STRUCTUREScroll within the panel for all 27 ·
Examples 27
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Alert Create Request Example
EXAMPLEAlert Example
EXAMPLEEvent Example
EXAMPLEEvents Request Example
EXAMPLEEvents Response Example
EXAMPLEForecast Response Example
EXAMPLEGeo Jsongeometry Example
EXAMPLEHistorical Request Example
EXAMPLEInsight Condition Example
EXAMPLEInsight Example
EXAMPLELocation Example
EXAMPLERoute Request Example
EXAMPLERoute Response Example
EXAMPLERoute Waypoint Example
EXAMPLETimeline Example
EXAMPLETimeline Interval Example
EXAMPLETimelines Request Example
EXAMPLETimelines Response Example
EXAMPLEWeather Values Example
EXAMPLEScroll within the panel for all 27 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Tomorrow.io — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tomorrow · machine-readable index on apis.io
This is an independent, third-party profile of Tomorrow.io, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.