Retrieve on-street parking block/meter metadata and restrictions via INRIX Parking Services (IPS) 3.0
domain: parking-api.inrix.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the current IPS 3.0 documentation (parking-api.inrix.com/doc/v3), not the deprecated docs.inrix.com/parking legacy pages
Authenticate through INRIX's standard authorization flow
Call the Blocks (v3) resource with a geographic filter to retrieve on-street block segments and meter details
Combine with the Occupancy & Probability resource for real-time or probabilistic space availability where supported
Consult the Destinations resource to resolve a city/neighborhood/venue name to a geographic search area first, if needed
Known gotchas
On-street real-time occupancy coverage is city-specific - check documented coverage before assuming block-level availability exists everywhere
Block metadata (restrictions, meter type) can change due to local regulation updates faster than INRIX's refresh cycle, so treat restriction data as advisory
Beta endpoints noted in INRIX's docs may have different rate limits or stability than GA v3 endpoints
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?