Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the receiving PSAP is willing to sponsor the project — APCO/TMA guidance states the PSAP must be the primary driver and owner of an ASAP implementation, not the alarm company.
Coordinate with the state's Nlets representative to confirm the PSAP's connection can carry ASAP transactions.
Have the PSAP sign a Traffic Authorization Letter (TAL) authorizing ASAP transmissions and submit it to the ASAP Service.
Complete joint testing between the monitoring center and the receiving PSAP's CAD system before go-live.
Once live, monitor for CAD acknowledgment responses routed back through the same path: monitoring company to CSAA message broker to Nlets to state control point to the PSAP's CAD system.
Known gotchas
A monitoring center cannot unilaterally 'join' ASAP — the receiving PSAP must actively participate and its CAD vendor must support the integration.
Coverage is PSAP-by-PSAP; being ASAP-enabled with one jurisdiction's PSAP does not mean neighboring PSAPs are also connected.
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?