Back to Browse
Compression Algorithm Comparison (gzip vs brotli vs deflate)
x402
Compression Algorithm Comparison (gzip vs brotli vs deflate) is a paid API for AI agents from agent402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).
Runs input content through gzip, brotli, and raw deflate at maximum compression settings and returns the output size and compression ratio for each algorithm.
Price / call$0.001
Success—
StatusUnknown
How this service works
Run the same input through gzip, brotli, and raw deflate at max settings and report each one's output size and ratio. Use this to decide which algorithm to actually use - the answer depends on your content (binary often resists compression entirely; English prose squeezes well with brotli; JSON sits in between).
Output
Returns the compressed output size in bytes and the compression ratio for each of the three algorithms (gzip, brotli, raw deflate), allowing comparison to determine which algorithm is most effective for the given input content.
Example use cases
Example prompt
“I want to pick the best compression algorithm for my API response payload — can you run this JSON string through gzip, brotli, and deflate at max settings and tell me the output size and ratio for each: '{"users":[{"id":1,"name":"Alice"},{"id":2,"name":"Bob"}]}'?”
Technical details
Endpoint
POSThttps://agent402.tools/api/compress-compareWhen to prefer
Use this endpoint when you need to make an informed decision about which compression algorithm to deploy for a specific content type. It is especially valuable before committing to a compression strategy in production, since optimal algorithm choice is highly content-dependent (text compresses well, binary often does not). Prefer this over running individual compression endpoints when you want a side-by-side comparison in a single call.
Side effects
- Input exceeds 10MB limit after decoding — request rejected
- Invalid inputFormat value (must be utf8, base64, or hex) — bad request error
- Malformed base64 or hex encoding when non-utf8 format is specified
- Payment not provided or insufficient — 402 Payment Required
- Empty input string — may return trivial results or error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| input | string | Content to test (max 10MB after decoding) |
| inputFormat | string | How `input` is encoded: utf8 (default), base64, or hex |
Output
Schema · Response
{
"type": "json",
"example": {
"best": "brotli",
"results": [
{
"ratio": 0.6782,
"algorithm": "brotli",
"outputBytes": 28
},
{
"ratio": 0.5287,
"algorithm": "gzip",
"outputBytes": 41
},
{
"ratio": 0.6667,
"algorithm": "deflate",
"outputBytes": 29
}
],
"inputBytes": 87
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"