Your Dante feed just became a link anyone can tap.
The board mix has always been trapped in the room, wired to the Dante network and locked behind receiver hardware. Text a link instead. They tap play and they are in your mix, live, in the browser already open on their phone. No app. No box. No pairing.
WAVE is media infrastructure for the agentic internet. Listen is the audio half you can hand to a person; the same route answers an agent, and both pay for it per call.
The link you text is not the key.
One durable token authorizes your organization's audio, and it stays on the server. It is never sent to a listener, never embedded in a URL, and never reachable from a page. Each tune-in spends it once, server side, to mint a fresh read-only join, and only that join crosses to the browser. Hand out a hundred links and you have handed out zero credentials.
$ curl -s -X POST https://listen.wave.online/api/moq-join 400 {"error":"invalid stream id — must match /^[A-Za-z0-9._-]{1,64}$/"}
That is the route refusing a malformed request before it becomes someone else's problem. A route that was never built answers 404; this one read the input, judged it, and told you the rule it applied. The namespace check is stricter still, and a bad id stops here as a 400 rather than surfacing downstream as a 502.
No app, no box, no pairing
Your Dante or AES67 source is bridged over Media-over-QUIC and plays in a stock browser, with a live scope, a peak and RMS meter, per-stem faders on a multi-stem channel, and one-tap record to WAV.
1. Pick a stream
An operator picks a channel on the Dante network — a mix, a program feed, a language track.
2. Share a link
Listen serves that channel at listen.wave.online/s/<id> — public or gated behind a listen:read entitlement.
3. Tap play, anywhere
A listener opens the link on any phone, tablet, or laptop, taps play, and hears the stream live over MoQ + WebAudio — with a live scope, meters, and a record button.
What teams build on WAVE's rails
Listen is one experience on the rails — here's what the same real-time audio infrastructure lets you and your teams build.
Share your Dante feed to any phone
Point Listen at a channel on your Dante network and hand out a link. No app to install, no hardware DI box, no wifi-pairing dance — anyone with a browser hears the mix.
Program audio to remote talent and listeners
Distribute the program feed off your console to remote talent, IFB, or overflow listeners anywhere with a network path — the same audio plane your booth already runs on.
Multi-language and overflow listening, BYOD
Run a language channel per Dante stream and let the audience bring their own phone and earbuds — no rented headsets, no per-seat receiver hardware.
Dante over the web, as a service
Mint a short-lived read-only join token from your own backend and embed the player, or speak the wire directly — Dante-to-web as an API you build on, not a one-off demo.
One thing you can do on WAVE's rails
WAVE is media infrastructure for the agentic internet: one call shape moves live and on-demand media, and people and agents both call it and pay for it per call. Listen is one thing built on those rails, sharing the edge, the entitlement check and the per-minute meter behind WAVE Voice. Mint a read-only join from your own backend, embed the player, or speak the MoQ wire directly.
Live now
Public streams anyone can tune into right now — no login. Gated streams need a listen:read session.
Federated — auth, entitlement, and metering run through api.wave.online; this spoke serves the directory + tune-in pages and mints short-lived read-only MoQ join tokens. The durable org token never touches the browser.