canonical: https://jentic.com/apis/az511.gov/az511-gov

# Az511 Gov Arizona 511 API

Jentic publishes the only available OpenAPI specification for Arizona 511 API, keeping it validated and agent-ready. The Arizona 511 API exposes traffic and transportation data published by the Arizona Department of Transportation, including cameras, weather stations, message signs, traffic events, alerts, rest areas, and Work Zone Data Exchange (WZDx) work-zone data. The API is rate limited to 10 calls per 60 seconds and authenticates via an API key in the `key` query parameter.

## For AI agents

Pull live Arizona traffic, weather, alerts, rest areas, and WZDx work-zone data from the state 511 feed. Suited to agents that brief travellers and freight planners on Arizona road conditions.

## Scope

Does not handle routing, navigation, or incident reporting back to ADOT - use Arizona 511 for read-only Arizona traffic, weather-station, message-sign, event, alert, rest-area, and WZDx work-zone data only.

## Capabilities

- Retrieve all live traffic cameras across the Arizona highway network
- Pull readings from ADOT-managed road weather stations
- List active dynamic message signs and their current text
- Get current traffic events and alerts statewide
- List public rest areas with location and amenity metadata
- Pull WZDx work-zone data for Arizona construction zones

## Use cases

### Freight WZDx Integration

Logistics platforms can ingest Arizona work-zone data through GET /wzdx, which serves the standard Work Zone Data Exchange format used by freight TMS and routing engines. This lets dispatchers route around construction with up-to-date geometry and timing. Suited to fleet operators and Class-8 routing tools.

Example prompt: Call GET /wzdx and feed the resulting WZDx feature collection into the fleet's routing engine for the day's planning

### Road-Conditions Briefing

Traveller-information apps can produce a road-conditions briefing by combining /endpoint/cameras, /endpoint/weatherstations, /endpoint/event, and /endpoint/alerts. The combined view tells drivers what is open, where weather is poor, and where incidents are slowing traffic. Suited to commuter apps and corporate travel briefings.

Example prompt: Call GET /endpoint/event and GET /endpoint/alerts and produce a one-paragraph road-conditions briefing covering Phoenix-Tucson and Phoenix-Flagstaff corridors

### Rest-Area and Trip Planning

Travel apps and RV planners can plot rest stops on a planned Arizona route by calling /endpoint/restareas and overlaying weather conditions from /endpoint/weatherstations. The combination allows pre-trip checks for long-haul routes through desert and mountain terrain. Suited to RV and tourism apps.

Example prompt: Fetch GET /endpoint/restareas and select the three closest rest stops to a planned overnight stop near Flagstaff

### Agent-Driven Travel Briefings via Jentic

An assistant agent can build a morning Arizona road briefing through Jentic by chaining the events, alerts, weather, and rest-area endpoints, all without holding the AZ511 API key. The 10-calls-per-60-seconds rate limit fits comfortably inside the briefing cadence. Suited to commuter copilots and corporate travel summaries.

Example prompt: Search Jentic for 'arizona traffic alerts', load GET /endpoint/alerts, and execute it as part of a morning briefing summarising statewide road conditions

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /endpoint/cameras | Get all traffic cameras |
| GET | /endpoint/weatherstations | Get all weather stations |
| GET | /endpoint/messagesigns | Get all dynamic message signs |
| GET | /endpoint/event | Get all traffic events |
| GET | /endpoint/alerts | Get all traffic alerts |
| GET | /endpoint/restareas | Get all rest areas |
| GET | /wzdx | Get WZDx work-zone data |

## Key resources

- **Cameras** — Live traffic camera registry across Arizona highways
- **Weather Stations** — Road weather sensor readings used by ADOT
- **Message Signs** — Current dynamic message sign text statewide
- **Events** — Active traffic incidents reported by ADOT
- **Alerts** — Closures, construction, and advisory alerts
- **Rest Areas** — Public rest areas with amenities and location metadata
- **Work Zones (WZDx)** — Standardised Work Zone Data Exchange feed for Arizona construction zones

## Why Jentic

- **Setup:** Wiring Arizona 511 by hand means adding the key to the key query parameter on az511.com/api, respecting the documented 10-calls-per-60-seconds limit, and building your own polling and back-off. Through Jentic you install once, import the Arizona 511 API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Every Arizona 511 endpoint is a read-only GET (cameras, weather stations, message signs, events, alerts, rest areas, and the WZDx work-zone feed) with no resource id in the path, so scoping is by operation. You limit the agent to the operations it needs, such as GET /endpoint/alerts or GET /wzdx, and the feed exposes no write operations that could change ADOT data.
- **Credential handling:** Your Arizona 511 API key is stored once, encrypted, by your own Jentic One instance and injected into the key query parameter at call time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'arizona traffic alerts' or 'arizona work zones', and Jentic returns the matching AZ511 operation with its input schema so the agent calls the right endpoint without reading the ADOT docs.

## Related APIs

- **AZ511 Traffic Data API** — Same Arizona DOT traffic data published under the .com domain with v2 path layout.
- **New York 511 API** — Equivalent state 511 traffic feed for New York instead of Arizona.
- **HERE Maps API** — HERE Maps provides routing and base maps that overlay well with state 511 traffic feeds.

## FAQ

### Why is there no official OpenAPI spec for Arizona 511 API?

ADOT does not publish an OpenAPI specification for the AZ511 feed. Jentic generates and maintains this spec so that AI agents and developers can call Arizona 511 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 Arizona 511 API use?

The Arizona 511 API uses an API key passed in the `key` query parameter. Through Jentic, the key is stored encrypted in the vault and added to the query string at call time so it never reaches the agent context.

### Can I get WZDx work-zone data with the Arizona 511 API?

Yes. GET /wzdx returns work-zone data in the standard Work Zone Data Exchange format, which is widely consumed by freight TMS and routing engines.

### What are the rate limits for the Arizona 511 API?

The Arizona 511 API is rate limited to 10 calls per 60 seconds, as documented in the spec. Plan polling cadence and batched briefings around that limit and back off on 429 responses.

### How do I get current Arizona traffic alerts through Jentic?

Search Jentic for 'arizona traffic alerts', load GET /endpoint/alerts, and execute it. Jentic injects the API key from the vault and returns the active alerts list.

### Is the Arizona 511 API free?

ADOT publishes the feed for public-information use and provides API keys on request via the AZ511 developer site. Confirm any commercial-use terms directly with ADOT.

### Can I limit what my agent is allowed to do with the Arizona 511 API?

Yes. Because you run Jentic One yourself, your own rules decide which Arizona 511 operations and credentials your agent may use. Every Arizona 511 endpoint is a read-only GET with no resource id in the path, so you scope by operation, allowing only the calls the agent needs such as GET /endpoint/alerts or GET /wzdx while withholding the rest. The feed exposes no write operations, so a scoped agent can never change ADOT data.