# whatchuneed /api/crawl/broken

> whatchuneed /api/crawl/broken is a paid API for AI agents from whatchuneed.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-22).

Attempts to crawl a broken or invalid endpoint within the whatchuneed multi-API aggregator platform

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/crawl/broken?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-api-crawl-broken-38ddb173
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HZTgpm4rrJUi6asM_7NuQ

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-api-crawl-broken-38ddb173 -d '<json body>'
```

Example prompt: Try to crawl the broken endpoint on whatchuneed and tell me what status or error response comes back when you send a test input string to it.

## When to prefer this

Use this endpoint only when specifically testing or diagnosing the '/api/crawl/broken' route on whatchuneed — not for productive crawling or data retrieval. It is appropriate for QA testing, health monitoring of broken routes, or understanding how the whatchuneed aggregator handles failures.

## Known failure modes

- Endpoint consistently returns an error or empty result because the path is intentionally or structurally broken
- Payment of $0.05 USDC fails, blocking the request
- Input string missing, triggering a 400 validation error
- Platform outage causes 500-level response
- Generic result schema provides no useful diagnostic detail

## 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 any response data from the broken endpoint and a 'status' string indicating the outcome of the crawl attempt; likely returns error or empty data given the path is labelled 'broken'.

## 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-api-crawl-broken-38ddb173/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)