Open-Meteo Weather Forecast (Public Test)
Forecast queries with multi-location, multi-model, 15-minute, date-window and export options.
- Selected price
- $0.01 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
open-meteo-freeCurrent Open-Meteo Global Weather Forecast · GET · View API reference | $0.01 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
currentobjectintervalintegertemperature_2mnumbertimestringweather_codeinteger
current_unitsobjectintervalstringtemperature_2mstringtimestringweather_codestring
dailyobjecttemperature_2m_maxnumber[]temperature_2m_minnumber[]timestring[]
daily_unitsobjecttemperature_2m_maxstringtemperature_2m_minstringtimestring
elevationintegergenerationtime_msnumberhourlyobjectrelative_humidity_2minteger[]temperature_2mnumber[]timestring[]
hourly_unitsobjectrelative_humidity_2mstringtemperature_2mstringtimestring
latitudenumberlongitudenumbertimezonestringtimezone_abbreviationstringutc_offset_secondsinteger
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
current?: {
interval?: number;
temperature_2m?: number;
time?: string;
weather_code?: number;
};
current_units?: {
interval?: string;
temperature_2m?: string;
time?: string;
weather_code?: string;
};
daily?: {
temperature_2m_max?: Array<number>;
temperature_2m_min?: Array<number>;
time?: Array<string>;
};
daily_units?: {
temperature_2m_max?: string;
temperature_2m_min?: string;
time?: string;
};
elevation?: number;
generationtime_ms?: number;
hourly?: {
relative_humidity_2m?: Array<number>;
temperature_2m?: Array<number>;
time?: Array<string>;
};
hourly_units?: {
relative_humidity_2m?: string;
temperature_2m?: string;
time?: string;
};
latitude?: number;
longitude?: number;
timezone?: string;
timezone_abbreviation?: string;
utc_offset_seconds?: number;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast?current=temperature_2m%2Cweather_code&daily=temperature_2m_max%2Ctemperature_2m_min&forecast_days=1&hourly=temperature_2m%2Crelative_humidity_2m&latitude=31.23&longitude=121.47&timezone=Asia%2FShanghai' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
latitude | URL query parametersquery | string | number | No | WGS84 latitude: one number or comma-separated values, e.g. 31.23,39.90; each value must be -90 to 90. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo. |
longitude | URL query parametersquery | string | number | No | WGS84 longitude: one number or comma-separated values, e.g. 121.47,116.40; each value must be -180 to 180. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo. |
bounding_box | URL query parametersquery | string | No | Optional area query in south,west,north,east order, e.g. 31.20,121.40,31.30,121.50. Use instead of latitude/longitude. South<north, west<east; coordinate ranges apply. Choose an explicit model supporting grid queries; best_match and some grids may reject bounding boxes. One fixed timezone only; auto is unsupported. Subject to upstream location/grid-cell limits. minLength: 1 |
current | URL query parametersquery | string | No | Comma-separated current variable identifiers, e.g. temperature_2m,relative_humidity_2m,weather_code. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. minLength: 1 |
hourly | URL query parametersquery | string | No | Comma-separated hourly variable identifiers, e.g. temperature_2m,relative_humidity_2m,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. minLength: 1 |
daily | URL query parametersquery | string | No | Comma-separated daily variable identifiers, e.g. temperature_2m_max,temperature_2m_min,sunrise,sunset. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Supply timezone when daily is selected. minLength: 1 |
minutely_15 | URL query parametersquery | string | No | Comma-separated minutely_15 variable identifiers, e.g. temperature_2m,precipitation,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Native 15-minute coverage is regional; other regions may use hourly interpolation. minLength: 1 |
current_weather | URL query parametersquery | boolean | No | Legacy convenience flag: true returns the predefined current-weather group and current_weather response section. Prefer current for explicit variable selection; when both are supplied true takes precedence. |
timezone | URL query parametersquery | string | No | IANA timezone, auto, or a comma-separated list for multiple locations. Default GMT. One timezone applies to all locations, otherwise count must match coordinates. Required with daily. Bounding-box queries allow one fixed timezone and do not allow auto. minLength: 1 |
forecast_days | URL query parametersquery | integer | No | Forecast calendar days, default 7; up to 16. Native model coverage may be shorter. Omit when using explicit start/end windows; a nonzero value conflicts with those windows. minimum: 0 · maximum: 16 |
past_days | URL query parametersquery | integer | No | Recent past calendar days, default 0; 0–92 for this Forecast API. Omit or set 0 with explicit windows. Earlier data use a separate historical endpoint. minimum: 0 · maximum: 92 |
forecast_hours | URL query parametersquery | integer | No | Number of future hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows. minimum: 0 |
past_hours | URL query parametersquery | integer | No | Number of past hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows. minimum: 0 |
forecast_minutely_15 | URL query parametersquery | integer | No | Number of future 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows. minimum: 0 |
past_minutely_15 | URL query parametersquery | integer | No | Number of past 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows. minimum: 0 |
initial_hours | URL query parametersquery | integer | No | Optional start hour within the current local day when using forecast_hours, e.g. initial_hours=0 with forecast_hours=12 selects the first 12 hours. Upstream validates the initial-step value. |
initial_minutely_15 | URL query parametersquery | integer | No | Optional starting 15-minute step within the current local day when using forecast_minutely_15, e.g. 0 starts at midnight. Upstream validates the initial-step value. |
start_date | URL query parametersquery | string | No | Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with end_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
end_date | URL query parametersquery | string | No | Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with start_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
start_hour | URL query parametersquery | string | No | Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
end_hour | URL query parametersquery | string | No | Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
start_minutely_15 | URL query parametersquery | string | No | 15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
end_minutely_15 | URL query parametersquery | string | No | 15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream. minLength: 1 |
models | URL query parametersquery | string | No | One model identifier or a comma-separated list, e.g. best_match or gfs_seamless,ecmwf_ifs025. Omit for automatic selection. All currently supported Forecast model identifiers are forwarded; no best_match-only restriction. Multiple models add model suffixes to returned variable keys and consume more upstream calls. Deprecated or regional models may be unavailable. minLength: 1 |
temporal_resolution | URL query parametersquery | string | No | Output timestep for hourly variables: native preserves model resolution; minutely_15/minutely_30 may interpolate; hourly/hourly_1, hourly_3 and hourly_6 select fixed steps. enum: "native", "minutely_15", "minutely_30", "hourly", "hourly_1", "hourly_3", "hourly_6" |
temperature_unit | URL query parametersquery | string | No | Temperature unit. enum: "celsius", "fahrenheit" |
wind_speed_unit | URL query parametersquery | string | No | Wind-speed unit; use this current spelling. enum: "kmh", "ms", "mph", "kn" |
windspeed_unit | URL query parametersquery | string | No | Legacy alias for wind_speed_unit. Avoid supplying both: this legacy spelling takes precedence upstream. enum: "kmh", "ms", "mph", "kn" |
precipitation_unit | URL query parametersquery | string | No | Precipitation unit; explicit value takes precedence over length_unit fallback. enum: "mm", "inch" |
length_unit | URL query parametersquery | string | No | Compatibility unit selection. imperial provides an inch precipitation fallback when precipitation_unit is omitted; do not assume every length-valued variable is converted. enum: "metric", "imperial" |
timeformat | URL query parametersquery | string | No | ISO 8601 local timestamps or Unix seconds. For daylight-saving-aware times, request unixtime and convert using the returned timezone. enum: "iso8601", "unixtime" |
cell_selection | URL query parametersquery | string | No | Weather grid-cell preference. enum: "land", "sea", "nearest" |
elevation | URL query parametersquery | string | number | No | Elevation in metres, comma-separated elevations for multiple locations, or the literal string nan to disable statistical elevation downscaling. With a list, supply one entry per location. Omit to use the digital elevation model. |
tilt | URL query parametersquery | string | number | No | Solar-panel tilt: numeric 0–90 degrees, or literal string nan for a horizontal tracker. Used by global_tilted_irradiance variables. Range and special value are checked upstream. |
azimuth | URL query parametersquery | string | number | No | Solar-panel azimuth: numeric -180–180 degrees (0 south, -90 east, 90 west), or literal string nan for a vertical tracker. Both tilt and azimuth set to nan select a biaxial tracker. Checked upstream. |
location_id | URL query parametersquery | string | No | Optional comma-separated integer location IDs for multi-location response identification. If supplied, count must match coordinates; one ID can be a single integer string. minLength: 1 |
format | URL query parametersquery | string | No | Response format. Default json. csv is text; xlsx and flatbuffers are binary and must be handled as bytes by the client. JSON response schema and the retained complete example apply to json only. Subject to 8 MiB response size. enum: "json", "csv", "xlsx", "flatbuffers" |
location_information | URL query parametersquery | string | No | Location metadata layout for CSV/XLSX export: section includes a metadata section; omit excludes it. This does not change JSON forecast variable selection. enum: "section", "omit" |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"current": {
"interval": 900,
"temperature_2m": 8.9,
"time": "2026-11-18T21:30",
"weather_code": 0
},
"current_units": {
"interval": "seconds",
"temperature_2m": "°C",
"time": "iso8601",
"weather_code": "wmo code"
},
"daily": {
"temperature_2m_max": [
14.9
],
"temperature_2m_min": [
7.5
],
"time": [
"2026-11-18"
]
},
"daily_units": {
"temperature_2m_max": "°C",
"temperature_2m_min": "°C",
"time": "iso8601"
},
"elevation": 3,
"generationtime_ms": 0.3647804260253906,
"hourly": {
"relative_humidity_2m": [
85,
85,
89,
91,
92,
94,
93,
92,
85,
76,
67,
61,
58,
57,
64,
63,
64,
68,
67,
63,
61,
59,
58,
58
],
"temperature_2m": [
13.3,
13.2,
13.1,
12.5,
12.4,
12.1,
11.6,
11.4,
12.1,
13.1,
14,
14.6,
14.9,
14.8,
13.5,
13.2,
12.8,
11.6,
11.2,
10.8,
10,
9.3,
8.5,
7.9
],
"time": [
"2026-11-18T00:00",
"2026-11-18T01:00",
"2026-11-18T02:00",
"2026-11-18T03:00",
"2026-11-18T04:00",
"2026-11-18T05:00",
"2026-11-18T06:00",
"2026-11-18T07:00",
"2026-11-18T08:00",
"2026-11-18T09:00",
"2026-11-18T10:00",
"2026-11-18T11:00",
"2026-11-18T12:00",
"2026-11-18T13:00",
"2026-11-18T14:00",
"2026-11-18T15:00",
"2026-11-18T16:00",
"2026-11-18T17:00",
"2026-11-18T18:00",
"2026-11-18T19:00",
"2026-11-18T20:00",
"2026-11-18T21:00",
"2026-11-18T22:00",
"2026-11-18T23:00"
]
},
"hourly_units": {
"relative_humidity_2m": "%",
"temperature_2m": "°C",
"time": "iso8601"
},
"latitude": 31.247803,
"longitude": 121.5,
"timezone": "Asia/Shanghai",
"timezone_abbreviation": "GMT+8",
"utc_offset_seconds": 28800
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Open-Meteo Weather Forecast (Public Test)
Forecast queries with multi-location, multi-model, 15-minute, date-window and export options.
## Available implementations
open-meteo-free · Open-Meteo Global Weather Forecast: https://openany.si/markets/apis/capabilities/open-meteo-weather-forecast-public-test?offering=0cb43e0a-3af5-492d-ab72-824e2840cdc0 · $0.01 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/open-meteo-weather-forecast-public-test
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast
Price: $0.01 / call
Provider: open-meteo-free
Contract revision: 2
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast?current=temperature_2m%2Cweather_code&daily=temperature_2m_max%2Ctemperature_2m_min&forecast_days=1&hourly=temperature_2m%2Crelative_humidity_2m&latitude=31.23&longitude=121.47&timezone=Asia%2FShanghai' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "Open-Meteo Global Weather Forecast",
"endpoint": "https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"accepted_types": [
"string",
"number"
],
"description": "WGS84 latitude: one number or comma-separated values, e.g. 31.23,39.90; each value must be -90 to 90. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.",
"location": "query",
"name": "latitude",
"nullable": false,
"required": false,
"type": "string"
},
{
"accepted_types": [
"string",
"number"
],
"description": "WGS84 longitude: one number or comma-separated values, e.g. 121.47,116.40; each value must be -180 to 180. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.",
"location": "query",
"name": "longitude",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Optional area query in south,west,north,east order, e.g. 31.20,121.40,31.30,121.50. Use instead of latitude/longitude. South<north, west<east; coordinate ranges apply. Choose an explicit model supporting grid queries; best_match and some grids may reject bounding boxes. One fixed timezone only; auto is unsupported. Subject to upstream location/grid-cell limits.",
"location": "query",
"min_length": 1,
"name": "bounding_box",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated current variable identifiers, e.g. temperature_2m,relative_humidity_2m,weather_code. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.",
"location": "query",
"min_length": 1,
"name": "current",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated hourly variable identifiers, e.g. temperature_2m,relative_humidity_2m,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.",
"location": "query",
"min_length": 1,
"name": "hourly",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated daily variable identifiers, e.g. temperature_2m_max,temperature_2m_min,sunrise,sunset. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Supply timezone when daily is selected.",
"location": "query",
"min_length": 1,
"name": "daily",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated minutely_15 variable identifiers, e.g. temperature_2m,precipitation,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Native 15-minute coverage is regional; other regions may use hourly interpolation.",
"location": "query",
"min_length": 1,
"name": "minutely_15",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Legacy convenience flag: true returns the predefined current-weather group and current_weather response section. Prefer current for explicit variable selection; when both are supplied true takes precedence.",
"location": "query",
"name": "current_weather",
"nullable": false,
"required": false,
"type": "boolean"
},
{
"description": "IANA timezone, auto, or a comma-separated list for multiple locations. Default GMT. One timezone applies to all locations, otherwise count must match coordinates. Required with daily. Bounding-box queries allow one fixed timezone and do not allow auto.",
"location": "query",
"min_length": 1,
"name": "timezone",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Forecast calendar days, default 7; up to 16. Native model coverage may be shorter. Omit when using explicit start/end windows; a nonzero value conflicts with those windows.",
"location": "query",
"maximum": "16",
"minimum": "0",
"name": "forecast_days",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Recent past calendar days, default 0; 0–92 for this Forecast API. Omit or set 0 with explicit windows. Earlier data use a separate historical endpoint.",
"location": "query",
"maximum": "92",
"minimum": "0",
"name": "past_days",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Number of future hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.",
"location": "query",
"minimum": "0",
"name": "forecast_hours",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Number of past hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.",
"location": "query",
"minimum": "0",
"name": "past_hours",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Number of future 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.",
"location": "query",
"minimum": "0",
"name": "forecast_minutely_15",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Number of past 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.",
"location": "query",
"minimum": "0",
"name": "past_minutely_15",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Optional start hour within the current local day when using forecast_hours, e.g. initial_hours=0 with forecast_hours=12 selects the first 12 hours. Upstream validates the initial-step value.",
"location": "query",
"name": "initial_hours",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Optional starting 15-minute step within the current local day when using forecast_minutely_15, e.g. 0 starts at midnight. Upstream validates the initial-step value.",
"location": "query",
"name": "initial_minutely_15",
"nullable": false,
"required": false,
"type": "integer"
},
{
"description": "Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with end_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "start_date",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with start_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "end_date",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "start_hour",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "end_hour",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "start_minutely_15",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.",
"location": "query",
"min_length": 1,
"name": "end_minutely_15",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "One model identifier or a comma-separated list, e.g. best_match or gfs_seamless,ecmwf_ifs025. Omit for automatic selection. All currently supported Forecast model identifiers are forwarded; no best_match-only restriction. Multiple models add model suffixes to returned variable keys and consume more upstream calls. Deprecated or regional models may be unavailable.",
"location": "query",
"min_length": 1,
"name": "models",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Output timestep for hourly variables: native preserves model resolution; minutely_15/minutely_30 may interpolate; hourly/hourly_1, hourly_3 and hourly_6 select fixed steps.",
"enum_values": [
"native",
"minutely_15",
"minutely_30",
"hourly",
"hourly_1",
"hourly_3",
"hourly_6"
],
"location": "query",
"name": "temporal_resolution",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Temperature unit.",
"enum_values": [
"celsius",
"fahrenheit"
],
"location": "query",
"name": "temperature_unit",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Wind-speed unit; use this current spelling.",
"enum_values": [
"kmh",
"ms",
"mph",
"kn"
],
"location": "query",
"name": "wind_speed_unit",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Legacy alias for wind_speed_unit. Avoid supplying both: this legacy spelling takes precedence upstream.",
"enum_values": [
"kmh",
"ms",
"mph",
"kn"
],
"location": "query",
"name": "windspeed_unit",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Precipitation unit; explicit value takes precedence over length_unit fallback.",
"enum_values": [
"mm",
"inch"
],
"location": "query",
"name": "precipitation_unit",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Compatibility unit selection. imperial provides an inch precipitation fallback when precipitation_unit is omitted; do not assume every length-valued variable is converted.",
"enum_values": [
"metric",
"imperial"
],
"location": "query",
"name": "length_unit",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "ISO 8601 local timestamps or Unix seconds. For daylight-saving-aware times, request unixtime and convert using the returned timezone.",
"enum_values": [
"iso8601",
"unixtime"
],
"location": "query",
"name": "timeformat",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Weather grid-cell preference.",
"enum_values": [
"land",
"sea",
"nearest"
],
"location": "query",
"name": "cell_selection",
"nullable": false,
"required": false,
"type": "string"
},
{
"accepted_types": [
"string",
"number"
],
"description": "Elevation in metres, comma-separated elevations for multiple locations, or the literal string nan to disable statistical elevation downscaling. With a list, supply one entry per location. Omit to use the digital elevation model.",
"location": "query",
"name": "elevation",
"nullable": false,
"required": false,
"type": "string"
},
{
"accepted_types": [
"string",
"number"
],
"description": "Solar-panel tilt: numeric 0–90 degrees, or literal string nan for a horizontal tracker. Used by global_tilted_irradiance variables. Range and special value are checked upstream.",
"location": "query",
"name": "tilt",
"nullable": false,
"required": false,
"type": "string"
},
{
"accepted_types": [
"string",
"number"
],
"description": "Solar-panel azimuth: numeric -180–180 degrees (0 south, -90 east, 90 west), or literal string nan for a vertical tracker. Both tilt and azimuth set to nan select a biaxial tracker. Checked upstream.",
"location": "query",
"name": "azimuth",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Optional comma-separated integer location IDs for multi-location response identification. If supplied, count must match coordinates; one ID can be a single integer string.",
"location": "query",
"min_length": 1,
"name": "location_id",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Response format. Default json. csv is text; xlsx and flatbuffers are binary and must be handled as bytes by the client. JSON response schema and the retained complete example apply to json only. Subject to 8 MiB response size.",
"enum_values": [
"json",
"csv",
"xlsx",
"flatbuffers"
],
"location": "query",
"name": "format",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Location metadata layout for CSV/XLSX export: section includes a metadata section; omit excludes it. This does not change JSON forecast variable selection.",
"enum_values": [
"section",
"omit"
],
"location": "query",
"name": "location_information",
"nullable": false,
"required": false,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "10000",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example · Shanghai — complete public evaluation respons",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"current": "temperature_2m,weather_code",
"daily": "temperature_2m_max,temperature_2m_min",
"forecast_days": "1",
"hourly": "temperature_2m,relative_humidity_2m",
"latitude": "31.23",
"longitude": "121.47",
"timezone": "Asia/Shanghai"
}
},
"response_body": {
"current": {
"interval": 900,
"temperature_2m": 8.9,
"time": "2026-11-18T21:30",
"weather_code": 0
},
"current_units": {
"interval": "seconds",
"temperature_2m": "°C",
"time": "iso8601",
"weather_code": "wmo code"
},
"daily": {
"temperature_2m_max": [
14.9
],
"temperature_2m_min": [
7.5
],
"time": [
"2026-11-18"
]
},
"daily_units": {
"temperature_2m_max": "°C",
"temperature_2m_min": "°C",
"time": "iso8601"
},
"elevation": 3,
"generationtime_ms": 0.3647804260253906,
"hourly": {
"relative_humidity_2m": [
85,
85,
89,
91,
92,
94,
93,
92,
85,
76,
67,
61,
58,
57,
64,
63,
64,
68,
67,
63,
61,
59,
58,
58
],
"temperature_2m": [
13.3,
13.2,
13.1,
12.5,
12.4,
12.1,
11.6,
11.4,
12.1,
13.1,
14,
14.6,
14.9,
14.8,
13.5,
13.2,
12.8,
11.6,
11.2,
10.8,
10,
9.3,
8.5,
7.9
],
"time": [
"2026-11-18T00:00",
"2026-11-18T01:00",
"2026-11-18T02:00",
"2026-11-18T03:00",
"2026-11-18T04:00",
"2026-11-18T05:00",
"2026-11-18T06:00",
"2026-11-18T07:00",
"2026-11-18T08:00",
"2026-11-18T09:00",
"2026-11-18T10:00",
"2026-11-18T11:00",
"2026-11-18T12:00",
"2026-11-18T13:00",
"2026-11-18T14:00",
"2026-11-18T15:00",
"2026-11-18T16:00",
"2026-11-18T17:00",
"2026-11-18T18:00",
"2026-11-18T19:00",
"2026-11-18T20:00",
"2026-11-18T21:00",
"2026-11-18T22:00",
"2026-11-18T23:00"
]
},
"hourly_units": {
"relative_humidity_2m": "%",
"temperature_2m": "°C",
"time": "iso8601"
},
"latitude": 31.247803,
"longitude": 121.5,
"timezone": "Asia/Shanghai",
"timezone_abbreviation": "GMT+8",
"utc_offset_seconds": 28800
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Shanghai — complete public evaluation respons
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 38
Review these request fields before running. Keep the published provider and request method unchanged.
latitude- WGS84 latitude: one number or comma-separated values, e.g. 31.23,39.90; each value must be -90 to 90. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.
longitude- WGS84 longitude: one number or comma-separated values, e.g. 121.47,116.40; each value must be -180 to 180. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.
bounding_box- Optional area query in south,west,north,east order, e.g. 31.20,121.40,31.30,121.50. Use instead of latitude/longitude. South<north, west<east; coordinate ranges apply. Choose an explicit model supporting grid queries; best_match and some grids may reject bounding boxes. One fixed timezone only; auto is unsupported. Subject to upstream location/grid-cell limits.
current- Comma-separated current variable identifiers, e.g. temperature_2m,relative_humidity_2m,weather_code. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.
hourly- Comma-separated hourly variable identifiers, e.g. temperature_2m,relative_humidity_2m,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.
daily- Comma-separated daily variable identifiers, e.g. temperature_2m_max,temperature_2m_min,sunrise,sunset. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Supply timezone when daily is selected.
minutely_15- Comma-separated minutely_15 variable identifiers, e.g. temperature_2m,precipitation,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Native 15-minute coverage is regional; other regions may use hourly interpolation.
current_weather- Legacy convenience flag: true returns the predefined current-weather group and current_weather response section. Prefer current for explicit variable selection; when both are supplied true takes precedence.
timezone- IANA timezone, auto, or a comma-separated list for multiple locations. Default GMT. One timezone applies to all locations, otherwise count must match coordinates. Required with daily. Bounding-box queries allow one fixed timezone and do not allow auto.
forecast_days- Forecast calendar days, default 7; up to 16. Native model coverage may be shorter. Omit when using explicit start/end windows; a nonzero value conflicts with those windows.
past_days- Recent past calendar days, default 0; 0–92 for this Forecast API. Omit or set 0 with explicit windows. Earlier data use a separate historical endpoint.
forecast_hours- Number of future hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
past_hours- Number of past hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
forecast_minutely_15- Number of future 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
past_minutely_15- Number of past 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
initial_hours- Optional start hour within the current local day when using forecast_hours, e.g. initial_hours=0 with forecast_hours=12 selects the first 12 hours. Upstream validates the initial-step value.
initial_minutely_15- Optional starting 15-minute step within the current local day when using forecast_minutely_15, e.g. 0 starts at midnight. Upstream validates the initial-step value.
start_date- Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with end_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
end_date- Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with start_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
start_hour- Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
end_hour- Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
start_minutely_15- 15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
end_minutely_15- 15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
models- One model identifier or a comma-separated list, e.g. best_match or gfs_seamless,ecmwf_ifs025. Omit for automatic selection. All currently supported Forecast model identifiers are forwarded; no best_match-only restriction. Multiple models add model suffixes to returned variable keys and consume more upstream calls. Deprecated or regional models may be unavailable.
temporal_resolution- Output timestep for hourly variables: native preserves model resolution; minutely_15/minutely_30 may interpolate; hourly/hourly_1, hourly_3 and hourly_6 select fixed steps.
temperature_unit- Temperature unit.
wind_speed_unit- Wind-speed unit; use this current spelling.
windspeed_unit- Legacy alias for wind_speed_unit. Avoid supplying both: this legacy spelling takes precedence upstream.
precipitation_unit- Precipitation unit; explicit value takes precedence over length_unit fallback.
length_unit- Compatibility unit selection. imperial provides an inch precipitation fallback when precipitation_unit is omitted; do not assume every length-valued variable is converted.
timeformat- ISO 8601 local timestamps or Unix seconds. For daylight-saving-aware times, request unixtime and convert using the returned timezone.
cell_selection- Weather grid-cell preference.
elevation- Elevation in metres, comma-separated elevations for multiple locations, or the literal string nan to disable statistical elevation downscaling. With a list, supply one entry per location. Omit to use the digital elevation model.
tilt- Solar-panel tilt: numeric 0–90 degrees, or literal string nan for a horizontal tracker. Used by global_tilted_irradiance variables. Range and special value are checked upstream.
azimuth- Solar-panel azimuth: numeric -180–180 degrees (0 south, -90 east, 90 west), or literal string nan for a vertical tracker. Both tilt and azimuth set to nan select a biaxial tracker. Checked upstream.
location_id- Optional comma-separated integer location IDs for multi-location response identification. If supplied, count must match coordinates; one ID can be a single integer string.
format- Response format. Default json. csv is text; xlsx and flatbuffers are binary and must be handled as bytes by the client. JSON response schema and the retained complete example apply to json only. Subject to 8 MiB response size.
location_information- Location metadata layout for CSV/XLSX export: section includes a metadata section; omit excludes it. This does not change JSON forecast variable selection.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/open-meteo-free/v1/forecast?current=temperature_2m%2Cweather_code&daily=temperature_2m_max%2Ctemperature_2m_min&forecast_days=1&hourly=temperature_2m%2Crelative_humidity_2m&latitude=31.23&longitude=121.47&timezone=Asia%2FShanghai' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "current": { "interval": 900, "temperature_2m": 8.9, "time": "2026-11-18T21:30", "weather_code": 0 }, "current_units": { "interval": "seconds", "temperature_2m": "°C", "time": "iso8601", "weather_code": "wmo code" }, "daily": { "temperature_2m_max": [ 14.9 ], "temperature_2m_min": [ 7.5 ], "time": [ "2026-11-18" ] }, "daily_units": { "temperature_2m_max": "°C", "temperature_2m_min": "°C", "time": "iso8601" }, "elevation": 3, "generationtime_ms": 0.3647804260253906, "hourly": { "relative_humidity_2m": [ 85, 85, 89, 91, 92, 94, 93, 92, 85, 76, 67, 61, 58, 57, 64, 63, 64, 68, 67, 63, 61, 59, 58, 58 ], "temperature_2m": [ 13.3, 13.2, 13.1, 12.5, 12.4, 12.1, 11.6, 11.4, 12.1, 13.1, 14, 14.6, 14.9, 14.8, 13.5, 13.2, 12.8, 11.6, 11.2, 10.8, 10, 9.3, 8.5, 7.9 ], "time": [ "2026-11-18T00:00", "2026-11-18T01:00", "2026-11-18T02:00", "2026-11-18T03:00", "2026-11-18T04:00", "2026-11-18T05:00", "2026-11-18T06:00", "2026-11-18T07:00", "2026-11-18T08:00", "2026-11-18T09:00", "2026-11-18T10:00", "2026-11-18T11:00", "2026-11-18T12:00", "2026-11-18T13:00", "2026-11-18T14:00", "2026-11-18T15:00", "2026-11-18T16:00", "2026-11-18T17:00", "2026-11-18T18:00", "2026-11-18T19:00", "2026-11-18T20:00", "2026-11-18T21:00", "2026-11-18T22:00", "2026-11-18T23:00" ] }, "hourly_units": { "relative_humidity_2m": "%", "temperature_2m": "°C", "time": "iso8601" }, "latitude": 31.247803, "longitude": 121.5, "timezone": "Asia/Shanghai", "timezone_abbreviation": "GMT+8", "utc_offset_seconds": 28800 }
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use Open-Meteo Weather Forecast (Public Test) with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.