OpenWeatherMap (inofficial)

Name: OpenWeatherMap (inofficial) API
Brand: OpenWeatherMap (inofficial)
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey4 EndpointsREST

For Agents

Install Jentic One Beta

Connect the OpenWeatherMap (inofficial) to your agent

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

Fetch current weather conditions for a city by name, coordinates, or city ID

Pull weather snapshots for several cities at once using a bounding box query

Look up weather for a list of cities in one batch by passing comma-separated city IDs

GET STARTED

Start building with OpenWeatherMap (inofficial) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use OpenWeatherMap (inofficial) API for, with concrete tasks.

★ Travel and trip planning agents

Trip-planning agents can call the OpenWeatherMap current weather endpoint to fetch conditions at a destination before recommending pack lists, outdoor activities, or rescheduling itineraries. A single GET to /weather with city name or coordinates returns temperature, wind, and weather descriptions, which the agent can summarise in plain language. Free-tier API keys cover roughly 60 calls per minute, enough for low-volume conversational planning.

Call GET /weather?q=Reykjavik&units=metric&APPID={key} and summarise temperature, wind speed, and conditions for the user.

Multi-city dashboards

Operations and logistics dashboards often need a snapshot of weather across many sites at once. The /group endpoint accepts a comma-separated list of city IDs and returns a single response with the current conditions for each, avoiding the need for a separate request per location. This is well suited to agents that monitor warehouses, retail stores, or event venues.

Call GET /group?id=2643743,5128581,1850147&units=metric&APPID={key} and return a table of city, temperature, and weather description.

Geofenced weather alerts

Field-service agents and outdoor-event agents can use the /box/city endpoint to pull weather for every city inside a rectangular bounding box, then alert when temperature or wind crosses a threshold. The bounding box is defined by two corner coordinates plus a zoom level, which makes it easy to scope checks to a single region.

Call GET /box/city?bbox=12,32,15,37,10&APPID={key} and flag every returned city where wind speed exceeds 20 m/s.

AI agent integration via Jentic

Agents using Jentic discover the OpenWeatherMap operations through natural-language search and call them with structured input schemas. Because the spec only exposes four read-only endpoints, an agent typically loads the /weather operation once and reuses it across conversational turns. The Jentic One instance holds the APPID key so the agent never sees the raw secret.

Search Jentic for 'get current weather for a city', load the /weather operation schema, and execute it for q=Dublin.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for openweathermap (inofficial), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/weather

Get current weather data for one location

GET

/box/city

Get current weather for several cities within a rectangle

GET

/find

Search for cities by name and return weather

GET

/group

Get current weather for several cities by ID

GET

/weather

Get current weather data for one location

GET

/box/city

Get current weather for several cities within a rectangle

GET

/find

Search for cities by name and return weather

GET

/group

Get current weather for several cities by ID

Why Jentic?

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

Credential isolation

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

Intent-based discovery

Agents search Jentic by intent such as 'get current weather for a city', and Jentic returns the matching /weather operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using OpenWeatherMap (inofficial) API through Jentic.

Why is there no official OpenAPI spec for OpenWeatherMap (inofficial)?

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

The OpenWeatherMap API uses an API key passed as the APPID query parameter on every request. Through Jentic, the APPID is stored in the encrypted vault and injected at execution time, so the agent never receives the raw key in its prompt or context.

Can I get a multi-day forecast with this API?

No. The four endpoints in this spec all return current conditions only - /weather, /box/city, /find, and /group. Forecast and historical data are separate OpenWeatherMap products with different endpoints and are not part of this specification.

What are the rate limits for the OpenWeatherMap API?

OpenWeatherMap's free tier is documented at roughly 60 calls per minute and 1,000,000 calls per month, with higher limits on paid plans. The spec does not enforce limits, so agents should handle 429 responses with backoff.

How do I fetch weather for many cities at once through Jentic?

Search Jentic for 'get current weather for several cities', load the /group operation, and pass a comma-separated list of city IDs in the id parameter. A single call returns the conditions for every city.

Is the OpenWeatherMap API free?

Yes, OpenWeatherMap offers a free tier that covers the four current-weather endpoints in this spec. Higher request volumes and forecast products require a paid plan billed directly by OpenWeatherMap.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which OpenWeatherMap operations the agent may call and which credentials it may use. OpenWeatherMap passes the location as query parameters rather than a resource id in the path, so scoping is by operation: you can allow only current weather by city on /weather while withholding bounding-box lookups on /box/city, city search on /find, or batch lookups on /group. Every operation the agent can reach is one you chose to enable, and your APPID key is injected at execution time rather than exposed to the agent.