# Receipt Normalizer by PDF Extract API

> Receipt Normalizer by PDF Extract API is a paid API for AI agents from receipt-normalizer.pdfextractapi.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Converts a receipt, invoice, or order confirmation file into a canonical structured purchase record.

## Facts

- Endpoint: POST https://receipt-normalizer.pdfextractapi.workers.dev/normalize
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/receipt-normalizer-by-pdf-extract-api-d79dd32d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Inz8xVtES0Vc-vQ9L-_rZ

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 receipt-normalizer-by-pdf-extract-api-d79dd32d -d '<json body>'
```

Example prompt: Can you normalize this receipt PDF into a structured purchase record so I can see the merchant, line items, totals, and date in a clean format?

## When to prefer this

Choose this endpoint when you need to convert raw receipt, invoice, or order confirmation documents (PDFs, images) into a canonical structured purchase record for downstream processing such as expense management, accounting ingestion, or financial analytics. Prefer this over generic OCR when you specifically need normalized purchase/expense fields rather than raw text extraction.

## Known failure modes

- Unreadable or corrupted file returns an error response
- Non-receipt/invoice documents may produce incomplete or inaccurate structured output
- Handwritten or low-quality scanned receipts may result in missing fields
- Unsupported file formats may be rejected
- Payment failure (x402) results in no processing

## How this service works

Normalize a receipt, invoice, or order confirmation into a canonical structured purchase record.

## Output

A canonical structured purchase record containing normalized fields extracted from the submitted receipt, invoice, or order confirmation — typically including merchant name, transaction date, line items with descriptions and amounts, subtotal, tax, and total amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [
      "file"
     ],
     "properties": {
      "file": {
       "type": "string",
       "format": "binary"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/receipt-normalizer-by-pdf-extract-api-d79dd32d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from receipt-normalizer.pdfextractapi.workers.dev](https://www.zero.xyz/host/receipt-normalizer.pdfextractapi.workers.dev/llms.txt)