canonical: https://jentic.com/apis/oceandrivers.com/odweather

# Oceandrivers ODWeather API

The ODWeather API serves coastal and marine weather data from OceanDrivers. It returns real-time readings from weather stations, including AEMET stations, EasyWind units, the SOCIB bay buoy, and weather-display software, and forecast time series for a latitude and longitude. It also lists forecast points for a yacht club, returns the stations tied to an event, and provides live webcam feeds. Sailing, regatta, and coastal applications use it to show current conditions and forecasts for known points. It is a read-only, public API.

## For AI agents

Read coastal and marine weather from OceanDrivers: real-time station data, forecast time series for a latitude and longitude, event stations, yacht-club forecast points, and webcams. Read-only and requires no authentication.

## Scope

Does not provide global weather coverage, tide or wave forecasts, or historical archives. Use for reading OceanDrivers coastal station data, point forecasts, event stations, and webcams only.

## Capabilities

- Read real-time data from AEMET, EasyWind, SOCIB buoy, and weather-display stations
- Get forecast time series for a latitude and longitude
- Compare forecast and real-time information for a known point
- List the forecast points and stations tied to a yacht club or event
- Retrieve live webcam feeds for coastal locations

## Use cases

### Show conditions for a regatta

A sailing or regatta app reads the stations tied to an event and the real-time data from each, then shows current wind and weather to competitors and organisers. It can compare forecast against live readings for a known point so crews plan around the conditions. Through Jentic an agent discovers the station operations by intent and calls them with the event or station name.

Example prompt: Get the stations tied to a given event and return the real-time data for each

### Forecast a point along a route

A routing or planning agent requests the forecast time series for a latitude and longitude to see how wind and weather change over the coming hours at a point on a course. It can pull several points along a route to build a picture of the conditions ahead. This supports passage planning without a separate forecast provider.

Example prompt: Get the forecast time series for a given latitude and longitude and return the coming hours of wind data

### Embed live coastal webcams

A coastal or tourism app lists the available webcam feeds and embeds them alongside current conditions for a location. Pairing a webcam with the nearest station's real-time data gives users both a visual and the numbers. The agent reads the webcam list and the station data and presents them together.

Example prompt: Retrieve the available webcam feeds and return them alongside the real-time data for a named station

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1.0/getForecastTimeSeries/{latitude}/{longitude}/` | Get forecast time series for a latitude and longitude |
| GET | `/v1.0/compareStation/{stationName}/` | Compare forecast and real-time information for a known point |
| GET | `/v1.0/getAemetStation/{stationName}/{period}/` | Get data from an AEMET weather station |
| GET | `/v1.0/getForecastPoints/{yatchclubid}/language/{language}` | Get the forecast points for a yacht club |
| GET | `/v1.0/getEventStations/{eventId}/` | Get the stations tied to an event |
| GET | `/v1.0/getWebCams/` | Get the available webcam feeds |

## Key resources

- **Weather stations** — Read real-time data from AEMET, EasyWind, SOCIB buoy, and weather-display stations
- **Forecasts** — Get forecast time series for a latitude and longitude and forecast points for a yacht club
- **Webcams** — Retrieve live webcam feeds for coastal locations

## Why Jentic

- **Setup:** Wiring the ODWeather API by hand is light because it needs no key, but you still write the HTTP client, build the station, forecast, and webcam paths with their coordinates and names, and parse each response yourself. Through Jentic you install once, import the ODWeather API from the API Directory, and your agent calls it with no credential to provision.
- **Permission scoping:** The ODWeather API is read-only and exposes only station, forecast, and webcam reads, so a rule can allow your agent those reads and nothing more. There are no write or delete operations, and the API carries no credential that could reach beyond reading public weather data.
- **Credential handling:** The ODWeather API is public and uses no credential, so there is nothing for Jentic to store or inject. The calls your agent makes carry no secret into its prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a marine forecast' or 'read a weather station', and Jentic returns the matching ODWeather operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **OpenWeatherMap API** — Global weather and forecast coverage versus ODWeather's focus on coastal stations and marine points.
- **WeatherAPI** — General-purpose weather and forecast data by location versus ODWeather's station-level marine data.
- **Storm Glass Marine Weather API** — Marine forecasts such as waves and tides that complement ODWeather's station and webcam data.

## FAQ

### What authentication does the ODWeather API use?

The ODWeather API requires no authentication. Its OpenAPI spec declares no security scheme, so the station, forecast, and webcam endpoints are public and need no key or token. Because there is no credential, there is nothing to store, rotate, or expose when an agent calls it through Jentic.

### What weather data does the ODWeather API return?

It returns real-time readings from AEMET stations, EasyWind units, the SOCIB bay buoy, and weather-display software, plus forecast time series for a latitude and longitude. It also lists forecast points for a yacht club, the stations tied to an event, and live webcam feeds for coastal locations.

### Can I get a forecast for a specific location with the ODWeather API?

Yes. Request the forecast time series for a latitude and longitude and the response returns how wind and weather change over the coming hours at that point. An agent can pull several points along a route to build a picture of the conditions ahead.

### What are the rate limits for the ODWeather API?

The OpenAPI spec does not declare rate limits for the ODWeather API. It is a public service, so apply conservative client-side throttling and caching and check the OceanDrivers documentation for current guidance.

### Can I limit what my agent is allowed to do with the ODWeather API?

Yes. The ODWeather API is read-only and exposes only station, forecast, and webcam reads, so an agent connected through Jentic can only read weather data and cannot change anything. You choose which of these operations it may call, and every call it makes is logged.

### Is there an ODWeather API MCP server?

You don't need an MCP server to give your agent the ODWeather API. Jentic connects it directly from the API Directory: import it and your agent calls the station, forecast, and webcam operations on demand, with no key to configure because the API is public.

### How do I read ODWeather forecasts through Jentic?

Search Jentic for an intent like 'get a marine forecast' or 'read a weather station', which returns the matching ODWeather operation with its input schema so the agent supplies the location or station name and reads the response, with no credential to configure because the API is public. To run it on your own infrastructure, install Jentic One from its GitHub repo.