# Synthex Forge Invoice Extract

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

Extracts structured invoice data from raw text input, returning parsed invoice fields as a signed artifact

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/utils/invoice-extract?utm_source=zero.xyz
- Price: $0.1/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-extract-5e23bdf0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__KNttW2VtxEKnKplu50cQ

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-extract-5e23bdf0 -d '<json body>'
```

Example prompt: Can you extract the structured invoice data from this text: 'Invoice #INV-2024-0042, Date: June 1 2024, Vendor: Acme Corp, Total: $1,250.00, Due: June 30 2024, Line items: 5 units widget A at $250 each'?

## When to prefer this

Choose this endpoint when you need cryptographically attested invoice extraction — the Ed25519+SHA-256 signed output makes results verifiable and audit-ready. Prefer it over generic LLM extraction when downstream systems require tamper-evident proof of the extracted data, or when operating in a compliance or governance context. Best suited for automating accounts payable, reconciliation pipelines, or document digitization workflows that require structured, trusted invoice data from free-form text.

## Known failure modes

- Empty or missing text field returns an error
- Malformed or non-invoice text may yield incomplete extractions with missing fields
- Payment of 0.1 USDC on Base mainnet (chain ID 8453) required; unpaid requests receive HTTP 402 with x402 v2 payment-required envelope
- Text that is too long or contains unsupported encoding may fail processing
- Network or blockchain payment confirmation delays may cause timeouts

## 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 parsed from the input text, signed as an Ed25519 + SHA-256 artifact per the Synthex Forge attestation standard. Fields typically include invoice number, date, vendor, buyer, line items, totals, and payment terms where present in the source text.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string"
  }
 }
}
```

## 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-extract-5e23bdf0/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)