# Invoket Invoice Read — Structured Invoice Parser

> Invoket Invoice Read — Structured Invoice Parser is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Parses a Factur-X/ZUGFeRD PDF or CII D16B/UBL 2.1 XML invoice and returns structured, machine-readable invoice data with provenance.

## Facts

- Endpoint: POST https://api.invoket.com/invoice/read
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-invoice-read-structured-invoice-parser-fef74bff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_POYv8dnRGl_g5U4HAN7fa

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 invoket-invoice-read-structured-invoice-parser-fef74bff -d '<json body>'
```

Example prompt: Parse this Factur-X invoice PDF I'm about to send you and give me the structured data — supplier, buyer, line items, totals, and tax breakdown — so I can verify the amounts before approving payment.

## When to prefer this

Choose this endpoint when you need to programmatically extract structured invoice data from EN 16931 compliant documents (Factur-X/ZUGFeRD PDFs or CII D16B/UBL 2.1 XML files) without OCR. It is ideal for AP automation agents that need to verify invoice amounts before executing payments, ERP ingestion pipelines, or audit workflows requiring provenance. Do not use for scanned invoices, image-based PDFs, or non-standard invoice formats.

## Known failure modes

- Scanned/image-only PDFs without embedded XML return 400 — OCR is not supported
- Documents exceeding 10 MB return 413 (payload too large)
- Malformed or non-EN-16931-compliant XML returns 400
- Non-PDF/non-XML content types without proper Content-Type header may be rejected
- Corrupted base64 encoding returns a parsing error

## How this service works

Read any EU structured e-invoice in one call: post a Factur-X PDF, CII or UBL XML and get faithful structured data - parties with SIREN/VAT identifiers, line items, VAT breakdown, totals, payment IBAN and due dates. Covers the three formats mandated by the French 2026-2027 e-invoicing reform (EN 16931). No account, no key, no OCR guesswork.

## Output

A structured JSON object containing the parsed invoice data extracted from the embedded EN 16931-compliant XML, including supplier and buyer identifiers, invoice number and date, line items with descriptions and quantities, subtotals, tax breakdowns, and grand totals, along with provenance metadata indicating the source format and extraction confidence.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "document_base64"
 ],
 "properties": {
  "document_base64": {
   "type": "string",
   "description": "Base64 (standard alphabet, whitespace tolerated) of the complete document: a Factur-X/ZUGFeRD PDF (PDF/A-3 with embedded XML) or a CII D16B / UBL 2.1 invoice XML. Alternatively, skip JSON entirely and POST the raw bytes with Content-Type: application/pdf or application/xml. Max body 10 MB (413 beyond). Scanned/image PDFs without embedded XML are rejected (400) - this endpoint reads the structured formats of the EN 16931 core, no OCR"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-invoice-read-structured-invoice-parser-fef74bff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.invoket.com](https://www.zero.xyz/host/api.invoket.com/llms.txt)