Aemet Es AEMET OpenData

Name: AEMET OpenData API
Brand: AEMET OpenData
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey62 EndpointsREST

For Agents

Pull official Spanish weather observations, forecasts, climatology, fire risk, radar, and CAP warnings across 62 REST endpoints from the national met agency.

Install Jentic One Beta

Connect the AEMET OpenData to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AEMET OpenData, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AEMET OpenData API.

Retrieve current observations from AEMET's network of conventional weather stations

Pull municipal, provincial, regional, and national forecasts for today, tomorrow, and medium-range

Access maritime forecasts for coastal zones and high seas around the Iberian peninsula

GET STARTED

Start building with AEMET OpenData API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AEMET OpenData API for, with concrete tasks.

★ Spain-Specific Weather Application

Build a Spanish-language weather product using authoritative national-agency data instead of third-party aggregators. AEMET OpenData covers municipal forecasts via /api/prediccion/especifica/municipio/diaria/{municipio}, station-level observations via /api/observacion/convencional/datos/estacion/{idema}, and the master list of Spanish municipalities via /api/maestro/municipios. All responses are referenced to AEMET station identifiers and INE municipality codes.

Call GET /api/maestro/municipios to find the code for Sevilla, then call /api/prediccion/especifica/municipio/diaria/{municipio} to get the 7-day forecast

Emergency and Warning Monitoring

Subscribe to AEMET CAP warnings for civil-protection or operational alerting in Spain. The /api/avisos_cap/ultimoelaborado/area/{area} endpoint returns the most recent warning bundle for a meteorological area, while /api/avisos_cap/archivo/fechaini/{fechaIniStr}/fechafin/{fechaFinStr} returns historical warnings for incident review and audit trails. Pair with the radar and fire-risk endpoints for an operational picture during severe weather.

Call GET /api/avisos_cap/ultimoelaborado/area/61 to fetch the latest warnings for the Comunidad Valenciana area and parse the CAP XML for active alerts

Climatology and Research Datasets

Pull long-running climatological products for research, sustainability reporting, or insurance modelling. /api/productos/climatologicos/resumenclimatologico/nacional/{anio}/{mes} returns the national monthly summary, /api/productos/climatologicos/balancehidrico/{anio}/{decena} returns the water balance for a 10-day period, and the network endpoints expose ozone, radiation, and background-pollution series.

Call GET /api/productos/climatologicos/resumenclimatologico/nacional/2025/05 to retrieve the May 2025 national climatological summary

AI Agent Spanish Weather Tool

Equip an AI agent with authoritative Spanish weather data through Jentic. The agent searches by intent for the right AEMET endpoint - municipal forecast, station observation, or active warning - loads its schema, and executes with the api_key isolated in your Jentic One instance. Useful for travel, logistics, or safety assistants whose users ask in Spanish or about Spanish locations.

Search Jentic for 'spanish municipal weather forecast', load /api/prediccion/especifica/municipio/diaria/{municipio} schema, and execute with municipio=28079 for Madrid

Key Endpoints

62 endpoints — jentic publishes the only available openapi specification for aemet opendata, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/prediccion/especifica/municipio/diaria/{municipio}

Daily forecast for a Spanish municipality

GET

/api/observacion/convencional/datos/estacion/{idema}

Observations from a specific weather station

GET

/api/avisos_cap/ultimoelaborado/area/{area}

Latest CAP weather warnings for an area

GET

/api/prediccion/maritima/costera/costa/{costa}

Coastal maritime forecast

GET

/api/maestro/municipios

List all supported Spanish municipalities

GET

/api/productos/climatologicos/resumenclimatologico/nacional/{anio}/{mes}

National monthly climatological summary

GET

/api/red/radar/nacional

Latest national radar imagery

GET

/api/prediccion/especifica/municipio/diaria/{municipio}

Daily forecast for a Spanish municipality

GET

/api/observacion/convencional/datos/estacion/{idema}

Observations from a specific weather station

GET

/api/avisos_cap/ultimoelaborado/area/{area}

Latest CAP weather warnings for an area

GET

/api/prediccion/maritima/costera/costa/{costa}

Coastal maritime forecast

GET

/api/maestro/municipios

List all supported Spanish municipalities

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AEMET api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'Spanish municipal weather forecast', and Jentic returns the matching AEMET operation with its input schema, including the municipio path parameter, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using AEMET OpenData API through Jentic.

Why is there no official OpenAPI spec for AEMET OpenData?

AEMET does not publish a downloadable OpenAPI 3 specification - only an interactive Swagger UI. Jentic generates and maintains this spec so that AI agents and developers can call AEMET OpenData via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the AEMET OpenData API use?

AEMET uses an api_key passed in a header named api_key, obtained free of charge from https://opendata.aemet.es/centrodedescargas/altaUsuario after agreeing to the reuse conditions. Through Jentic the key is stored in the vault and injected at execution time.

Which Spanish locations does AEMET OpenData cover?

AEMET covers all Spanish municipalities (call GET /api/maestro/municipios for the master list using INE codes), every autonomous community and province for regional forecasts, the coastal areas and high seas around Iberia and the Canaries, and the conventional observation network for station-level data.

How do I get active weather warnings for a region in Spain?

Call GET /api/avisos_cap/ultimoelaborado/area/{area} with the AEMET area code; the response contains a CAP-formatted XML bundle of every active warning for that area. For historical review use /api/avisos_cap/archivo/fechaini/{fechaIniStr}/fechafin/{fechaFinStr} with date range parameters.

What are the rate limits for the AEMET OpenData API?

AEMET applies a per-key throttle but does not document a fixed quota in the spec; HTTP 429 responses are returned when the limit is exceeded. Jentic surfaces the 429 response so agents can back off and retry.

How do I retrieve a municipal forecast through Jentic?

Run pip install jentic, search Jentic with 'spanish municipal weather forecast', load the /api/prediccion/especifica/municipio/diaria/{municipio} schema, and execute with the 5-digit INE municipality code. Jentic returns the parsed forecast without exposing your api_key.

Can I limit what my agent is allowed to do with the AEMET OpenData API?

Yes. Because you run Jentic One yourself, your own rules decide which AEMET operations the agent may call, and every AEMET OpenData operation is a read, so you can pin the agent to just the forecast and observation reads it needs, such as the daily municipal forecast at /api/prediccion/especifica/municipio/diaria/{municipio} or station data at /api/observacion/convencional/datos/estacion/{idema}. Location codes like the municipio or estacion sit in the URL path, so your rules can scope access down to specific paths. Any operation you leave out of the allowed set, such as the CAP warnings or radar endpoints, stays unreachable to the agent. Your api_key is injected at execution time and never enters the agent's prompt or logs.