VercelEngineering PostOfficial Source
WebSocket support for OpenAI Responses API live on AI Gateway
Vercel’s gateway now supports persistent WebSocket sessions for the Responses API, reducing repeated context transfer during long, tool-heavy agent runs.
Vercel · Jul 27, 2026
Source Summary
AI Gateway now exposes the OpenAI Responses API over **WebSocket** at GET /v1/responses. Each new turn can send fresh input plus **previous_response_id** instead of resubmitting the full context over HTTP.
Practical Implication
Consider the persistent route for long coding-agent loops where connection and context overhead accumulate. OpenAI reports **up to about 40% faster** end-to-end execution for rollouts with at least 20 tool calls.
Agent-Ready Context
AI Gateway now exposes the OpenAI Responses API over **WebSocket** at GET /v1/responses. Each new turn can send fresh input plus **previous_response_id** instead of resubmitting the full context over HTTP. Consider the persistent route for long coding-agent loops where connection and context overhead accumulate. OpenAI reports **up to about 40% faster** end-to-end execution for rollouts with at least 20 tool calls. That performance figure applies to a specific tool-heavy workload, not every interaction. The route accepts raw response.create frames and supports **store=false and Zero Data Retention**, so clients must manage the socket and event protocol.
Context Map
infracoding#gateways#agent-reliabilityUncertainty
That performance figure applies to a specific tool-heavy workload, not every interaction. The route accepts raw response.create frames and supports **store=false and Zero Data Retention**, so clients must manage the socket and event protocol.