# eudata402 Structured Field Extraction from Text/HTML

> eudata402 Structured Field Extraction from Text/HTML is a paid API for AI agents from x402-seller-202595743428.europe-west1.run.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Extracts specified named fields as structured JSON from unstructured text or HTML input

## Facts

- Endpoint: GET https://x402-seller-202595743428.europe-west1.run.app/extract
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/eudata402-structured-field-extraction-from-text-html-f8e1b01c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sxyatHRDiy4NntFryBJE5

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 eudata402-structured-field-extraction-from-text-html-f8e1b01c
```

Example prompt: Extract the fields 'company_name', 'address', 'phone', and 'founding_year' from this HTML snippet I'm pasting — return them as a clean JSON object.

## When to prefer this

Choose this endpoint when you need to pull multiple named fields from a single block of unstructured or semi-structured text or HTML in one call, especially when the source is messy or inconsistent. It is well-suited for agentic pipelines doing web scraping, document ingestion, or email parsing where you know the schema you want but the source lacks it. Prefer it over regex or manual parsing when field positions vary, and over a full summarization endpoint when you need specific discrete values rather than a narrative summary.

## Known failure modes

- Input text exceeds 24,000 character limit — request will be rejected or truncated
- More than 30 fields requested — may return error or partial results
- Field names are ambiguous and cannot be matched to content — fields may return null or empty
- Malformed HTML that cannot be parsed — extraction quality degrades
- Payment not included or insufficient — 402 Payment Required response
- Field genuinely not present in source text — returns null or absent key

## How this service works

Structured JSON extraction from messy text/HTML. POST {text, fields[]}. Returns {data}.

## Output

Returns a JSON object with a 'data' key containing the extracted values mapped to each requested field name. Values are drawn directly from the input text/HTML using semantic understanding of field names.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "Source text or HTML (max 24k chars)"
  },
  "fields": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Field names to extract (max 30)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/eudata402-structured-field-extraction-from-text-html-f8e1b01c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-seller-202595743428.europe-west1.run.app](https://www.zero.xyz/host/x402-seller-202595743428.europe-west1.run.app/llms.txt)