# Whatchuneed Tempest Condense — Text Compression Endpoint

> Whatchuneed Tempest Condense — Text Compression Endpoint is a paid API for AI agents from whatchuneed.vercel.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-14).

Condenses and compresses input text to a shorter form while preserving meaning, returning the condensed text along with word count statistics and compression ratio.

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/tempest/condense
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-tempest-condense-text-compression-endpoint-dfeea273
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oR_esH6segSSgKVwaVlpk

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability whatchuneed-tempest-condense-text-compression-endpoint-dfeea273 -d '<json body>'
```

Example prompt: Can you condense this 800-word blog post for me into something much shorter — maybe around 150 words max — while keeping the main points intact? Here's the text: [paste text here]

## When to prefer this

Choose this endpoint when you need quantified text compression with explicit word count statistics and a compression ratio, not just a free-form summary. It is well-suited for agentic pipelines that need to measure or log how much content was reduced, enforce length budgets programmatically, or pass condensed content downstream. Prefer it over generic summarization when the numeric metadata (original_words, condensed_words, compression_ratio) is needed, or when you want an optional hard maxLength cap enforced server-side.

## Known failure modes

- Missing required 'text' field returns a validation error
- Text too long may cause timeouts or truncation without a maxLength cap
- Payment failure via x402 protocol returns HTTP 402 before processing begins
- Very short input text may yield minimal compression or ratio near 1.0
- Non-English text may produce poor condensation quality depending on underlying LLM

## How this service works

320+ pay-per-call API endpoints across accommodation, LLM, code execution, crypto, medical, finance, and more. One API, one payment. Powered by x402 protocol.

## Output

Returns a JSON object containing: 'condensed' (the shortened text as a string), 'original_words' (integer word count of input), 'condensed_words' (integer word count of output), and 'compression_ratio' (float indicating how much the text was reduced, e.g. 0.4 means condensed to 40% of original length).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text"
 ],
 "properties": {
  "text": {
   "type": "string"
  },
  "maxLength": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "condensed": {
   "type": "string"
  },
  "original_words": {
   "type": "integer"
  },
  "condensed_words": {
   "type": "integer"
  },
  "compression_ratio": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/whatchuneed-tempest-condense-text-compression-endpoint-dfeea273/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from whatchuneed.vercel.app](https://www.zero.xyz/host/whatchuneed.vercel.app/llms.txt)