# whatchuneed Crawl Verify

> whatchuneed Crawl Verify 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-20).

Verifies a crawl request or URL against the whatchuneed multi-API gateway

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/crawl/verify?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-crawl-verify-42f5500b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4GlaoYK-PRx2bIB_9DtAt

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-crawl-verify-42f5500b -d '<json body>'
```

Example prompt: Can you verify this input string against the whatchuneed crawl endpoint before I commit to the full API call: 'https://example.com/page-to-crawl'?

## When to prefer this

Use this endpoint when you need to validate or pre-check a crawl request or input string before committing to a more expensive downstream call in the whatchuneed ecosystem. Prefer this over direct API calls when input quality is uncertain or when you want to avoid wasting pay-per-call credits on malformed requests.

## Known failure modes

- Missing or empty 'input' field returns a 400-level error
- Malformed input string that cannot be parsed may return an error status
- Payment failure via x402 protocol prevents endpoint access
- Timeout if the crawl target is unreachable
- Unexpected input type (non-string) may cause schema validation failure

## 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' object containing verification details and a 'status' string indicating whether the input passed or failed validation against the crawl endpoint.

## 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-crawl-verify-42f5500b/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)