canonical: https://jentic.com/apis/api.met.no/met-no

# Met No MET Norway Locationforecast API

Jentic publishes the only available OpenAPI specification for MET Norway Locationforecast API, keeping it validated and agent-ready. The MET Norway Locationforecast service provides free worldwide weather forecasts published by the Norwegian Meteorological Institute. The API exposes 5 endpoints: compact and complete JSON forecasts, a legacy XML forecast, plus service status and health endpoints. It is well suited for any product that needs accurate point-location forecasts without the cost of a commercial weather provider, provided requests respect MET Norway's identifying User-Agent terms of service.

## For AI agents

Fetch free worldwide weather forecasts from the Norwegian Meteorological Institute: compact and complete JSON forecasts plus legacy XML for any latitude and longitude.

## Scope

Does not handle historical weather, weather alerts, or radar imagery - use for point-location weather forecasts only.

## Capabilities

- Retrieve a compact JSON weather forecast for any latitude and longitude with the next several days of hourly data
- Retrieve a complete JSON weather forecast with the full set of meteorological parameters
- Retrieve the legacy XML weather forecast for systems that still consume the original format
- Check the operational status of the MET Norway weather service before making bulk requests
- Hit a health endpoint suitable for uptime checks and cron-driven monitoring

## Use cases

### Free Worldwide Weather Forecasts

Embed accurate weather forecasts in a consumer or B2B product without the cost of commercial weather APIs. The /compact endpoint returns hourly forecasts for any latitude and longitude, suitable for travel apps, outdoor activity planners, and dashboards. Setup is under an hour - the only requirement is a descriptive User-Agent header identifying your application.

Example prompt: Call /compact with lat=59.91 and lon=10.75, parse the timeseries array, and surface the next 24 hourly entries with temperature and precipitation.

### Outdoor Activity Planner

Drive recommendations for hiking, sailing, and cycling by combining the /complete forecast (which includes wind speed, cloud cover, and precipitation type) with user-supplied activity thresholds. The MET Norway dataset has strong coverage in Northern Europe and globally. Most teams build the recommendation logic in 2 to 3 days.

Example prompt: Call /complete with the user's chosen latitude and longitude, then return the first time window in the next 48 hours where wind_speed < 8 m/s and precipitation_amount = 0.

### Operational Reliability Monitoring

Use /status and /healthz to detect MET Norway service outages before they affect your downstream consumers. Pair these with your alerting stack so that a degraded forecast service triggers a page rather than silently returning stale data. Effort is minimal - a single uptime check task per environment.

Example prompt: Call /healthz every minute and emit a PagerDuty alert if three consecutive responses return non-200.

### AI Travel Assistant

An AI travel assistant can call MET Norway through Jentic to answer 'what is the weather like in Bergen tomorrow' without any API key management. Jentic stores the required User-Agent identifier as a credential and surfaces the compact and complete forecast operations by intent. Setup is under an hour.

Example prompt: Use Jentic to search for 'get weather forecast for coordinates', execute /compact with the destination's latitude and longitude, and summarise the forecast as a friendly natural-language response.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/compact` | Compact JSON weather forecast |
| GET | `/complete` | Complete JSON weather forecast |
| GET | `/classic` | Legacy XML weather forecast |
| GET | `/status` | Service status |
| GET | `/healthz` | Health check endpoint |

## Key resources

- **Forecast** — Compact, complete, and legacy XML weather forecasts for any latitude and longitude
- **Status** — Service status and health endpoints for monitoring availability

## Why Jentic

- **Setup:** Wiring the MET Norway Locationforecast API by hand means setting an identifying User-Agent header on every request and coding your own reads of the compact, complete, and classic forecast endpoints. Through Jentic you install once, import the MET Norway Locationforecast API from the API Directory, store the identifying header once, and your agent calls it.
- **Permission scoping:** MET Norway passes coordinates as request parameters rather than ids in the URL path, and every operation here is read-only, so limit the agent to the read operations it needs, such as compact or complete. Every operation you grant is your explicit choice.
- **Credential handling:** Your MET Norway identifying header value 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.
- **Discovery method:** Agents search Jentic by intent such as 'get the weather forecast for a location' or 'check the forecast service status', and Jentic returns the matching MET Norway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **OpenWeatherMap API** — Commercial weather forecast API with paid tiers and high request quotas
- **Open-Meteo API** — Free open-source weather forecast API based on multiple national models
- **WeatherAPI** — Commercial weather forecasts plus historical and astronomy data

## FAQ

### Why is there no official OpenAPI spec for MET Norway Locationforecast API?

MET Norway does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MET Norway Locationforecast API 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 MET Norway Locationforecast API use?

MET Norway does not require an API key. Instead it requires a descriptive User-Agent header identifying your application and contact email - this is enforced as the userAgent apiKey scheme in the spec. Through Jentic, the User-Agent is configured once and applied automatically on each call.

### Can I retrieve a complete weather forecast with the MET Norway Locationforecast API?

Yes. GET /complete returns the full set of forecast parameters including wind speed and direction, cloud area fraction, precipitation amount and type, and pressure. Use /compact instead when you only need the most common temperature, wind, and precipitation fields.

### What are the rate limits for the MET Norway Locationforecast API?

MET Norway publishes a fair-use policy rather than a fixed rate limit. Requests must include a descriptive User-Agent and clients must respect the cache headers (typically a few minutes). Sustained high-volume usage requires contacting MET Norway directly.

### How do I get a forecast for specific coordinates with the MET Norway Locationforecast API through Jentic?

Run pip install jentic, then search for 'get weather forecast for coordinates'. Jentic returns the /compact operation schema. Execute it with lat and lon parameters and parse the returned timeseries array for the desired forecast horizon.

### Is the MET Norway Locationforecast API free to use?

Yes. The service is provided free by the Norwegian Meteorological Institute under the terms of service that require a descriptive User-Agent and adherence to cache headers. Commercial use is permitted within the fair-use policy.

### Can I limit what my agent is allowed to do with the MET Norway Locationforecast API?

Yes. Because you run Jentic One yourself, your own rules decide which MET Norway operations and credentials the agent can use, and every operation you grant is your explicit choice. All of this API's operations are read-only, so you can restrict the agent to just the reads it needs, such as GET /compact or GET /complete, and withhold the others like /classic, /status, and /healthz. Coordinates are passed as request parameters rather than ids in the URL path, so scoping is a matter of choosing which read operations the agent may call.