OpenWeatherMap
OpenWeather (operating openweathermap.org) is a global weather data platform delivering current weather, multi-horizon forecasts, historical archives, climate statistics, air pollution, solar irradiance, road risk, geocoding, and weather map tiles. Data is sourced from satellites, weather models, radars, and a worldwide network of weather stations, served through REST APIs across a freemium, multi-tier, and pay-per-call commercial model.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles OpenWeatherMap the way a machine reads it — 107 machine-readable artifacts across 14 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 — OpenWeatherMap scores 73.5/100 (exemplar), with a separate agent-readiness read of 71/100 (agent native). 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 OpenWeatherMap
Each block below is one kind of artifact we hold for OpenWeatherMap. 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 14
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.
OpenWeatherMap Accumulated Parameters API
Accumulated temperature and precipitation totals for agriculture.
OpenWeatherMap Air Pollution API
Current, forecast, and historical air pollution data with AQI.
OpenWeatherMap Current Weather API
Current weather data for any geographic coordinates worldwide.
OpenWeatherMap Forecast API
Weather forecasts at multiple granularities and time horizons.
OpenWeatherMap Geocoding API
Direct and reverse geocoding between location names and coordinates.
OpenWeatherMap History API
Historical weather records by coordinate with hourly granularity.
OpenWeatherMap Measurements API
Submit and retrieve aggregated weather station measurements.
OpenWeatherMap One Call API
Unified timeline API with current, forecast, and historical weather plus alerts.
OpenWeatherMap Road Risk API
Route weather, road surface state, and alerts for a track of waypoints.
OpenWeatherMap Solar Irradiance API
Solar irradiance values for clear and cloudy sky models.
OpenWeatherMap Solar Panels API
Manage modeled locations and solar panel configurations and retrieve power output.
OpenWeatherMap Stations API
Register, retrieve, update, and delete personal weather stations.
OpenWeatherMap Statistical Weather API
Long-term statistical weather aggregates for any global location.
OpenWeatherMap Weather Maps API
Weather layer tile service for map overlays.
Scroll within the panel for all 14 ·
Postman Collections 12
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.
OpenWeatherMap Forecast APIs
POSTMANOpenWeatherMap Geocoding API
POSTMANOpenWeatherMap Road Risk API
POSTMANScroll within the panel for all 12 ·
Open Collections 12
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).
OpenWeatherMap Accumulated Parameters API
OPEN COLLECTIONOpenWeatherMap Air Pollution API
OPEN COLLECTIONOpenWeatherMap Current Weather Data API
OPEN COLLECTIONOpenWeatherMap Forecast APIs
OPEN COLLECTIONOpenWeatherMap Geocoding API
OPEN COLLECTIONOpenWeatherMap Historical Weather API
OPEN COLLECTIONOpenWeatherMap One Call API 4.0
OPEN COLLECTIONOpenWeatherMap Road Risk API
OPEN COLLECTIONOpenWeatherMap Solar Energy APIs
OPEN COLLECTIONOpenWeatherMap Statistical Weather API
OPEN COLLECTIONOpenWeatherMap Weather Maps 1.0 API
OPEN COLLECTIONOpenWeatherMap Weather Stations API
OPEN COLLECTIONScroll within the panel for all 12 ·
Arazzo Workflows 8
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.
OpenWeatherMap Air Quality By City
Geocode a city name, then fetch current air pollution and its hourly forecast.
ARAZZOOpenWeatherMap Coordinate Weather And Air Snapshot
From raw coordinates, gather current weather, One Call current conditions, and air pollution.
ARAZZOOpenWeatherMap Historical Air Pollution Window
Geocode a city, then fetch historical air pollution for a window and the current reading.
ARAZZOOpenWeatherMap Locate And Report Current Weather
Geocode a city name, then fetch current weather and a five day forecast for it.
ARAZZOOpenWeatherMap Multi Horizon Forecast
Geocode a city, then stack hourly, daily, and climatic forecasts for it.
ARAZZOOpenWeatherMap Reverse Geocode Weather
Turn coordinates into a place name, then fetch current weather and One Call conditions.
ARAZZOOpenWeatherMap Weather Map Overlay Context
Geocode a city, read its current weather, then fetch a matching weather map tile.
ARAZZOOpenWeatherMap Zip To Forecast
Resolve a zip or postal code to coordinates, then return five day and sixteen day forecasts.
ARAZZOScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server (candidate)
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
OpenWeatherMap GraphQL Schema
This is a conceptual GraphQL schema for the OpenWeatherMap API surface. OpenWeatherMap does not publish a native GraphQL endpoint; this schema is a structured representation of ...
GRAPHQLPricing 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.
Openweathermap 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.
Openweathermap Finops
FINOPSFeatures 10
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.
Global Weather Coverage
Real-time and forecast weather for any latitude/longitude on Earth.
Long-Range Historical Archive
Over 47 years of historical weather observations available via History, One Call 4.0, and Statistical APIs.
Air Quality Telemetry
AQI plus eight pollutant concentrations covering current, forecast, and historical air pollution.
Solar Energy Modeling
GHI, DNI, DHI irradiance and per-panel power output predictions for solar projects.
Map Tile Overlays
Direct integration with Leaflet, OpenLayers, and Google Maps via raster tile layers.
Pay-Per-Call One Call 4.0
First 1,000 daily One Call requests free; additional calls billed per call for flexible cost control.
Multi-Tier Subscriptions
Free, Startup, Developer, Professional, Expert, and Enterprise tiers tuned for varying volume and SLA.
Personal Weather Stations
Register stations, submit measurements, and retrieve aggregated readings.
Road and Route Risk
Per-waypoint weather and road surface state with severity-tagged alerts for routing.
Multi-Lingual Output
Forecast and condition text returned in 40 plus languages.
Scroll within the panel for all 10 ·
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.
Openweathermap 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.
OpenWeatherMap API Rules
SPECTRALOpenWeatherMap 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.
OpenWeatherMap Air Pollution
JSON SCHEMAOpenWeatherMap Current Weather
JSON SCHEMAOpenWeatherMap Forecast Item
JSON SCHEMAOpenWeatherMap Geocoding Result
JSON SCHEMAOpenWeatherMap Weather Station
JSON SCHEMAJSON Structure 3
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.
Openweathermap Air Pollution Structure
JSON STRUCTUREOpenweathermap Current Weather Structure
JSON STRUCTUREOpenweathermap Geocoding Structure
JSON STRUCTUREExamples 12
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.
Current Weather Example
EXAMPLEForecast Five Day Example
EXAMPLEGeocoding Direct Example
EXAMPLEHistory City Example
EXAMPLEOne Call Current Example
EXAMPLERoad Risk Example
EXAMPLEStatistical Month Example
EXAMPLEWeather Maps Tile Example
EXAMPLEScroll within the panel for all 12 ·
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.
Use Cases 8
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.
Consumer Weather Apps
Power mobile and web weather apps with current, forecast, and alert data.
Logistics and Routing
Use Road Risk and forecast data to optimize fleet routing and arrival times.
Energy and Utilities
Forecast solar generation and demand with solar irradiance and panel energy prediction APIs.
Agriculture
Use accumulated temperature and precipitation data to inform irrigation, planting, and harvest decisions.
Insurance and Risk
Combine historical and statistical weather with air quality and road risk to underwrite and adjudicate claims.
Smart City and Air Quality
Surface AQI and pollutant concentrations in civic dashboards and citizen notification systems.
Outdoor and Travel
Embed weather data in trip planning, ski resort, sailing, and outdoor recreation experiences.
Aviation and Maritime
Use high-frequency forecast and wind data for flight planning and marine operations.
Scroll within the panel for all 8 ·
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Leaflet
Weather Maps 1.0 tile layers render directly inside Leaflet maps.
OpenLayers
Tile layers compatible with OpenLayers raster sources.
Google Maps
Weather tiles can be added as overlays in Google Maps.
Home Assistant
OpenWeather integration is a first-class weather provider in the Home Assistant ecosystem.
Node-RED
Numerous community Node-RED nodes wrap the OpenWeather APIs.
Power BI and Tableau
REST connectors and community templates ingest OpenWeather data for analytics dashboards.
Model Context Protocol Servers
Multiple community MCP servers (NimbleBrainInc, robertn702, fgladisch, jezweb, SaintDoresh, tristau) expose OpenWeather data to MCP-compatible agents and Claude.
Claude Code Skills
ForecastSkill and OpenWeather API Automation skills add weather capabilities to Claude Code workflows.
Scroll within the panel for all 8 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
VANE Geospatial Platform
OpenWeather's geospatial platform for working with weather grids and time series.
Deker Storage Engine
OpenWeather's open-source multidimensional array storage engine used internally for weather time series.
Marketplace Bulk Data
Bulk history, forecast, solar, and tile downloads for analytics and ML pipelines.
Enterprise SLAs
Contractual SLAs with dedicated account management and data residency options.
Resources
Every other property we hold for OpenWeatherMap — 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 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 17
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 17 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/openweathermap · machine-readable index on apis.io