# Whatchuneed Tempest Clarify

> Whatchuneed Tempest Clarify is a paid API for AI agents from whatchuneed.vercel.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-20).

Clarifies or refines an ambiguous user input request by returning a structured response via the Tempest clarification endpoint

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/tempest/clarify?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-tempest-clarify-8630658f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8F5I3PxMKuo2EG3kM9A0K

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-clarify-8630658f -d '<json body>'
```

Example prompt: Can you clarify what the user meant by 'I need something for my trip' — run it through Tempest Clarify and give me the structured interpretation so I know how to proceed?

## When to prefer this

Use this endpoint when a user's request is ambiguous or underspecified and you need a structured interpretation before routing to a downstream action. Prefer this over attempting to guess intent directly, especially when the cost of misinterpretation is high. It is particularly useful as a pre-processing step in agentic pipelines where user intent must be confirmed before executing irreversible or paid actions.

## Known failure modes

- Empty or missing 'input' field returns a validation error
- Overly long or malformed input string may cause a processing error
- Ambiguous inputs with no resolvable meaning may return a low-confidence or null result
- Network or payment (x402) failure may result in a 402 or 5xx error
- Input in an unsupported language may not be correctly clarified

## 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

A result object containing a structured clarification of the input request, along with a status string indicating success or failure. The result field contains the interpreted or disambiguated form of the original input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Request input"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "result": {
   "type": "object",
   "description": "Response data"
  },
  "status": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/whatchuneed-tempest-clarify-8630658f/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)