# whatchuneed Scrape Group Endpoint

> whatchuneed Scrape Group Endpoint 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-14).

Scrapes and aggregates content from a group of web sources based on a natural-language input string, returning structured result data

## Facts

- Endpoint: POST https://whatchuneed.vercel.app/api/scrape/group
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whatchuneed-scrape-group-endpoint-229d3183
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T9UJJvP0T9XI4kYs3GUzF

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-group-endpoint-229d3183 -d '<json body>'
```

Example prompt: Can you scrape and group together the latest accommodation listings for budget hotels in New York City and give me the results in a structured format?

## When to prefer this

Choose this endpoint when you need to scrape and aggregate content from a named group or category of web sources in a single pay-per-call operation, especially when you want grouped/categorized results rather than scraping individual URLs one at a time. It is well-suited for agents needing multi-source aggregation across domains like accommodation, crypto, finance, or medical without managing individual scraping logic.

## Known failure modes

- Vague or ambiguous input string returns empty or irrelevant results
- Target websites block or rate-limit the scraper, returning partial data
- Status field indicates failure if the group query cannot be resolved
- Unstructured or highly dynamic web pages may produce malformed result objects
- Payment of $0.15 USDC not fulfilled causes 402 rejection before scraping begins

## 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 aggregated scraped data from the group query, and a 'status' field indicating success or failure of the scraping operation.

## 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-group-endpoint-229d3183/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)