AccuWeather Core Weather API
Browse all Accuweather APIs★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey8 EndpointsREST
For Agents
Resolve a location and retrieve current conditions, 1-day or 5-day daily forecasts, and 12-hour hourly forecasts from AccuWeather core endpoints so agents can deliver weather information for any global location.
Use for: I want the current weather conditions for Tokyo, Get the 5-day forecast for a given city, Find a locationKey for autocomplete suggestions as the user types, Resolve coordinates into a locationKey
Not supported: Does not handle severe weather alerts, lifestyle indices, radar tiles, or historical archives — use for location resolution and current/daily/hourly forecasts on AccuWeather only.
Jentic publishes the only available OpenAPI specification for AccuWeather Core Weather API, keeping it validated and agent-ready. This is the focused core cut of AccuWeather's data services, exposing 8 endpoints across location resolution, current conditions, and 1-day, 5-day, and 12-hour forecasts. Locations can be resolved by city search, autocomplete, or geoposition, and weather data is keyed by the resulting locationKey. The API uses an apikey query parameter for authentication and is hosted at dataservice.accuweather.com.
Install Jentic One Beta
Connect the AccuWeather Core Weather API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AccuWeather Core Weather 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.
1
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 | sh2
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 instanceJentic 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 AccuWeather Core Weather API.
Search cities by name with full text or autocomplete to resolve a locationKey
Resolve a latitude/longitude pair into a locationKey via geoposition search
Retrieve location detail by locationKey for display name, country, and timezone
Retrieve current weather conditions at a locationKey
Retrieve a 1-day daily forecast for short-horizon planning
Retrieve a 5-day daily forecast for trip-style planning
Retrieve a 12-hour hourly forecast for the next half-day
Use Cases
Patterns agents use AccuWeather Core Weather API for, with concrete tasks.
★ Autocomplete-Driven Location Picker
A weather widget powers a city autocomplete using GET /locations/v1/cities/autocomplete. Each keystroke calls the endpoint with the partial query and renders matching cities. When the user picks one, the locationKey is cached and used for subsequent forecast calls. The autocomplete keeps the picker responsive and avoids requiring users to type full city names.
Call /locations/v1/cities/autocomplete with the partial query 'San Fr' and return the top 5 matching cities with their locationKeys
1-Day Forecast for Same-Day Decisions
A logistics dashboard shows a 1-day forecast for each route start city using GET /forecasts/v1/daily/1day/{locationKey}. Operators glance at the day's high, low, and precipitation chance to triage routes before dispatch. This is lighter than a 5-day pull and fits the same-day decision horizon.
For each route's start city, retrieve the 1-day daily forecast and flag any with precipitation probability above 60%
Event Venue Weather at Coordinates
An event app stores venue coordinates rather than addresses. Weather lookup goes through /locations/v1/cities/geoposition/search to resolve a locationKey and then /forecasts/v1/hourly/12hour/{locationKey} for the event window. The flow handles outdoor festivals and pop-ups where there may be no canonical city name. Hourly precision lets organizers plan tent setup vs pack-up time.
Resolve venue coordinates to a locationKey and return the next 12 hours of hourly forecast
Agent-Driven Weather Lookup via Jentic
An AI travel assistant calls AccuWeather Core Weather through Jentic to answer 'what's the weather in Reykjavik this weekend?' The agent searches for the right operation, resolves the city, and returns the 5-day forecast. The apikey lives in the Jentic vault and is added at execution time.
Through Jentic, search 'get the 5-day forecast for a city', resolve Reykjavik, and return the daily highs, lows, and precipitation
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for accuweather core weather api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/locations/v1/cities/search
Search cities by full name
GET
/locations/v1/cities/autocomplete
Autocomplete city names from partial input
GET
/locations/v1/cities/geoposition/search
Resolve coordinates into a locationKey
GET
/locations/v1/{locationKey}
Retrieve detail for a locationKey
GET
/currentconditions/v1/{locationKey}
Current weather conditions
GET
/forecasts/v1/daily/1day/{locationKey}
1-day daily forecast
GET
/forecasts/v1/daily/5day/{locationKey}
5-day daily forecast
GET
/forecasts/v1/hourly/12hour/{locationKey}
12-hour hourly forecast
GET
/locations/v1/cities/search
Search cities by full name
GET
/locations/v1/cities/autocomplete
Autocomplete city names from partial input
GET
/locations/v1/cities/geoposition/search
Resolve coordinates into a locationKey
GET
/locations/v1/{locationKey}
Retrieve detail for a locationKey
GET
/currentconditions/v1/{locationKey}
Current weather conditions
GET
/forecasts/v1/daily/1day/{locationKey}
1-day daily forecast
GET
/forecasts/v1/daily/5day/{locationKey}
5-day daily forecast
GET
/forecasts/v1/hourly/12hour/{locationKey}
12-hour hourly forecast
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AccuWeather API keys are stored encrypted in the Jentic vault. Jentic injects the apikey query parameter at execution time, so raw key values never appear in agent context or logs.
Intent-based discovery
Agents search by intent — for example, 'get the 5-day forecast for a city' — and Jentic returns the city search and forecast endpoints together with their parameter schemas.
Time to first call
Direct integration: a few hours to wire up locationKey caching and apikey plumbing. Through Jentic: under 30 minutes for the first end-to-end forecast call.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AccuWeather Core Weather API through Jentic.
Why is there no official OpenAPI spec for AccuWeather Core Weather API?
AccuWeather does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AccuWeather Core Weather 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 AccuWeather Core Weather API use?
An apikey query parameter on every request. Through Jentic, the key is stored encrypted in the vault and injected at execution time so the raw value stays out of agent context.
How do I get a 5-day forecast for a city?
Two calls. First GET /locations/v1/cities/search with the city name to obtain a locationKey, then GET /forecasts/v1/daily/5day/{locationKey}. Cache the locationKey per city — it is stable across calls.
What are the rate limits for the AccuWeather Core Weather API?
The OpenAPI spec does not document explicit rate limits. Limits are tied to the AccuWeather plan tier (free, standard, prime, elite) and are documented in the AccuWeather developer portal. Implement exponential backoff on HTTP 429.
How is this different from the AccuWeather API entry on Jentic?
The Core Weather API is the leaner cut focused on locations, current conditions, and forecasts (1-day, 5-day, hourly). The full AccuWeather API entry adds severe weather alerts and lifestyle indices. Pick this one when alerts and indices are not needed.
How do I look up weather by coordinates through Jentic?
Run pip install jentic, then search 'resolve coordinates to a weather forecast'. Jentic returns /locations/v1/cities/geoposition/search and the forecast endpoints. The apikey is injected at execution time, so you only supply the coordinates and locationKey.
GET STARTED