# QuantaFlow Rapid Website Contacts Scraper

> QuantaFlow Rapid Website Contacts Scraper is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-14).

Scrapes contact information (emails, phone numbers, social links) from a given website via a pay-per-call x402 gateway

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-website-contacts-scraper?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-rapid-website-contacts-scraper-65bd09b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k78rV9ptNeVRzZsLi4MaS

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 quantaflow-rapid-website-contacts-scraper-65bd09b9 -d '<json body>'
```

Example prompt: Can you scrape all the contact information — emails, phone numbers, and social links — from acmecorp.com for me?

## When to prefer this

Choose this endpoint when you need to programmatically extract contact details (emails, phones, social links) from one or more websites on a pay-per-use basis without a subscription. It is ideal for ad-hoc lead generation, sales prospecting, or data enrichment workflows where you want to pay only $0.01 USDC per scrape via the x402 micropayment protocol rather than committing to a monthly plan.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted (402 response)
- Target website blocks scraping or returns no contact data
- Invalid or unreachable URL path provided
- Upstream scraper service unavailable or rate-limited
- Empty result if the target page has no extractable contact information
- Malformed query/body parameters causing upstream request failure

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

Returns the upstream scraper's response containing extracted contact data from the target website — typically including email addresses, phone numbers, social media profile URLs, and other contact-related information found on the page, passed through directly after successful x402 micropayment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-rapid-website-contacts-scraper-65bd09b9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)