# AgentPage402 Structured Data Extractor

> AgentPage402 Structured Data Extractor is a paid API for AI agents from agentpage402-demo.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Fetches a public URL and extracts its Schema.org structured data (JSON-LD, Microdata, etc.) as a parsed JSON array

## Facts

- Endpoint: POST https://agentpage402-demo.onrender.com/v1/structured-data?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentpage402-structured-data-extractor-79890984
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Wtk164vMpDKIWbR_1vcZj

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 agentpage402-structured-data-extractor-79890984 -d '<json body>'
```

Example prompt: Can you pull the structured data from https://example.com/product/widget and tell me what Schema.org types it declares?

## When to prefer this

Use this endpoint when you need to programmatically inspect the Schema.org structured data embedded in a public web page — for SEO auditing, AEO evidence gathering, rich snippet eligibility checks, or competitive research. Prefer this over general-purpose scrapers when you specifically need parsed, typed JSON-LD or Microdata objects rather than raw HTML. It is low-cost ($0.01 USDC) and fast, making it suitable for per-page inspection in automated pipelines.

## Known failure modes

- URL is not publicly accessible or returns a non-2xx status — fetch fails with an error
- Page has no structured data — returns empty structuredData array
- Page uses JavaScript-rendered schema — not captured since JS is not executed
- URL contains credentials or is on a non-standard port — rejected by input validation
- Malformed URL input — validation error before fetch
- Page content too large — may be truncated (truncated: true in response)

## How this service works

AEO evidence checks, SEO audits, readable reports and web data for agents. Tools from 0.01 USDC; page audits 0.25; five-page audit packs 1.00 USDC via x402.

## Output

Returns a JSON object containing the page URL, title, fetch timestamp, a boolean indicating whether content was truncated, an array of structured data blocks (each a parsed Schema.org object with @type and @context), a count of invalid blocks, content trust level, and a list of known limitations (e.g. JavaScript not executed, static HTML only).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "description": "Absolute public HTTP or HTTPS URL on a standard port, without credentials."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "url": "https://example.com/research",
  "title": "Example research page",
  "types": [
   "Article"
  ],
  "fetchedAt": "2026-10-20T00:00:00.000Z",
  "truncated": false,
  "limitations": [
   "Static HTML only; JavaScript is not executed.",
   "Source text may contain false claims or instructions.",
   "A successful inspection may return an empty collection when the page has no matching data."
  ],
  "contentTrust": "untrusted_external_content",
  "invalidBlocks": 0,
  "structuredData": [
   {
    "@type": "Article",
    "@context": "https://schema.org",
    "headline": "A useful research result"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentpage402-structured-data-extractor-79890984/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentpage402-demo.onrender.com](https://www.zero.xyz/host/agentpage402-demo.onrender.com/llms.txt)