# Document Validator – Required Fields & Source Evidence Checker

> Document Validator – Required Fields & Source Evidence Checker is a paid API for AI agents from i3p3mgbsn54dvlivnk6wbumal40eqtsn.lambda-url.us-east-1.on.aws, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-10).

Validates invoices, contracts, tenders, and text documents for required fields and source evidence before downstream automation.

## Facts

- Endpoint: POST https://i3p3mgbsn54dvlivnk6wbumal40eqtsn.lambda-url.us-east-1.on.aws/v1/document-validator?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/document-validator-required-fields-source-evidence-checker-33fd7ce5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hx3rW-VNiRnM5WHT3oe0-

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-validator-required-fields-source-evidence-checker-33fd7ce5 -d '<json body>'
```

Example prompt: Can you validate this invoice text to make sure all required fields are present and that there's source evidence for each one before I send it to the payment workflow?

## When to prefer this

Choose this endpoint when you need to gate downstream automation on document completeness — specifically when you need to verify that invoices, contracts, tenders, or other text documents contain all required fields AND that those fields are backed by source evidence. Prefer this over generic extraction endpoints when validation and compliance checking (not just extraction) is the goal, and when you need a structured pass/fail result before triggering payment or workflow automation.

## Known failure modes

- Document text is empty or unparseable — returns error indicating no content to validate
- Unrecognized document type or profile — returns error with supported document types
- Required field list not provided or malformed — validation cannot proceed
- Document too large — may return a payload size error
- Network or Lambda cold-start timeout on large documents

## How this service works

Check invoices, contracts, tenders, and text documents for required fields and source evidence before downstream automation.

## Output

Returns a structured validation report indicating which required fields are present, which are missing, and whether source evidence exists for each field. Includes field-level findings and an overall compliance status indicating whether the document passes validation.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/document-validator-required-fields-source-evidence-checker-33fd7ce5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from i3p3mgbsn54dvlivnk6wbumal40eqtsn.lambda-url.us-east-1.on.aws](https://www.zero.xyz/host/i3p3mgbsn54dvlivnk6wbumal40eqtsn.lambda-url.us-east-1.on.aws/llms.txt)