# Web Page Structured Data Extractor

> Web Page Structured Data Extractor is a paid API for AI agents from x402-seller-0ay3.onrender.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Fetches a public web page, extracts its readable content, and returns structured JSON fields defined by a caller-provided JSON Schema, powered by Claude Haiku 4.5

## Facts

- Endpoint: POST https://x402-seller-0ay3.onrender.com/api/web/extract
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-page-structured-data-extractor-5c404d8d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_U9nCiZxV27kf6WViZinGp

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 web-page-structured-data-extractor-5c404d8d -d '<json body>'
```

Example prompt: Go to https://en.wikipedia.org/wiki/HTTP_402 and extract the page title, the first paragraph, and a list of any related status codes mentioned — return it as structured JSON.

## When to prefer this

Choose this endpoint when you need to fetch a specific public web page AND extract structured, schema-defined fields from it in a single API call. It is ideal when you know exactly which fields you want (product name, price, author, etc.) and want them returned as clean JSON without writing a custom parser. Prefer this over a plain page-reader endpoint when structured extraction is the goal, and over a generic LLM prompt when you want schema-enforced output. Not suited for JavaScript-heavy SPAs, login-gated pages, or full-site crawls.

## Known failure modes

- URL is not publicly accessible or returns a non-200 status — extraction fails with an error
- Page content exceeds 8000 characters and gets truncated, potentially missing fields near the end
- Requested fields in the JSON Schema are not present or ambiguous on the page — fields may return null or empty
- Page is JavaScript-rendered (SPA) and readability extraction returns minimal content
- Malformed JSON Schema provided — may cause extraction errors or unexpected output
- Rate limiting or blocking by the target website returns no content

## How this service works

Read a public web page and extract structured data from it according to a JSON Schema you provide, via Claude Haiku 4.5 — combines page fetching, readability extraction, and structured extraction in one call. Body: {url: string (http/https), schema: object (JSON Schema describing the fields to extract, page content truncated to 8000 chars)}.

## Output

A JSON object containing the URL that was fetched, a `data` field holding the extracted fields matching the caller-provided JSON Schema, the page title, and a `fetched_at` ISO timestamp indicating when the page was retrieved.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Public http(s) URL of the page to read and extract from."
  },
  "schema": {
   "type": "object",
   "description": "JSON Schema describing the fields to extract."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "url": "https://en.wikipedia.org/wiki/HTTP_402",
  "data": {
   "title": "HTTP 402",
   "first_paragraph": "The HTTP 402 Payment Required..."
  },
  "title": "HTTP 402",
  "fetched_at": "2026-09-01T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/web-page-structured-data-extractor-5c404d8d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-seller-0ay3.onrender.com](https://www.zero.xyz/host/x402-seller-0ay3.onrender.com/llms.txt)