# J-sey Data API – Web Scrape Endpoint

> J-sey Data API – Web Scrape Endpoint is a paid API for AI agents from johncross-data-api.johncrossugwuegede.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14, last successful call 2026-07-17).

Fetches and returns scraped content from a given URL via a pay-per-call GET request billed in USDC

## Facts

- Endpoint: GET https://johncross-data-api.johncrossugwuegede.workers.dev/scrape
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Last successful call: 2026-07-17
- Success rate: 100% of calls made through Zero
- Rating: 4.7 / 5 from 1 review
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/j-sey-data-api-web-scrape-endpoint-4861809a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gimcJl-eOG0JdEAyZkDjG

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 j-sey-data-api-web-scrape-endpoint-4861809a
```

Example prompt: Can you scrape the content of https://example.com/products and return whatever text and HTML you find on that page?

## When to prefer this

Use this endpoint when you need to retrieve live web page content programmatically and are willing to pay micro-USDC per call; useful for agents that need real-time page data without maintaining a browser session, and prefer a simple pay-per-use model over a subscription scraping service.

## Known failure modes

- Target URL is unreachable or returns a non-200 status — scrape fails with an error
- URL is behind a login wall or bot-protection (e.g. Cloudflare) — partial or empty content returned
- Malformed or missing URL parameter — request rejected with a 4xx error
- Payment not settled — 402 Payment Required returned before scrape is attempted
- Rate limiting or timeout on the target server — incomplete content or error response

## How this service works

18-endpoint pay-per-call data API. USDC on 10 EVM networks.

## Output

The agent receives the scraped content of the requested URL, likely as raw HTML or extracted text from the page at the time of the call.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "url"
   ],
   "properties": {
    "url": {
     "type": "string",
     "example": "https://example.com",
     "description": "URL to scrape"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "result": {
     "type": "object",
     "description": "Endpoint response payload"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/j-sey-data-api-web-scrape-endpoint-4861809a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from johncross-data-api.johncrossugwuegede.workers.dev](https://www.zero.xyz/host/johncross-data-api.johncrossugwuegede.workers.dev/llms.txt)