AccuWeather Core Weather API
Browse all Accuweather APIs70
AI ReadinessAI-Aware (B+)70/100
Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Faccuweather.com%2Faccuweather-core-weather-api" | sh2
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%2Faccuweather-core-weather-api" | 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 your Jentic One instance 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AccuWeather Core Weather API
- AI-Aware (B+)70/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
26%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AccuWeather Core Weather API by hand means appending the apikey query parameter on every call and resolving a location key before requesting current conditions or forecasts. Through Jentic you install once, import the AccuWeather Core Weather API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
These endpoints are read-only lookups that take the location key in the URL or query, so limit the agent to the operations it needs, such as searching for a city and reading its 5-day forecast. You choose the operations it may call, so hourly or current-conditions reads are not included unless you add them.
Credential isolation
Your AccuWeather API key is stored once, encrypted, by your own Jentic One instance and injected as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get the 5-day forecast for a city', and Jentic returns the city-search and forecast operations with their parameter schemas so the agent calls the right endpoint without browsing the reference docs.
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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the AccuWeather Core Weather API?
Yes. Because you run Jentic One yourself, your own rules decide which of these read-only lookups the agent may call, so you can grant just the operations it needs, such as searching for a city and reading its 5-day daily forecast. If you do not add the current-conditions, 1-day, or 12-hour hourly endpoints, the agent cannot invoke them. Your AccuWeather API key is injected as the apikey query parameter at execution time and never enters the agent's context.
GET STARTED