# whatchuneed Tempest Dispatch

> whatchuneed Tempest Dispatch 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-13).

Routes a natural-language request to one of 320+ specialized API endpoints covering accommodation, LLMs, code execution, crypto, medical, finance, and more via a single pay-per-call interface

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/tempest/dispatch
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-tempest-dispatch-62bfb03d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sL8-FIvLV4MlJQv8Hy_vx

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-dispatch-62bfb03d -d '<json body>'
```

Example prompt: Find me a hotel in Paris for 2 adults checking in July 10 and checking out July 14, budget around $150 per night — send that request through whatchuneed's dispatch endpoint.

## When to prefer this

Choose this endpoint when you need a single unified gateway to dozens of specialized APIs without managing separate credentials or integrations — especially useful for agents that need to switch across domains (hotel booking, crypto data, code execution, medical lookups) within a single workflow and want pay-per-call pricing with no subscription overhead.

## Known failure modes

- Ambiguous or malformed input string may route to the wrong underlying endpoint
- Rate limiting or payment failures via x402 protocol may cause request rejection
- Upstream provider outages for the specific sub-service being dispatched can return errors
- Unsupported request types not covered by the 320+ endpoints will fail with an error status
- Network timeouts if the underlying provider is slow to respond

## 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 response data from the underlying specialized endpoint that was dispatched to, along with a 'status' string indicating success or failure.

## 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-dispatch-62bfb03d/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)