AccuWeather APIs for AI Agents

Data EnrichmentData TransformationJentic-Generated SpecsAPI keyAgent Ready

www.accuweather.com·Developer portal → developer.accuweather.com

AccuWeather API Catalog

2 APIs across 1 product group. All share one credential.

Data Enrichment2

AccuWeather Core Weather APIResolve 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.~8 endpoints AccuWeather APILook up a location and retrieve current conditions, 5-day daily forecasts, 12-hour hourly forecasts, alerts, and lifestyle indices from AccuWeather so agents can answer weather questions for any global location.~7 endpoints

Which AccuWeather API should I use?

I want to...	Use	Why
Location resolution plus current, daily, and hourly forecasts with the smallest surface	AccuWeather Core Weather API	The core cut exposes city search, autocomplete, geoposition search, location detail, current conditions, and 1-day, 5-day, and 12-hour forecasts without extra endpoints.
Weather forecasts together with severe weather alerts or lifestyle indices	AccuWeather API	The full AccuWeather API adds active severe weather alerts and daily lifestyle indices such as running, allergy, and beach on top of conditions and forecasts.
Current conditions and 5-day or 12-hour forecasts for a resolved location	AccuWeather Core Weather API	Both APIs serve these reads, but the core cut is the leaner default when alerts and indices are not needed.

Install Jentic One Beta

Connect the AccuWeather APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AccuWeather APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring these AccuWeather APIs by hand means appending the apikey query parameter on every call and resolving a location key before you can read conditions, forecasts, alerts, or indices. Through Jentic you install once, add the AccuWeather APIs you need from the Jentic directory, store your AccuWeather key once, and your agent calls both.

Permission scoping

Every operation across both APIs is a read-only lookup that takes a location key, so with your own Jentic One instance your rules decide which operations the agent may call. You can grant a city search and current conditions while withholding forecasts, alerts, and lifestyle indices, or open only the reads a given task needs.

Credential isolation

FAQs

Specific to using AccuWeather APIs through Jentic.

What is the difference between the two AccuWeather APIs on Jentic?

The Core Weather API is the leaner cut focused on location resolution, current conditions, and 1-day, 5-day, and 12-hour forecasts. The full AccuWeather API covers those same forecasts and adds active severe weather alerts and daily lifestyle indices such as running, allergy, and beach. Use the core cut when alerts and indices are not needed, and the full API when they are.

Do I need separate credentials for each AccuWeather API?

No. Both APIs authenticate with a single AccuWeather apikey query parameter, so one AccuWeather API key covers every operation across both. Your key is tied to your AccuWeather plan tier, which governs your call quota regardless of which of the two APIs you call.

How do location keys work across the two APIs?

Both APIs resolve a location by city name, autocomplete, or coordinates into a stable AccuWeather location key, then serve weather data keyed off that key. The key is stable across calls and shared between the two APIs, so you can resolve a location once, cache the key, and reuse it for conditions, forecasts, alerts, or indices.

Can an agent combine forecasts with alerts and indices?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs2 in catalogue

Endpoints15 indexed

AuthAPI key — 1 credential for all 2 APIs

ProvenanceJentic-generated specs

Agents can resolve any global location by city name, autocomplete, or coordinates into an AccuWeather location key, then read current conditions, 1-day, 5-day, and 12-hour forecasts, active severe weather alerts, and daily lifestyle indices for that location.

AccuWeather offers two read-only weather APIs that share one location-key model and one apikey: a focused core cut for location resolution plus current, daily, and hourly forecasts, and a fuller surface that also returns severe weather alerts and lifestyle indices such as running, allergy, and beach. Both cover any global location and favor stable location keys that callers can cache to avoid repeat resolution.

Use for: Reading AccuWeather current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices for any global location after resolving it to a location key by city, autocomplete, or coordinates.

Not supported: weather radar tiles, historical weather archives, air quality measurements, writing weather data, minute-by-minute nowcasts

Credentials: Both APIs authenticate with a single AccuWeather apikey query parameter, so one AccuWeather API key covers every operation across both.

All 2 AccuWeather OpenAPI specs are Jentic-generated and indexed by Jentic, kept validated and agent-ready.

AccuWeather provides weather data for any location worldwide, including current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices. Jentic publishes and maintains OpenAPI specifications for AccuWeather's weather data services, keeping them validated and agent-ready. Both APIs resolve a location by city name, autocomplete, or geoposition into a stable location key, then serve weather data keyed off that location key. Authentication is a single apikey query parameter on every request, and both APIs are hosted at dataservice.accuweather.com. The Core Weather API is the leaner cut focused on location resolution, current conditions, and 1-day, 5-day, and hourly forecasts, while the full AccuWeather API adds severe weather alerts and daily lifestyle indices.

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Faccuweather.com" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faccuweather.com" | 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.

Once connected, ask your agent something like: “get weather forecasts and alerts for a location”.

What AI Agents Can Do with AccuWeather

Each workflow spans multiple AccuWeather APIs. Jentic routes each operation to the right API automatically.

Autocomplete picker to a full weather panel

A weather widget resolves a city as the user types with the core API autocomplete, caches the returned location key, then reads current conditions plus a 5-day forecast from the full AccuWeather API and appends any active severe weather alerts. The shared location-key model lets one resolved key drive reads on both APIs.

Example prompt:

Autocomplete 'San Fr' via the core API, cache the top location key, then return current conditions, the 5-day forecast, and any active alerts from the full AccuWeather API

APIs used

AccuWeather Core Weather API + AccuWeather API

Event venue planning with hourly forecast and alerts

An event app stores venue coordinates, resolves them to a location key through the core API geoposition search, pulls the next 12 hours of hourly forecast, then checks the full AccuWeather API for active severe weather alerts covering the event window. Organizers get both timing and hazard signals from one location key.

Example prompt:

Resolve venue coordinates to a location key with the core API, return the 12-hour hourly forecast, then flag any active alerts from the full AccuWeather API

APIs used

AccuWeather Core Weather API + AccuWeather API

Trip planning with forecasts and a running index

A travel assistant resolves each destination through the core API, retrieves a 5-day daily forecast for the trip dates, and adds the daily running lifestyle index from the full AccuWeather API so travelers see both expected conditions and an activity signal. One AccuWeather key drives every call.

Example prompt:

Resolve 'Lisbon', return the 5-day daily highs and lows from the core API, then add the 5-day running index from the full AccuWeather API

APIs used

AccuWeather Core Weather API + AccuWeather API

Your single AccuWeather API key is stored once, encrypted, by your own Jentic One instance and injected as the apikey query parameter at execution time for calls to either API. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search the Jentic directory by intent such as 'get the current weather for a city' or 'get the 5-day forecast for a city', and Jentic returns the matching location-search and weather operations across both APIs with their parameter schemas, so the agent calls the right endpoint without browsing reference docs.

Yes. An agent can resolve a location once, read forecasts from either API, and pull severe weather alerts and lifestyle indices from the full AccuWeather API for the same location key. This lets a single request flow return conditions, a forecast, and a hazard or activity signal together.

Are these AccuWeather APIs read-only?

Yes. Every operation across both APIs is a read: location resolution, current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices. There are no write operations, so an agent using these APIs can retrieve weather data but cannot change anything on AccuWeather.

Why does Jentic publish OpenAPI specs for AccuWeather?

AccuWeather does not publish an OpenAPI specification. Jentic generates and maintains the specs for both APIs so AI agents and developers can call them through structured tooling. The specs are validated against the live API and kept up to date, which keeps both entries agent-ready.

What weather data is out of scope for these APIs?

These APIs do not cover weather radar tiles, historical weather archives, air quality measurements, or minute-by-minute nowcasts. They are built for location resolution and current, daily, and hourly forecasts, plus alerts and lifestyle indices on the full API.

AccuWeather APIs for AI Agents

AccuWeather API Catalog

Data Enrichment2

Which AccuWeather API should I use?

Connect the AccuWeather APIs to your agent

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

What AI Agents Can Do with AccuWeather

If you need a different Data Enrichment vendor