One import. Your code builds on WAVE — and your agents pay their own way through it.
Install the TypeScript or Python SDK, drop in one API key, and call live streaming, AI media, and pay-per-call payments through a single gateway. Open source, generated from one OpenAPI spec — and autonomous agents run on the same rails, paying for what they use over HTTP 402.
No catch, nothing to stitch.
TypeScript and Python are live and open source today, both generated from one shared OpenAPI spec, so they never drift from the API. One API key authorizes streaming, AI, and payments at a single gateway — the SDK forwards your Bearer key and the gateway does auth, scope, entitlement, and metering. Agents pay per call over HTTP 402 (x402 / Machine Payments Protocol) on that same surface — there is no separate agent stack to build.
Start building
Quickstart
Install an SDK, configure your API key, and make your first call. The same key works across every WAVE product; the SDK sends it as a Bearer token and the gateway does the rest.
Quickstart →TypeScript SDK
The @wave-av/sdk umbrella for Node and the browser — one client over the WAVE API, generated from the shared OpenAPI spec. A layered, AWS-v3-style split into per-product packages is rolling out. Open source on GitHub.
TypeScript →Python SDK
The Python client for the WAVE API, generated from the same OpenAPI spec as every other SDK. Open source on GitHub.
Python →API reference
Every SDK wraps one gateway-fronted surface at api.wave.online, described by OpenAPI: streaming, clips, AI media, webhooks, agents, and the Machine Payments Protocol. The reference is the canonical contract.
Reference →Authentication & entitlement
SDKs send your API key as a Bearer token; they never make access decisions. The wave-gateway authorizes, scopes, and meters every call, and returns 403 when your account is not entitled to an endpoint.
Get an API key →Open core
The SDK fleet is generated from a shared OpenAPI spec in one open-core umbrella repo, wave-av/sdks. Read the source, file issues, and follow new languages as they land.
Browse the source →The SDK fleet
TypeScript Available
@wave-av/sdk
pnpm add @wave-av/sdk
- Install the @wave-av/sdk umbrella — one client over the whole API
- Layered, AWS-v3-style per-product packages rolling out
- Generated from the shared OpenAPI spec
Python Available
wave-sdk (PyPI)
pip install wave-sdk
- Generated from the same OpenAPI spec as the TypeScript SDK
- Covers the gateway-fronted API surface
- Open source on GitHub
Go Coming soon
—
# planned — generated from the shared OpenAPI spec
- Planned via codegen from the shared OpenAPI spec
- Follow wave-av/sdks for progress
Rust Coming soon
—
# planned — generated from the shared OpenAPI spec
- Planned via codegen from the shared OpenAPI spec
- Follow wave-av/sdks for progress
Ruby Coming soon
—
# planned — generated from the shared OpenAPI spec
- Planned via codegen from the shared OpenAPI spec
- Follow wave-av/sdks for progress
What you get
Products
One client, every capability — for people and agents alike.
Go, Rust, and Ruby are coming via codegen from the same spec, and a layered, AWS-v3-style per-product split is rolling out so you depend on only the modules you call. Because every WAVE product sits behind one gateway-fronted surface, every new capability — streams, clips, AI, webhooks, MPP — arrives as one more method on the client you already installed, for people and agents alike.
One install, one key.
Pick TypeScript or Python, set your API key, and make your first call. Your autonomous agents pay their own way on the exact same rails.