Met No MET Norway Locationforecast API

Name: MET Norway Locationforecast API
Brand: MET Norway Locationforecast API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey5 EndpointsREST

For Agents

Install Jentic One Beta

Connect the MET Norway Locationforecast API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MET Norway Locationforecast API, 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 MET Norway Locationforecast API.

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

GET STARTED

Start building with MET Norway Locationforecast API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use MET Norway Locationforecast API for, with concrete tasks.

★ 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.

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.

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.

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.

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

5 endpoints — jentic publishes the only available openapi specification for met norway locationforecast api, keeping it validated and agent-ready.

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

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

Why Jentic?

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

Credential isolation

The MET Norway User-Agent is configured once in the Jentic MAXsystem vault and applied automatically on every call. Agents do not see or rotate the identifying string themselves.

Intent-based discovery

Agents search by intent — 'get the weather forecast for coordinates' — and Jentic returns the /compact and /complete operations with input schemas, removing the need to read MET Norway's documentation site.

Time to first call

Direct integration with MET Norway: under an hour for a basic forecast pull. Through Jentic: minutes from sign-up to first forecast — the User-Agent and cache headers are handled by the runtime.

FAQs

Specific to using MET Norway Locationforecast API through Jentic.

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 at https://app.jentic.com/sign-up.

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.