The WAVE Money Engine
One engine gets everyone paid, people and agents, on the same rail. Payments, identity, and compliance run behind every WAVE stream, so value moves as easily as the video does.
18 capabilities, 0 priced
Every one is the same call for a person with a key and an agent with a wallet.
Each chip opens the machine-readable document for that path.
A 402 is the invoice
$ curl -sI https://api.wave.online/v1/x402 HTTP/2 402content-type: application/jsonwww-authenticate: Payment …
Every priced path on WAVE answers an unauthenticated call the same way: 402, terms in the header. Retry with the payment header and the response is the work. Read the OpenAPI document
| Field | Observed |
|---|---|
| Status | 402Payment Required |
| content-type | application/json |
| www-authenticate | Payment … |
| Surface | api.wave.online/v1/x402 |
| Document | Read the OpenAPI document |
Built once, for every party
The engine itself handles verification, settlement, identity, compliance, and metering. People pay with cards and keys; agents pay over HTTP-402. Same rail, same enforcement.
9 the rails4 live · 3 building · 2 planned
| Name | Status | What it solves |
|---|---|---|
| 01x402 facilitator | Live | An HTTP-402 facilitator implements the EIP-3009 “exact” scheme. The payer signs an EIP-712 authorization; the facilitator binds the payer and settles USDC on Base. Live on mainnet. |
| 02On-chain settlement | Live | Sign → verify → settle → replay-rejected: proven end-to-end on Base mainnet with real USDC. Atomic replay protection on every settled credential. |
| 03Agent identity | Live | The platform signs its identity at /.well-known/did.json (did:wave-platform, Ed25519), so an agent can prove who it is before any charge. |
| 04Compliance | Live | OFAC sanctions screening runs on the credential source address, with per-agent spend tiers: money moves inside guardrails, not around them. |
| 05Per-dimension metering | Building | One usage meter covers egress, stream-minutes, frames, samples, and reconnects, so every transport is measured and billed the same way. Deployed; rolling out behind a flag. |
| 06Signed receipts | Building | Every settlement gets a signed, retrievable receipt, verifiable proof of what was paid, for both sides. Deployed; rolling out behind a flag. |
| 07Fiat on/off-ramp | Building | Fiat rails run via Bridge: USD ACH/wire, EUR SEPA, GBP Faster Payments, MXN SPEI, BRL PIX, so a stablecoin rail has a fiat edge on both ends. |
| 08WAVE Account | Planned | A did:wave-keyed account holds a balance, tops up, spends, and pays out across rails, the foundation of the WAVE Wallet. Non-custodial by composition. |
| 09WAVE Wallet | Planned | Every party, creator, viewer, and both their agents, holds a wallet on one rail: the 4-party network that makes micropayments for video native. |
Composed, not locked in
The Money Engine composes the best rails rather than locking you in. WAVE’s own x402, OFAC screening, and replay protection are live today; Stripe, Bridge, and Privy compose in under one did:wave account as the WAVE Account and Wallet land. Open protocol where it earns trust; metered where it earns revenue.