Transport-Layer HTTP Payload Compression (Gzip / Brotli / Zstd)

Overview

In multi-agent pipelines and MCP server architectures, transmitting multi-turn conversation histories, large AST dumps, or workspace files over plain HTTP generates 100KB to 5MB payloads per API request.

Uncompressed HTTP transfers suffer from:

1. Network Egress Bottlenecks: High data transfer costs and slow uplink speeds on mobile/remote connections.
2. Socket Timeout Failures: Large payload upload times trigger gateway socket drops and HTTP 504 errors.
3. Transport Latency Overhead: Adds 200ms to 1,500ms of pure network transfer time before the LLM provider even begins tokenization.

The Transport-Layer Compression Protocol transparently compresses outgoing HTTP request bodies and incoming response streams using standard gzip, brotli, or zstd headers.

Uncompressed HTTP vs. Gzip Compressed Stream