WAVE documentation
Guides, concepts, and reference for building on WAVE — for people and agents.
$ curl -s https://api.wave.online/.well-known/x402
{
"facilitator": "https://gateway.wave.online/v1/x402/facilitator",
"scheme": "exact", "version": "x402@1",
"networks": [
{"networkId": "eip155:8453"},
{"networkId": "eip155:84532"}
]
}
- 224
- documented paths
- 1.1.0
- OpenAPI 3.1 version
- 402
- what an unpaid call returns
No key on that call. The discovery document and the path count are read from openapi.json at the edge, so this block is the live surface, not a screenshot of one.
Getting started
Concepts
Concepts
The three engines (Media, Money, Dispatch) and the Trust pillar — how WAVE's one gateway works.
Agent commerce
How autonomous agents discover, negotiate, and pay for media over x402 and MPP.
What WAVE speaks
The transports, protocols, and codecs behind the one API.
WAVE Mesh
WAVE's native overlay network for resilient media transport — coordinator-driven routing, multi-region reach, heartbeat-driven failover.
Braided Audio
Publish N synchronized audio channels as one MoQ track — structural phase-lock for stem players, karaoke, remix decks, and multichannel beds.
Billing and payment
The two payment rails — subscription with metered usage for people, per-call HTTP-402 for agents — and how to read a price off the wire.
Machine Payments Protocol (MPP)
MPP — the second machine-payment protocol the gateway accepts alongside x402 — discovery, challenge shape, and live rail status.
Reference
Compliance & trust
WAVE's documented compliance posture.
MCP server
Call WAVE from any MCP client: the hosted endpoint at api.wave.online/mcp, the local server, and how a key scopes the tools.
Rendering
Render video and stills through /v1/render — its scopes, its six meters, and how an agent pays for a render per call.
MCP tools
Every tool the WAVE MCP server exposes to an agent, generated from the server's own tools/list.
Zoom integration
Connect Zoom to WAVE — adding, using, and removing the integration.
API endpoints
Every WAVE API endpoint with a working curl, generated from the served OpenAPI contract.
CLI reference
Every wave CLI command, generated from the published binary's own --help.
ADK reference
Every exported class, adapter and CLI command in the Agent Developer Kit, generated from the published package.
Errors
The normalized error envelope every WAVE API failure returns, generated from the gateway's own OpenAPI contract.