Media infrastructure for the agentic internet

The shift

The internet has a second kind of user. Alongside the people who watch, create, and broadcast, there are now autonomous agents that discover, negotiate, and pay for services with no person in the loop. Most infrastructure was built for one of those users, not both. Media is the hardest case. It is real-time, expensive to move, split across a dozen incompatible transports, and almost never designed for a machine to find and pay for directly.

What WAVE is

WAVE is media infrastructure for the agentic internet: one call shape moves live and on-demand media across every transport, and both kinds of users, people and agents, discover it, call it, and pay for it per call. A person integrates once with a key. An agent reads the skills index, calls the same route, and settles over HTTP-402.

Three engines sit under that one call shape. One carries the media, one clears the payment, one chooses the path.

The WAVE Media Engine: move the media

The hard parts of moving audio, video, and captions are solved once, in an open core, so every transport is a thin adapter on top: a single media clock, a uniform duplex adapter interface, integrity, sync, reliability, and metering. Add a protocol and it inherits all of that. SRT, RIST, AES67, OMT, MoQ, HLS, WebRTC: none of them rebuilds the hard parts. Live adapters ship on the open core today, and each capability on the engine page carries its status: live, building, or planned.

The Media Engine

The WAVE Money Engine: get both kinds of users paid

Payment, identity, and compliance are native to the same surface, not bolted on. WAVE runs a public x402 facilitator, live on Base mainnet. An agent proves its identity with a did:wave credential, settles on-chain, and is screened against sanctions on the way through, on the same routes a person hits with a bearer key. This is what sets WAVE apart: every capability is callable and payable over HTTP-402 on the same route.

The Money Engine

The WAVE Dispatch Engine: choose the path

Once media can move and value can settle, something still has to decide what compute each request needs. The Dispatch Engine classifies a prompt at the edge and returns a routing decision in milliseconds: which tier runs the work, at what cost, under whose keys. WAVE bills the decision, $0.0001 over x402 or a card subscription, and never the inference. Keys, prompts, and models stay on your infrastructure. Like every WAVE capability, each decision is callable with a key and payable by an agent over HTTP-402 on the same route, and the service runs in production at dispatch.wave.online.

The Dispatch Engine

The WAVE Wallet

The Money Engine’s product face is the WAVE Wallet: a wallet every party holds. The creator and their agent. The viewer and theirs. When all four sides transact on one rail, micropayments for media become native and cheap. That four-party symmetry is the point. The WAVE Wallet is being built.

Trust you can check

Every request, from a person or an agent, passes one edge gateway that enforces authentication, scope, entitlement, and metering, and returns 403 when an account is not entitled. The posture is public. The trust center states the compliance position (GDPR and CCPA aligned with a signed DPA available, HIPAA-ready under a signed BAA, EU AI Act Article 26 record-keeping) and lists every subprocessor. The same posture is machine-readable at trust.wave.online, where the security contact and disclosure policy ship as an RFC 9116 security.txt that a person or an agent reads with one request.

Trust center

Why it’s different

One surface for people and agents: the same routes, the same enforcement, three engines under one call shape. Each capability is marked live, building, or planned. Open where it earns trust, metered where it earns revenue.

Who it’s for

The people who make media: creators, streamers, broadcasters, and media-infrastructure teams. And the agents that discover, call, and pay for it. WAVE is the layer underneath both.