Tomorrow.io
Tomorrow.io is a Boston-based weather intelligence platform combining a global proprietary numerical weather model, a constellation of microsatellite weather radars, and a developer-facing v4 REST API. The platform exposes 60+ hyperlocal data layers — core weather, air quality, pollen, solar, soil, fire, flood, lightning, maritime, aviation, road — together with map tiles, severe-weather event detection, routable forecast queries, climate normals, historical archive access, customer-defined locations, named insights, and threshold-based webhook alerts. Used by airlines, on-demand logistics platforms, agriculture, energy, and the US Air Force, Tomorrow.io's API is designed for ETA-aware route planning, geofenced alerting, agentic workflows, and large-scale operational decisioning under weather risk.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Tomorrow.io the way a machine reads it — 95 machine-readable artifacts across 10 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 74.7/100 (exemplar), with a separate agent-readiness read of 56/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
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 10
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 Historical Weather API
Retrieve historical weather observations and monthly climate normals for any point or polygon on Earth using the same field catalog as the realtime and forecast APIs.
Tomorrow.io Events API
Retrieve severe weather events, fires, floods, lightning swarms, and custom vector events affecting a point or geometry.
Tomorrow.io Weather on Routes API
Retrieve weather along an arbitrary polyline of waypoints at the times each segment is expected to be traversed — powers route optimization, logistics planning, and ETA-aware ha...
Tomorrow.io Locations API
Manage saved locations (points, polygons, lines) referenced by ``locationId`` across the Tomorrow.io APIs, with tag-based cohorts for fleet, customer, or asset organization.
Tomorrow.io Alerts API
Create and manage threshold-based weather alerts that evaluate Tomorrow.io data layers against custom rules for linked locations and deliver notifications via webhook, email, an...
Tomorrow.io Insights API
Define and manage reusable Insights — named rules combining Tomorrow.io data layers, operators, and thresholds — that power the Events and Alerts APIs.
Tomorrow.io Forecast API
1h / 1d step weather forecast for the next 14 days.
Tomorrow.io Maps API
Web Mercator tile service for weather layers.
Tomorrow.io Realtime API
Current weather conditions for a point or location.
Tomorrow.io Timelines API
Flexible timeline retrieval across any combination of fields and timesteps.
Scroll within the panel for all 10 ·
Postman Collections 8
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.
Tomorrow.io Alerts API
POSTMANTomorrow.io Events API
POSTMANTomorrow.io Insights API
POSTMANTomorrow.io Locations API
POSTMANTomorrow.io Weather Maps API
POSTMANTomorrow.io Weather API
POSTMANScroll within the panel for all 8 ·
Open Collections 8
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).
Tomorrow.io Alerts API
OPEN COLLECTIONTomorrow.io Events API
OPEN COLLECTIONTomorrow.io Historical Weather API
OPEN COLLECTIONTomorrow.io Insights API
OPEN COLLECTIONTomorrow.io Locations API
OPEN COLLECTIONTomorrow.io Weather Maps API
OPEN COLLECTIONTomorrow.io Weather on Routes API
OPEN COLLECTIONTomorrow.io Weather API
OPEN COLLECTIONScroll within the panel for all 8 ·
Arazzo Workflows 12
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Tomorrow.io Alert Threshold Tuning
Inspect an existing alert, retune its threshold, and confirm the updated definition.
ARAZZOTomorrow.io Decommission a Monitored Location
Confirm a location exists, unlink it from an alert, then delete the saved location.
ARAZZOTomorrow.io Historical and Climate Normals Analysis
Save a location, pull its historical weather timeline, and compare against climate normals.
ARAZZOTomorrow.io Insight-Driven Alert Setup
Define a reusable insight, build an alert from it, bind locations, and activate monitoring.
ARAZZOTomorrow.io Insight-Scoped Event Query
Define an insight, then run an advanced event query filtered to that insight over an area.
ARAZZOTomorrow.io Location Severe Weather Events
Save a location, scan it for severe weather events, and branch on whether any are active.
ARAZZOTomorrow.io Map Tile Precipitation Overlay
Read realtime precipitation for a point, then fetch the matching weather map tile.
ARAZZOTomorrow.io Realtime Snapshot then Timelines Deep Dive
Take a realtime reading, then pull a multi-field timeline window over the same location.
ARAZZOTomorrow.io Realtime vs Climate Normals Benchmark
Compare current conditions for a location against its long-term monthly climate normals.
ARAZZOTomorrow.io Route Weather Hazard Scan
Retrieve weather along a planned route, then scan the destination for severe events.
ARAZZOTomorrow.io Saved Location Realtime and Forecast
Create a reusable saved location, then pull realtime conditions and a multi-day forecast for it.
ARAZZOTomorrow.io Tag and Monitor a Location Cohort
Create a location, tag it into a cohort, confirm the tag, and read its current conditions.
ARAZZOScroll within the panel for all 12 ·
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 six things the Kin Score reads for commercial clarity.
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 Io 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 Io Finops
FINOPSFeatures 12
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
60+ Hyperlocal Data Layers
Core weather, air quality, pollen, solar, soil, fire, flood, lightning, maritime, aviation, and road layers retrievable at point, polygon, or polyline geometry.
Proprietary Microsatellite Weather Radar Constellation
Tomorrow.io operates its own constellation of space-based weather radars to fill gaps in terrestrial radar coverage, especially over oceans and the developing world.
Minutely Forecast Resolution
60-minute minute-by-minute precipitation forecast in addition to hourly and daily timelines (Enterprise tier).
14-Day Forecast Horizon
Daily forecast out to 14 days on Enterprise plans, 5 days on Free.
Climate Normals
Monthly long-term averages for benchmarking current conditions against typical patterns.
Severe Weather and Custom Events
First-class API for severe weather phenomena plus customer-defined vector events for proprietary hazard models.
Threshold Alerts with Webhooks
Define rule-based alerts that fire webhooks and emails when conditions cross thresholds for linked locations.
Weather Map Tiles
Web Mercator PNG tiles for visualizing every data layer in Mapbox, MapLibre, Leaflet, OpenLayers, Google Maps.
Weather on Routes
ETA-aware weather retrieval along a polyline of waypoints for logistics, aviation, and maritime planning.
MCP Server
Official Tomorrow.io Model Context Protocol server for agentic AI access to the Weather API.
99.9% Uptime SLA
Enterprise SLA with rate-limit response headers exposed for programmatic monitoring.
LLMs.txt Indexed Documentation
Tomorrow.io publishes an LLMs.txt index of every documentation page and endpoint for AI agents.
Scroll within the panel for all 12 ·
Semantic 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 Io 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 5
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.
Tomorrow.io Alert
JSON SCHEMATomorrow.io Event
JSON SCHEMATomorrow.io Insight
JSON SCHEMATomorrow.io Location
JSON SCHEMATomorrow.io Weather Values
JSON SCHEMAJSON Structure 1
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.
Tomorrow Io Weather Values Structure
JSON STRUCTUREExamples 5
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.
Tomorrow Io Alert Example
EXAMPLETomorrow Io Events Example
EXAMPLETomorrow Io Realtime Example
EXAMPLETomorrow Io Route Example
EXAMPLESecurity 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.
Use Cases 10
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Route Optimization and Logistics
ETA-aware weather along truck, drone, and last-mile routes to avoid storms, ice, and visibility hazards.
Aviation Planning
Airline operations centers and dispatch use Tomorrow.io for icing, turbulence, low-level wind shear, and aerodrome forecasts.
Energy Forecasting
Wind and solar generation forecasting, load forecasting under heat events, and outage management.
Agriculture
Soil moisture, evapotranspiration, frost, and growing-degree-day analytics for farm operations.
Severe Weather Alerting
Geofenced alerting for tropical storms, severe thunderstorms, hail, lightning, and flash floods.
Sports and Outdoor Events
Game-day, race-day, and venue operations under lightning, heat, and precipitation risk.
Insurance and Climate Risk
Historical and climate-normals data for parametric insurance pricing and physical climate risk modeling.
Data Science
Bulk historical timelines for training operational decision models and backtesting weather-sensitive workflows.
Maritime Operations
Wave height, swell direction, and sea-state forecasting for shipping, offshore energy, and fisheries.
On-Demand Platforms
Surge demand modeling and worker-safety alerting for rideshare, delivery, and on-demand services.
Scroll within the panel for all 10 ·
Integrations 9
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Mapbox
Drop Tomorrow.io map tiles directly into Mapbox GL JS basemaps; official tomorrow-route-mapbox sample.
MapLibre
Open-source slippy-map client compatible with the Tomorrow.io Maps API.
Leaflet
Compatible with the Tomorrow.io Maps XYZ tile service.
Google Cloud Functions
Official tomorrow-api-proxy sample demonstrates key-safe proxy deployment on GCP.
Netlify Edge
Official tomorrow-netlify sample for serverless edge proxying.
Postman
Official Tomorrow.io Postman collection covering every v4 endpoint.
Model Context Protocol (MCP)
Official Tomorrow.io MCP server for plugging Weather, Forecast, Timelines, and Events into AI agents.
Webhooks
First-class webhook delivery for alert notifications.
Insights Dashboard
tomorrow-events-charts open-source dashboard demonstrating the Events API.
Scroll within the panel for all 9 ·
Solutions 6
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Weather API for Developers
Self-serve developer API with 60+ data layers, Postman collection, and MCP server.
Tomorrow.io Resilience Platform
Operational dashboards, alerts, and decision automation built on top of the Tomorrow.io Weather API.
Aviation Resilience
Vertical solution for airline operations centers, dispatch, and aerodrome operations.
Energy Resilience
Vertical solution for utility load forecasting, generation forecasting, and outage management.
Logistics Resilience
Vertical solution for fleet, freight, and last-mile delivery routing under weather risk.
Government and Defense
Tomorrow.io serves the US Air Force and other defense and government customers with operational weather intelligence and proprietary space-based weather radar.
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 5
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 12
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 12 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tomorrow-io · machine-readable index on apis.io