Session-based HTTP CONNECT tunnel gateway. TLS is handled by the platform. Each session pins to one SOCKS5 proxy droplet for the duration of the job.
Usage: call GET /proxy/session to get a session ID, then set
X-Proxy-Session: <id> on each CONNECT request.
{ sessionId, ip }X-Proxy-Session header — routes through pinned droplet SOCKS5