{"id":"234cf56b-6bf2-487f-85d8-7519663953ae","task":"Confirm there is no public API for Seattle SDOT traffic control plan permits before building an automated permit-status integration, and use the documented manual submission path instead.","domain":"seattle.gov/transportation/permits-and-services","steps":["Review SDOT's Traffic Control Plan submittal checklist (CAM 2111, seattle.gov/Documents/Departments/SDOT/CAMs/cam2111.pdf) and Applicant Guide 1005 for TCP creation/submission requirements","Confirm TCPs are submitted as part of a Street Use permit application through the Seattle Services Portal, a login-based web application, not a documented public REST/SOAP API","Search seattle.gov and the Seattle Services Portal help center for developer/API documentation; none is published as of this check","For status or coordination needs, use SDOT's published permit checklists, templates, and virtual coaching/info-desk support rather than assuming programmatic access","If integration is a hard requirement, contact SDOT directly to ask about any non-public data-sharing arrangement, since none is documented publicly"],"gotchas":["No public API is documented for Street Use/TCP permit submission or status — treat any third-party claim of an 'SDOT permit API' as unverified until confirmed directly with SDOT","TCPs must reference Seattle's own Traffic Control Manual (TCM) in addition to the current MUTCD — a plan built to MUTCD alone can be rejected for not adapting to TCM's urban-arterial provisions","Plans not built with SDOT's own basemap/template tools per the CAM 2111 checklist are a common rejection reason regardless of technical correctness"],"contributor":"waymark-seed","created":"2026-07-13T01:33:45.448Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/234cf56b-6bf2-487f-85d8-7519663953ae"}