Open-Meteo
Open-Meteo is an open-source weather API that provides free global weather forecasts, historical reanalysis data, marine conditions, air quality indexes, and long-range climate projections through a simple REST interface requiring no API key for non-commercial use. The service aggregates data from over 30 weather models provided by 15+ national meteorological services including ECMWF, NOAA GFS, DWD ICON, Météo-France, and JMA, delivering resolutions from 1 km to 11 km updated every 1 to 6 hours. Historical data extends back to 1940 via ERA5 reanalysis, giving developers and researchers access to consistent long-term climate records alongside real-time forecasts. Commercial users who need dedicated server capacity, higher throughput, and access to extended APIs such as ensemble forecasts, seasonal outlooks, satellite radiation, and climate change projections can subscribe to paid plans priced at a flat monthly rate with no per-call overage charges. The entire server infrastructure is open-source under the AGPLv3 license and can be self-hosted, while the underlying weather data is released under CC BY 4.0.
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 Open-Meteo the way a machine reads it — 24 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 — Open-Meteo scores 51.6/100 (developing), with a separate agent-readiness read of 39/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Open-Meteo
Each block below is one kind of artifact we hold for Open-Meteo. 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.
Geocoding API
Converts place names and city searches into geographic coordinates and returns metadata such as country, timezone, population, and elevation to facilitate location lookup within...
Open-Meteo Air Quality APIs API
The Air Quality APIs API from Open-Meteo — 1 operation(s) for air quality apis.
Open-Meteo Climate Change APIs API
The Climate Change APIs API from Open-Meteo — 1 operation(s) for climate change apis.
Open-Meteo Elevation API API
The Elevation API API from Open-Meteo — 1 operation(s) for elevation api.
Open-Meteo Ensemble Forecast APIs API
The Ensemble Forecast APIs API from Open-Meteo — 1 operation(s) for ensemble forecast apis.
Open-Meteo Flood APIs API
The Flood APIs API from Open-Meteo — 1 operation(s) for flood apis.
Open-Meteo Historical Weather APIs API
The Historical Weather APIs API from Open-Meteo — 1 operation(s) for historical weather apis.
Open-Meteo Marine Weather APIs API
The Marine Weather APIs API from Open-Meteo — 1 operation(s) for marine weather apis.
Open-Meteo Seasonal Forecast APIs API
The Seasonal Forecast APIs API from Open-Meteo — 1 operation(s) for seasonal forecast apis.
Open-Meteo Weather Forecast APIs API
The Weather Forecast APIs API from Open-Meteo — 1 operation(s) for weather forecast apis.
Scroll within the panel for all 10 ·
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.
Open Meteo 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.
Open Meteo 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.
Open Meteo Context
JSON-LDSpectral Rules 1
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.
Open-Meteo API Rules
SPECTRALJSON Schema 3
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.
Open-Meteo Air Quality Response
JSON SCHEMAOpen-Meteo Error Response
JSON SCHEMAOpen-Meteo Weather Response
JSON SCHEMAExamples 4
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.
Open Meteo Elevation Example
EXAMPLEOpen Meteo Geocoding Example
EXAMPLESecurity Posture 1
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 Open-Meteo — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
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/open-meteo · machine-readable index on apis.io