Agent-native · HTTP-402

An API your agents can pay for and use on their own.

WAVE exposes video as a machine-readable, agent-native API. Autonomous agents discover capabilities, negotiate payment over HTTP-402 (x402), and settle programmatically — no human in the loop required.

Machine-readable surfaces

skill.md

A skill descriptor that tells an agent what WAVE can do and how to call it.

skill.md →

OpenAPI

The full machine-readable contract for the WAVE gateway.

openapi.json →

x402 payment

HTTP-402 payment negotiation: agents discover price terms and settle programmatically.

.well-known/x402 →

Pricing terms

Usage-based, per-product metered terms — published per product behind the gateway.

pricing.json →

llms.txt

A discovery file pointing agents and LLMs at every WAVE surface.

llms.txt →

MCP

Model Context Protocol discovery so MCP clients can wire up WAVE tools.

.well-known/mcp →

How agents transact

Discover

An agent reads skill.md, the OpenAPI spec, and llms.txt to learn WAVE's capabilities and endpoints.

Negotiate

On a paid call, the gateway returns HTTP-402 with x402 payment terms the agent can parse.

Settle

The agent settles via x402 / MPP and retries — payment and access are negotiated machine-to-machine.

Use

The gateway enforces auth, scope, entitlement, and metering centrally; the agent just calls the API.

Products

Wire your agent to WAVE.

Start from the skill descriptor and the OpenAPI spec. Payment is native; the rails are the same for agents and people.