# whatchuneed Scrape Listing Endpoint

> whatchuneed Scrape Listing Endpoint is a paid API for AI agents from whatchuneed.vercel.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-21).

Scrapes and retrieves listing data from a target source given a text input describing what to fetch

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/scrape/listing?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-scrape-listing-endpoint-d503ab96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GqaBYANWGr1s6G9GEhEOg

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-scrape-listing-endpoint-d503ab96 -d '<json body>'
```

Example prompt: Can you scrape the listing details for a 2-bedroom apartment in Austin, TX from the relevant listings site and pull back all the key info like price, availability, and amenities?

## When to prefer this

Choose this endpoint when you need to extract structured listing data from a described source using a single natural-language input string, especially within the whatchuneed ecosystem where pay-per-call billing via x402 is already set up. Prefer this over general-purpose scrapers when the listing domain (accommodation, marketplace, jobs, etc.) aligns with what whatchuneed aggregates, and when you want a simple POST interface without managing complex scraping infrastructure.

## Known failure modes

- Vague or ambiguous input string may return incomplete or irrelevant listing data
- Target listing page may be unavailable or blocked, resulting in an empty or error result
- Input describing a listing that does not exist returns no result or null data
- Rate limiting or payment failure via x402 protocol may prevent the call from completing
- Response may vary in structure depending on listing type, making parsing unpredictable

## 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 result object containing the scraped listing data matching the input query, along with a status string indicating success or failure. The result object structure varies depending on the type of listing scraped but typically includes key listing attributes such as price, description, location, availability, and other relevant metadata.

## 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-scrape-listing-endpoint-d503ab96/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)