Build with ATN.
This page provides a practical, public overview for builders. It intentionally avoids sensitive protocol parameters while describing integration modes, safety concepts, and ecosystem conventions.
Integration modes
Choose the approach that matches your product: broadcast campaigns, enterprise orchestration, or payment initiation.
Campaign triggers
Encode approved campaign actions and deliver them through any audio channel.
- Links & content handoffs
- Creator and podcast activations
- Offline-first experiences
Controlled execution
Allowlisted operations across fleets with audit‑ready governance and policy controls.
- Allowlists & roles
- Local validation modes
- Optional verification service
Checkout initiation
Start a controlled payment flow via acoustic token with validation before handoff.
- Checkout start + session context
- Group sessions
- Merchant integrations
Safety principles
ATN is designed around permission gating. The receiver decides what may execute — not the audio source.
Approved operations only
Unknown or unapproved actions do not execute. Apps can require explicit user confirmation.
Short validity windows
Tokens can be designed to expire quickly to reduce replay risk and limit accidental execution.
Traceability
Receivers can log validation and execution steps for enterprise environments.