Concepts

WAVE is media infrastructure for the agentic internet: one gateway in front of three engines, used the same way by two kinds of caller. A person calls with a key; an agent calls and pays per call. Every transport, every product, and every caller share one call shape and go through the same plane.

Three engines, one surface

Carry — Media Engine. Move the signal, intact, on time, metered. Clock, integrity, sync, reliability, and metering are solved once; every transport (SRT, RTMP, WebRTC, MoQ, and the rest) is a thin adapter on top. The protocol is a parameter you pass at call time, not a commitment you make at design time.

Clear — Money Engine. Move the value, priced, settled, screened, metered. People pay with cards and keys; agents pay over HTTP-402 (x402) or MPP. Same rail, same enforcement, whether the caller is a person or a script.

Choose — Dispatch Engine. Choose the path: which tier runs the work, at what cost, under whose keys. Each unit of work is classified at the edge and routed to the cheapest capable path, metered per decision — an agent pays per turn the way it pays per stream.

One API. One gateway. Three planes. An agent transacts on all three the same way a person does.

The Trust pillar

The gateway is also the trust boundary: authentication, scope, entitlement, and metering are enforced in one place, so policy is written once instead of drifting per product.

• Privacy: GDPR & CCPA aligned, with a signed DPA available.
• Healthcare: HIPAA-ready under a signed Business Associate Agreement (BAA).
• AI transparency: EU AI Act Article 26 record-keeping, with immutable audit records.
• Infrastructure: built on Cloudflare, Supabase, and Stripe — all SOC 2 Type II infrastructure. WAVE itself does not hold a SOC 2 or ISO attestation.

See the full posture on Compliance & trust, and the normalized failure shape every one of these engines returns on Errors.

Try it

Every engine answers through the same gateway. One call proves the surface is live:

curl -s https://api.wave.online/openapi.json | jq '.info.title, .info.version'

Where each engine lives in these docs