Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look 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.
Use for: I want the current weather for San Francisco, Get the 5-day forecast for a given latitude and longitude, Find the AccuWeather location key for Paris, France, Retrieve hourly forecasts for the next 12 hours at a location
Not supported: Does not handle weather radar tiles, historical weather archives, or air quality measurements - use for current conditions, daily/hourly forecasts, alerts, and indices on AccuWeather only.
Jentic publishes the only available OpenAPI specification for AccuWeather API, keeping it validated and agent-ready. AccuWeather provides current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices for any location worldwide. The API resolves locations through a city search or geoposition, returns a location key, and then serves weather data keyed off that location key. Authentication is via an apikey query parameter, and the base URL is dataservice.accuweather.com.
Install Jentic One Beta
Connect the AccuWeather API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AccuWeather 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" | 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" | 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 API.
Resolve a city name into an AccuWeather locationKey via /locations/v1/cities/search
Resolve latitude and longitude into a locationKey via /locations/v1/geoposition/search
Retrieve current weather conditions for a locationKey
Retrieve a 5-day daily forecast for a locationKey
Retrieve a 12-hour hourly forecast for a locationKey
Pull active severe weather alerts for a locationKey
Retrieve daily lifestyle indices (running, allergy, beach, etc.) for a locationKey
Use Cases
Patterns agents use AccuWeather API for, with concrete tasks.
★ Travel App Weather Cards
A travel itinerary app shows a weather card for each destination by first calling /locations/v1/cities/search to resolve the city name, then /forecasts/v1/daily/5day/{locationKey} for the trip dates. Travelers see expected conditions before they pack. Caching the locationKey per destination reduces repeat resolution calls.
Resolve 'Lisbon' to a locationKey, then call /forecasts/v1/daily/5day/{locationKey} and return the high and low for each of the next 5 days
Weather-Aware Field Operations
A logistics dispatcher uses the geoposition search and alerts endpoints to flag deliveries entering an active severe weather zone. The system geocodes each delivery address externally, calls /locations/v1/geoposition/search for the locationKey, and queries /alerts/v1/{locationKey}. Drivers get a heads-up rather than discovering hazards en route.
For each delivery in tomorrow's schedule, look up the locationKey and return any active alerts as a routing risk flag
Outdoor Activity Planning with Lifestyle Indices
A running app shows a 'running index' for the user's location each morning, sourced from /indices/v1/daily/5day/{locationKey}. The app picks the running-specific index and renders a 5-day strip. Compared to showing raw temperature, the index combines temperature, humidity, wind, and air quality into a single planning signal.
Retrieve the 5-day running index for a user's home locationKey and return the day with the highest score
Agent-Driven Weather Lookup via Jentic
An AI assistant in a calendar app answers 'what's the weather for my meeting in Berlin tomorrow?' by calling AccuWeather through Jentic. The agent searches for the right operation, resolves the location, and returns the forecast. The apikey query parameter is injected by Jentic at execution time.
Through Jentic, search 'get the current weather for a city', resolve Berlin, and return current conditions plus tomorrow's daily forecast
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for accuweather api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/locations/v1/cities/search
Search cities by name to resolve a locationKey
GET
/locations/v1/geoposition/search
Resolve latitude and longitude into a locationKey
GET
/currentconditions/v1/{locationKey}
Current weather conditions for a location
GET
/forecasts/v1/daily/5day/{locationKey}
5-day daily forecast
GET
/forecasts/v1/hourly/12hour/{locationKey}
12-hour hourly forecast
GET
/alerts/v1/{locationKey}
Active severe weather alerts
GET
/indices/v1/daily/5day/{locationKey}
Daily lifestyle indices
GET
/locations/v1/cities/search
Search cities by name to resolve a locationKey
GET
/locations/v1/geoposition/search
Resolve latitude and longitude into a locationKey
GET
/currentconditions/v1/{locationKey}
Current weather conditions for a location
GET
/forecasts/v1/daily/5day/{locationKey}
5-day daily forecast
GET
/forecasts/v1/hourly/12hour/{locationKey}
12-hour hourly forecast
GET
/alerts/v1/{locationKey}
Active severe weather alerts
GET
/indices/v1/daily/5day/{locationKey}
Daily lifestyle indices
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 API
- Foundational (D+)48/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability15
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.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
32%
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.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
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 API by hand means appending the apikey query parameter on every call and resolving a location key before you can read conditions or forecasts. Through Jentic you install once, import the AccuWeather 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 current conditions. You choose the operations it may call, so forecast, alert, or index 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 current weather for a city', and Jentic returns the location-search and current-conditions 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 API through Jentic.
Why is there no official OpenAPI spec for AccuWeather API?
AccuWeather does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AccuWeather 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 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 key value never appears in the agent's context.
How do I get the weather for a city with the AccuWeather API?
Two steps. First call GET /locations/v1/cities/search with the city name to get a locationKey, then call GET /currentconditions/v1/{locationKey} or GET /forecasts/v1/daily/5day/{locationKey}. The locationKey is stable, so cache it per location to avoid repeating the lookup.
What are the rate limits for the AccuWeather API?
The OpenAPI spec does not document explicit rate limits - they are tied to your AccuWeather plan tier (free, standard, prime, elite). Implement exponential backoff on HTTP 429 and check your plan's daily call quota in the AccuWeather developer portal.
How do I get a 5-day forecast through Jentic?
Run pip install jentic, then search 'get the 5-day forecast for a city'. Jentic returns the locations search and forecast endpoints. Resolve the city, then call /forecasts/v1/daily/5day/{locationKey}. The apikey is injected by Jentic at execution time.
Does the AccuWeather API include severe weather alerts?
Yes. GET /alerts/v1/{locationKey} returns active alerts from official sources for the given location. Coverage and alert categories vary by region - North American and European coverage tends to be denser than less monitored areas.
Can I limit what my agent is allowed to do with the AccuWeather API?
Yes. Because Jentic One is self-hosted, you decide which of the read-only AccuWeather operations your agent may call, so you can allow it to search for a city and read current conditions while withholding the daily forecast, hourly forecast, alerts, and lifestyle index reads. Since every one of these endpoints only takes a location key in the URL or query and returns data, scoping the agent to just the operations it needs means it cannot reach the rest. Your own rules govern both the permitted operations and the API key that lets them run.
GET STARTED