Document to Verified JSON

Choose this endpoint when you need not just structured data extraction but also source-backed provenance and verifiability — i.e., when downstream consumers must be able to audit where the data came from and confirm it hasn't been tampered with. It is especially valuable in compliance, fact-checking, legal, and multi-agent trust workflows where raw scraping output is insufficient without attestation. Prefer it over generic HTML-to-JSON parsers when chain-of-custody evidence is required.

• Document URL is not publicly accessible — returns an access or fetch error
• Input document format is unrecognized or malformed — normalization fails with a parse error
• Document content is too large or complex to normalize within service constraints
• Network timeout when fetching the source document
• Ambiguous or unsupported schema in input results in partial normalization
• Payment not confirmed via x402 protocol — request rejected before processing