OpenWeatherMap (inofficial)

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

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey4 EndpointsREST

For Agents

Retrieve current weather conditions for any city, coordinate, or bounding box using a single API key, returning temperature, humidity, wind, and cloud data in one call.

Quickstart

Get started with OpenWeatherMap (inofficial) in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get current weather for a city"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

Search for cities matching a partial name and return matching weather records

GET STARTED

Start building with OpenWeatherMap (inofficial) API

Explore with Jentic

View OpenAPI Document

Use for: Get the current temperature in London right now, Find all weather stations within a bounding box around Berlin, Retrieve current conditions for New York, Paris, and Tokyo in one call, Check whether it is raining at a given latitude and longitude

Not supported: Does not handle multi-day forecasts, historical weather, severe weather alerts, or air quality — use for current weather lookups by city, coordinates, or bounding box only.

Jentic publishes the only available OpenAPI document for OpenWeatherMap (inofficial), keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for OpenWeatherMap (inofficial), keeping it validated and agent-ready. The OpenWeatherMap API exposes current weather data for cities and geographic regions worldwide through a small set of read-only HTTP endpoints. Agents can fetch conditions for a single location, look up several cities by ID, search by city name, or pull a batch of cities inside a bounding box. Authentication is a single APPID query parameter, which keeps integration trivial once a free or paid account key is provisioned.

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 vault 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 though Jentic?

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

Credential isolation

The OpenWeatherMap APPID query-parameter key is stored encrypted in the Jentic vault. Agents receive a scoped execution context — the raw key is injected at request time and never appears in the agent's prompt or response.

Intent-based discovery

Agents search Jentic with intents like '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 OpenWeatherMap docs.

Time to first call

Direct integration: 1-2 hours to read the docs, register a key, and write a client. Through Jentic: under 10 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

WeatherAPI

Drop-in replacement covering current weather, forecast, and history in one API

Choose WeatherAPI when the agent needs forecast or historical data alongside current conditions in a single provider.

Alternative

Weatherbit

Weather data provider with current, forecast, and severe weather alerts

Choose Weatherbit when the agent needs severe weather alerts or air quality data not exposed by OpenWeatherMap's current weather endpoints.

Alternative

AccuWeather Core Weather API

Commercial weather API with branded forecast products

Choose AccuWeather when commercial licensing or hyper-local forecasts are required for production agents.

Complementary

Visual Crossing Weather

Historical and forecast weather often paired with current-conditions providers

Use alongside OpenWeatherMap when the agent needs long-range historical weather records to back analytical queries.

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

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.