Media infrastructure for an internet with two kinds of users
WAVE is media infrastructure for the agentic internet. The people who make media integrate once and move it across every transport. The agents that consume it discover the same routes over MCP and pay per call over HTTP-402 (x402) and MPP. Three engines under one call shape, paid per call by people and by agents, discoverable by agents without a sales motion. Video is the first capability on it; per-call payment is what sets it apart.
WAVE Online, LLC is pre-revenue. This page describes shipped technology and capability, not financial performance. Forward-looking materials are shared privately.
The bet
Software agents are beginning to discover, negotiate, and pay for services with no person in the loop. Two things are missing underneath them: a way to pay per call without opening an account, and media infrastructure a machine can find and call directly. WAVE is pure-play infrastructure for both. It is the machine-payment and agent-native media layer the rest of the stack sits on.
What is live today
Agent commerce in production
dispatch.wave.online is a public service in production. Agents discover media capabilities there and settle for them over x402 and MPP on Base mainnet. Each payment is screened against sanctions lists on the way through.
Sourcedispatch.wave.online ↗Native machine payments
HTTP-402 (x402) runs end to end. An agent pays per request and needs no account to do it.
Sourceapi.wave.online/.well-known/x402 ↗Protocol depth
SRT, AES67, MoQ, HLS, DASH, captions, and DRM sit behind one API. This is media infrastructure in its own right, not a wrapper around someone else's.
Sourcewave.online/protocol ↗Compliance on the payment path
KYB-cleared payment rails, sanctions screening on every settlement, and a structured record of each transaction. Agent commerce needs a counterparty a compliance team can approve. WAVE is built to be that counterparty.
Sourcewave.online/trust ↗Why now, why us
Agent platforms can run operations. What they cannot do yet is pay for a service without a person opening an account first, or move real-time video at all. WAVE removes both at the protocol layer. An agent calls a route, receives a 402, settles, and receives the media, on the same route a person calls with a key. Nothing in that path requires an account or a person in the loop, and nothing about it is a wrapper: the transports, the metering, and the settlement are WAVE's own.
| Caller | Account | Path |
|---|---|---|
| Agent | None. Pays per request over x402. | GET → 402 → settle → 200 |
| Person | An API key. | GET → 200 |
Who builds WAVE
Jake FinemanFounder
Jake Fineman has spent 15+ years in live production and broadcast infrastructure. He has built and operated global live command centers, designed sub-second WebRTC delivery for million-viewer events, and works hands-on across the live-video transport stack: SRT, RIST, NDI, Dante, HLS, RTMP, and WebRTC. WAVE is the platform he kept needing and could never buy.
Selected talks
- 2025Wall Street Video SummitNew York“Virtualized Hardware at Scale”
- 2024Silicon Valley Video SummitMountain View · Computer History MuseumFeatured speaker, Studio Production & Post track
- 2024
- 2024InfoCommLas VegasPanel: “Remote Production Workflows within Corporate Infrastructure”
- 2023
Speaks regularly on cloud and remote broadcast production.
Request access
Architecture, roadmap, and terms are shared privately under NDA. Write to us and we will open the data room.