canonical: https://jentic.com/apis/openweathermap.org/openweathermap # OpenWeatherMap (inofficial) 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Return temperature, humidity, wind speed, cloud cover, and pressure in a single response ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'get current weather for a city', load the /weather operation schema, and execute it for q=Dublin. ## Key endpoints | 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 | ## Key resources - **Weather** — Current weather conditions for a single city by name, coordinates, or ID - **Box/City** — Current weather for every city inside a bounding box - **Group** — Current weather for a batch of cities by ID - **Find** — Search for cities by partial name and return weather ## Why Jentic - **Setup:** Wiring OpenWeatherMap by hand means appending the APPID key as a query parameter on every request and choosing the right lookup endpoint for a city name, coordinates, or bounding box yourself. Through Jentic you install once, import OpenWeatherMap from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** OpenWeatherMap lookups carry the location as query parameters rather than a resource id in the path, so scoping is by operation: you limit the agent to the operations it needs, such as current weather by city or by bounding box, and leave the others out unless you want them. Every operation the agent can call is one you chose to allow. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **WeatherAPI** — Drop-in replacement covering current weather, forecast, and history in one API - **Weatherbit** — Weather data provider with current, forecast, and severe weather alerts - **AccuWeather Core Weather API** — Commercial weather API with branded forecast products - **Visual Crossing Weather** — Historical and forecast weather often paired with current-conditions providers ## FAQ ### 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.