# Document to Verified JSON

> Document to Verified JSON is a paid API for AI agents from phion.systems, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Normalizes public text, HTML, JSON, or XML documents into source-backed, verifiable JSON with provenance tracking

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/document-to-verified-json?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/document-to-verified-json-9b5b17a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6zVtm5Utj7VPErMDonIvm

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 document-to-verified-json-9b5b17a7 -d '<json body>'
```

Example prompt: Take this public HTML page at https://example.com/report.html and normalize it into source-backed JSON — I need the result to include provenance so I can prove where the data came from.

## When to prefer this

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.

## Known failure modes

- 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

## How this service works

Normalize public text, HTML, JSON or XML documents into source-backed JSON

## Output

A normalized JSON object representing the document's structured content, accompanied by source reference metadata, content hashes, and provenance attestation that allows downstream consumers to verify the data's origin and integrity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/document-to-verified-json-9b5b17a7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)