Quickstart
Three steps to your first call. Replace $WAVE_API_KEY with the key from the developer portal.
1. Get an API key
Create a developer account and issue a key. You can also pass it as the WAVE_API_KEY environment variable.
2. Install an SDK
Pick TypeScript, Python, or the CLI. Each ships typed clients and helpers for streams, clips, analytics, webhooks, AI, and payments.
TypeScript
pnpm add @wave-av/sdk
Python
pip install wave-sdk
CLI
npm i -g @wave-av/cli
3. Make your first call
GET /v1/usage reads your account's metered totals for the current period — no resource to create first, so it is the fastest way to confirm your key works end to end.
Your first call
curl https://api.wave.online/v1/usage \ -H "Authorization: Bearer $WAVE_API_KEY"
Expected response (shape):
{"org": "<your-org-id>", "range": {"from": "20260903", "to": "20260903", "days": 1}, "totals": {"bytes": 0, "frames": 0, ...}, "billable": {"bytes_GB": 0, ...}}
The same Authorization header works for every WAVE product. The gateway enforces auth, scope, entitlement, and metering — your key rides through the edge spoke untouched.
If it doesn't work
401
No key, or an invalid one, on the Authorization header.
Issue a key at /keys, then retry with Authorization: Bearer $WAVE_API_KEY.
402
The route is a priced capability and the request needs a payment intent instead of, or in addition to, a key.
See the agent-payments (x402 / MPP) guide at https://docs.wave.online/docs/agent-commerce.