Interoperate with UTM/U-space systems using the InterUSS Platform and ASTM F3548 USS-to-USS protocol
domain: github.com/interuss · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review ASTM F3548-21 (UTM USS Interoperability standard) to understand the required USS-to-USS data-exchange behaviors
Deploy or connect to a Discovery and Synchronization Service (DSS) instance — InterUSS provides an open-source, standards-compliant DSS implementation used in production UTM/U-space deployments
Use the InterUSS monitoring/automated test suite to continuously validate your USS's compliance against F3548-21 requirements
Implement operational intent sharing and conflict-detection data exchange between your USS and peer USSs via the DSS
Participate in relevant UTM pilot programs or regulatory sandboxes to validate interoperability end-to-end before production rollout
Known gotchas
The DSS itself does not store flight/operational data — it's a lightweight discovery layer; USSs still exchange the substantive data directly with each other after discovery
F3548-21 compliance is necessary but not sufficient for regulatory approval in a given jurisdiction — national/regional UTM/U-space rules layer additional requirements on top
InterUSS is a Linux Foundation open-source project under active development; pin specific releases for production use rather than tracking main branch
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?