# Synthex Forge Invoice OCR

> Synthex Forge Invoice OCR is a paid API for AI agents from x402.synthexforge.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-23).

Extracts structured data from invoice images or PDFs using OCR, returning parsed fields as a signed JSON artifact

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/invoice-ocr?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthex-forge-invoice-ocr-5c34aa52
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2sAzAxvRpzM5EEP-fupUl

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 synthex-forge-invoice-ocr-5c34aa52 -d '<json body>'
```

Example prompt: Can you OCR this invoice image I'm uploading and pull out the vendor name, invoice number, line items, and total amount due?

## When to prefer this

Choose this endpoint when you need a pay-per-call invoice OCR service that returns cryptographically signed, verifiable artifacts (Ed25519 + SHA-256) and settles payment atomically in USDC on Base mainnet via the x402 protocol. Ideal for agents that process invoices on-demand without subscription overhead and need auditability of the extracted data.

## Known failure modes

- Unreadable or low-quality image returns extraction failure or empty fields
- Unsupported file format causes a 400 or processing error
- Payment not settled triggers HTTP 402 with x402 v2 payment-required envelope
- Malformed binary upload returns validation error
- Non-invoice documents may return partially populated or incorrect fields

## How this service works

Synthex Forge x402 Receive: 41 paid verification, attestation and governance endpoints (Ed25519 + SHA-256 signed artifacts) plus free verify/public-key/standard sibling routes. Paid routes answer HTTP 402 with an x402 v2 `payment-required` envelope (atomic USDC on Base mainnet, chain ID 8453). Free routes are declared with `security: []` per the x402scan discovery spec.

## Output

Returns a JSON object with ok: true and extracted invoice fields such as vendor name, invoice number, issue date, due date, line items with descriptions and amounts, subtotal, tax, and total amount due. Fields are signed with Ed25519 and SHA-256 as a verifiable artifact.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "file": {
   "type": "string",
   "format": "binary"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-invoice-ocr-5c34aa52/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.synthexforge.com](https://www.zero.xyz/host/x402.synthexforge.com/llms.txt)