Media

Money

Dispatch

Company

Developer portal · one API key

Build on the media infrastructure.

WAVE is media infrastructure for the agentic internet: one API for live and on-demand video, AI media, and agent-native payments. Get a key, install an SDK, and ship — you and your agents use the same rails.

One route. Two callers.Your first call
personsends a key
$ curl https://api.wave.online/v1/usage \
    -H "Authorization: Bearer $WAVE_API_KEY"

200 OK
{"org":"<your-org-id>",
 "range":{"from":"20260903","to":"20260903","days":1},
 "totals":{"bytes":0,"frames":0},
 "billable":{"bytes_GB":0}}
agentsends nothing, gets a price
$ curl https://api.wave.online/v1/clips

HTTP/2 402
{"x402Version":1,"error":"payment required",
 "accepts":[{"scheme":"exact","protocol":"x402",
   "network":"base","maxAmountRequired":"20000",
   "asset":"USDC","resource":"/v1/clips"}]}

Same gateway, same route shape, one key model. Responses captured from api.wave.online on September 3, 2026.

Start building

Getting started

Create a developer account, claim an API key, and make your first call against a route that is live today: usage, clips, transcription, and more, all documented in OpenAPI.

Quickstart →

API keys

Authenticate with a Bearer key. Pass it via the SDK constructor or the WAVE_API_KEY environment variable. The key is shown once at issue time — copy it immediately; WAVE never stores the plaintext.

Get a key →

SDKs

Official client libraries for TypeScript, Python, and the command line, plus the ADK, MCP server, and Dispatch packages. Typed responses, sync and async clients, and built-in helpers for streams, clips, analytics, webhooks, AI, and payments.

Browse SDKs →

API reference

The full OpenAPI surface for streaming, AI, webhooks, agents, and the Machine Payments Protocol. Every endpoint is gateway-enforced and metered; Authorization rides through untouched.

Open the reference →

Webhooks

Subscribe to stream, VOD, clip, and payment events. Deliveries are signed with HMAC-SHA256, retried with exponential backoff, and replayable from the dead-letter queue.

Webhooks guide →

Agent payments (x402 / MPP)

Metered endpoints negotiate payment over HTTP-402. Agents sign an EIP-712 intent and replay the request — per-request charge or pre-funded session vouchers, settled in USDC on Base or Tempo.

MPP guide →

What you get

One API key across streaming, AI, and paymentsTypeScript, Python, and CLI SDKs, plus ADK, MCP server, and DispatchRTMPS · SRT · WebRTC (WHIP) ingest from one callSigned webhooks with retry + DLQ replayx402 / MPP agent payment negotiationGateway-enforced auth, scope, and metering

Products

Ship on media infrastructure for the agentic internet.

Get a key, install an SDK, and make your first call. Agents and people, same rails.