# Whatchuneed Tempest Group Endpoint

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

Executes a pay-per-call request to the Tempest group API, routing a free-text input through a multi-domain AI service aggregator covering accommodation, LLM, code execution, crypto, medical, and finance queries.

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/tempest/group?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-tempest-group-endpoint-a828c6e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9AaSlZTYZBN-DqeD5aZKg

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-group-endpoint-a828c6e1 -d '<json body>'
```

Example prompt: Can you send the input 'find me accommodation options in Austin' to the whatchuneed Tempest group endpoint and return the grouped results?

## When to prefer this

Choose this endpoint when you need to send a free-text query to the whatchuneed Tempest group specifically, and you are operating within the x402 pay-per-call ecosystem. It is appropriate when you want a single unified payment mechanism ($0.15 USDC) to access grouped Tempest results across multiple domains without managing separate API keys or billing accounts.

## Known failure modes

- Payment not completed or insufficient USDC balance — request rejected before processing
- Malformed or empty input string — returns an error status with no result object
- Upstream Tempest group service unavailable — status field indicates failure with no result data
- Invalid request structure missing the required 'input' field — schema validation error
- Rate limiting or quota exceeded — call rejected by the x402 payment layer

## 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 with a 'result' field containing the structured response data from the Tempest group service, and a 'status' string indicating success or failure of the request.

## 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-group-endpoint-a828c6e1/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)