/v1/responses endpoint with realtime-capable models. The system includes 29 realtime models across multiple providers, a WebSocket vendor layer, and realtime-specific settlement.
How it works
Realtime requests go through the same/v1/responses endpoint as text inference. When the resolved model is a realtime type (e.g., gpt-realtime-2, qwen-omni-turbo-realtime), the engine opens a WebSocket session to the provider, streams audio/text bidirectionally, and meters the result with realtime-specific billing.
Realtime models
Use
GET /v1/models?type=realtime or GET /v1/models/search?type=realtime to list all realtime models.
Appending input to a live session
For ongoing realtime sessions, append audio or text without starting a new response:Settlement
Realtime sessions are settled like any other inference call — the metering system extracts audio duration, token counts, and session metrics from the provider’s usage format, then settles via x402. The receipt includes per-modality token breakdowns (input_audio_tokens, output_audio_tokens).Related
- Streaming — SSE streaming for text and media
- Modalities — All supported modality types
- Speech models — TTS and STT provider details
- SDK: Inference — TypeScript API for inference