AccuWeather Core Weather API

Name: AccuWeather Core Weather API API
Brand: AccuWeather Core Weather API
Availability: InStock

★ Only Publicly Available SpecData 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.

Quickstart

Get started with AccuWeather Core Weather API 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 the 5-day forecast for a city"

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

Capabilities

What an agent can do with AccuWeather Core Weather API 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

GET STARTED

Start building with AccuWeather Core Weather API API

Explore with Jentic

View OpenAPI Spec

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.

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.

Use Cases

Patterns agents use AccuWeather Core Weather API 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

Why though 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.

Alternative

AccuWeather API

Full AccuWeather surface that adds severe weather alerts and daily lifestyle indices.

Choose the full AccuWeather API when you also need alerts and lifestyle indices. Choose Core Weather when you only need locations, conditions, and forecasts.

Alternative

OpenWeatherMap API

Free-tier-friendly weather API with current, forecast, and historical data.

Choose OpenWeatherMap when free-tier volume is the priority. Choose AccuWeather Core Weather for higher-resolution forecasts.

Alternative

WeatherAPI.com

Single-call weather API by city or coordinates without a separate location resolution step.

Choose WeatherAPI.com to skip the locationKey step. Choose AccuWeather Core Weather when you want stable locationKeys to cache.

FAQs

Specific to using AccuWeather Core Weather API 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.