Confirm Portland PBOT's Temporary Street Use Permitting (TSUP) process has no public submission API, and use PBOT's open-data map as the read-only alternative for active permit and closure visibility.
domain: portland.gov/transportation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review PBOT's Temporary Street Use Permitting (TSUP) page (portlandoregon.gov/transportation/article/620091) for traffic control plan/work-space diagram requirements
Confirm traffic control plans must be built using PBOT's own basemap tool, per pages 9-10 of the PBOT Traffic Control Manual — plans not built with it are rejected
Confirm permit applications and payments are submitted through the FastTrackGov-hosted login portal (portlandcityor.portal.fasttrackgov.com), which has no documented public API
For read-only visibility into active construction/right-of-way permits, use PBOT's 'Keep Portland Moving' map and the City of Portland Open Data Portal/PortlandMaps instead of expecting permit-submission API access
Check gis-pdx.opendata.arcgis.com for any permit-adjacent datasets that could substitute for a true permit API
Known gotchas
FastTrackGov is a shared third-party permitting platform used by many municipalities; for Portland it is login/portal-based, not a documented public API
The open-data map is a visibility tool for active projects, not a substitute for the authoritative TSUP permit record — don't treat it as a system of record
Plans must use PBOT's own basemap tool rather than a generic CAD/MUTCD-only diagram — verify this requirement before submission since it is a common rejection reason
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?