# wave OMT

Low-latency, high-quality video over the LAN — OMT sources discovered, routed, and bridged to WAVE.

- This host (omt.wave.online) is a WAVE Protocol Plane spoke: a thin edge front-door.
- The API, auth, scopes, metering, and pay-per-use all live at the gateway: https://api.wave.online
- Errors are JSON: {"error":{"code","message"}}. Authenticate with a wave key or pay via x402.

## Surfaces
- [Landing page](https://omt.wave.online/)
- [Status](https://omt.wave.online/status) — health + dependencies (append ?format=json)
- [Transparency](https://omt.wave.online/transparency) — data + logging policy
- [Health](https://omt.wave.online/health) — liveness probe (JSON)
- [llms.txt](https://omt.wave.online/llms.txt) — this document
- [Structured manifest](https://omt.wave.online/index.json) — index.json
- [Atom feed](https://omt.wave.online/feed.xml) — product updates

## For agents
- [MCP manifest](https://omt.wave.online/.well-known/mcp.json) — tool discovery (server hosted at the gateway)
- [Agent card](https://omt.wave.online/.well-known/agent-card.json) — A2A
- [x402 discovery](https://omt.wave.online/.well-known/x402) — pay-per-use
- [did:web identity](https://omt.wave.online/.well-known/did.json)


## OMT on the gateway
- Routes: the OMT product lives at https://api.wave.online/v1/omt/* (this host forwards /api/* there).
- Scopes (enforced by the WAVE gateway, fail-closed): GET/HEAD need `omt:read`; POST/PUT/PATCH/DELETE need `omt:write`.
- Maturity: preview. The gateway routes and scope-gates /v1/omt/* today; the native OMT transport relay is not yet GA.
- This spoke performs NO auth, scope, or metering itself — all of that is the gateway's job.

[a WAVE product](https://wave.online)