Reference · built on requestCommons signalWeather & climate

Open-Meteo

Hourly and daily forecasts to 16 days, current conditions, and reanalysis back to 1940 from Open-Meteo's combined national models.

Request accessPricing ↗

About

Open-Meteo is an open-source weather API that merges numerical models from national weather services, among them ECMWF, DWD, NOAA, Météo-France, JMA, the UK Met Office, and MeteoSwiss, and serves them from one JSON endpoint. The forecast API at api.open-meteo.com/v1/forecast takes latitude and longitude and returns hourly, daily, or current variables for up to 16 days ahead and 92 days back. The Historical Weather API at archive-api.open-meteo.com serves ERA5 reanalysis from 1940. Free use is non-commercial and needs no key; commercial use is a paid plan with a key for customer-api.open-meteo.com.

Through Fibric, an operator reads the variables it needs for each site and proposes an action on the numbers: a staffing change, a start time, or a hold.

This is a reference listing. It documents what Fibric would read from Open-Meteo and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Hourly variables such as temperature_2m, precipitation, snowfall, weather_code, wind_speed_10m, wind_gusts_10m, and cloud_cover
  • Daily variables such as temperature_2m_max, temperature_2m_min, precipitation_sum, sunrise, sunset, and wind_speed_10m_max
  • Current conditions: every hourly variable is also available as an instantaneous value
  • forecast_days from 0 to 16 and past_days from 0 to 92 on the same request
  • A models parameter that picks one or more named models, or auto, which combines the best suited ones
  • Reanalysis from ERA5 (0.25°, from 1940) and ERA5-Land (0.1°, from 1950) through the archive endpoint with start_date and end_date
  • JSON, CSV, XLSX, or FlatBuffers output, with timezone=auto resolving local time from the coordinates

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Forecast tomorrow's covers from the weather

    Daily precipitation_sum and temperature_2m_max for the venue's coordinate feed the cover forecast. The operator proposes tomorrow's prep and staffing numbers with the forecast row attached.

    With Cover Forecast

  • Set the morning start from the overnight low

    Hourly temperature_2m for the next 24 hours tells the operator how long the building needs to warm. It proposes the start time for your approval.

    With Optimal Start

  • Explain a yield dip with the cloud record

    past_days hourly cloud_cover for the site sits beside inverter output. The operator separates weather from faults and proposes which arrays need a visit.

    With Array Yield

  • Put weather into the demand outlook

    Sixteen days of daily maxima and precipitation join the sales history. The operator proposes an adjusted outlook and notes which days the weather moved.

    With Demand Outlook

Requirements

  • A paid Open-Meteo plan and API key if the deployment is commercial, since the free API is for non-commercial use
  • Attribution to Open-Meteo under CC BY 4.0, also on paid plans
  • WGS84 coordinates for each site you want forecasts for
  • A polling schedule that fits the model update cycle, from hourly for some regional models to every six hours for global ones
Authentication
No key or sign-up for non-commercial use; a paid plan issues an API key for the customer-api.open-meteo.com endpoint that a commercial deployment must use.

Limits

  • Free access is rate-limited to 600 calls a minute, 5,000 an hour, and 10,000 a day, with no uptime guarantee
  • ERA5 and ERA5-Land reanalysis arrive with a five-day delay; CERRA covers Europe only and is no longer updated
  • 1 km resolution applies only in regions with a high-resolution model; elsewhere grids are 9 to 11 km
  • The data carry no warranty; Open-Meteo assumes no responsibility for inaccuracies or omissions

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Open-Meteo ↗

Questions and answers

Does Open-Meteo need an API key?
Not for non-commercial use, which the terms define as private or non-profit sites without ads or subscriptions, home automation, public research, and education. Commercial products need a paid plan; the key it issues works on customer-api.open-meteo.com, a separate endpoint from the free one.
Which weather model answers my request?
By default models=auto, and Open-Meteo combines the best suited models for the coordinate. You can name one or more models instead. Regional models such as ICON-D2, HRRR, and AROME update every one to three hours; most global models update every six hours.
How far back can I read?
The forecast endpoint accepts past_days up to 92. For longer history the archive endpoint serves ERA5 from 1940 and ERA5-Land from 1950 by start_date and end_date, with a five-day delay behind real time.
Ask about Open-Meteo

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Open-Meteo (api.open-meteo.com). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy