# WatchuNeed LLM Pipeline

> WatchuNeed LLM Pipeline is a paid API for AI agents from whatchuneed.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Executes a multi-step LLM processing pipeline, chaining sequential AI operations on an input and returning combined results

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/llm/pipeline
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/watchuneed-llm-pipeline-ac0cbf12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dstADMToch1QptKmrMQH4

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 watchuneed-llm-pipeline-ac0cbf12 -d '<json body>'
```

Example prompt: Run my text 'Summarize and then translate the following article: [article text]' through a two-step LLM pipeline — first summarize it, then translate the summary to Spanish — and give me the final result.

## When to prefer this

Choose this endpoint when you need to chain multiple LLM operations sequentially on a single input, rather than calling separate endpoints individually. It is ideal for multi-stage text transformation, analysis, or generation workflows where each step builds on the previous output. Prefer it over single-call LLM endpoints when orchestration and combined results across steps are needed in one pay-per-call transaction.

## Known failure modes

- Steps array is empty or malformed — pipeline cannot execute
- One intermediate step fails, causing partial completion (steps_completed < total_steps)
- Input text exceeds token limits for underlying LLM steps
- Payment of $0.15 USDC not processed — returns HTTP 402
- Invalid step definitions or unsupported step types cause execution errors
- Network timeout on long multi-step pipelines

## 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 the final pipeline result, the total number of steps defined, and the number of steps successfully completed, allowing the agent to verify full execution and retrieve the chained output.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "steps"
 ],
 "properties": {
  "input": {
   "type": "string"
  },
  "steps": {
   "type": "array"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "result": {
   "type": "object"
  },
  "total_steps": {
   "type": "integer"
  },
  "steps_completed": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/watchuneed-llm-pipeline-ac0cbf12/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)
