Retrieve standardized work zone and road closure data from 511 SF Bay's WZDx feed
domain: 511.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a 511.org Open Data API token
Call the traffic/wzdx endpoint with your api_key to retrieve the WZDx-formatted feed
Parse the response as a standard Work Zone Data Exchange feed (road event features with location, direction, and timing)
Optionally set includeAllDefinedEnums=true to preserve non-standard directional values like 'both' instead of having them collapsed to 'undefined'
Cross-reference with the Traffic Events API if both crash/incident and planned work-zone data are needed together
Known gotchas
By default the API converts the non-standard 'both' directional value to WZDx's 'undefined' enum - set includeAllDefinedEnums=true if that distinction matters
This feed only covers Bay Area work zones, not a national WZDx aggregation
It shares the same per-token rate limit as the other 511 SF Bay endpoints, so budget requests across all 511 endpoints used together
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?