# SuVerse Freight — Fuel Receipt Parser

> SuVerse Freight — Fuel Receipt Parser is a paid API for AI agents from api.suverse.io, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Extracts structured data from fuel receipts submitted as text, PDF, or image, returning parsed fields useful for freight accounting and IFTA reporting.

## Facts

- Endpoint: POST https://api.suverse.io/v1/freight/parse_fuel_receipt
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/suverse-freight-fuel-receipt-parser-41fa4e2a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Csi-TeCcFYz1rUAQ9samg

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 suverse-freight-fuel-receipt-parser-41fa4e2a -d '<json body>'
```

Example prompt: I've got a diesel fuel receipt from a Flying J stop — here's the image encoded in base64. Can you parse it and pull out the gallons, price per gallon, total cost, date, and location using OCR mode?

## When to prefer this

Choose this endpoint when you need to digitize and structure fuel receipts specifically in a freight/trucking context, especially when inputs arrive in mixed formats (scanned images, PDFs, or pasted text). It is purpose-built for freight fuel receipts and IFTA/expense use cases, making it more reliable than generic document OCR for this domain. Prefer it over generic OCR APIs when field-level accuracy for gallons, fuel type, and vendor location is critical.

## Known failure modes

- Low-quality or blurry image input may result in incomplete or inaccurate OCR extraction
- Unrecognized receipt formats may yield missing or null fields
- Invalid base64 encoding returns a parsing or input validation error
- Text input that is not a fuel receipt returns empty or irrelevant fields
- Mode mismatch (e.g., sending pdf_base64 but specifying text mode) may cause degraded results

## How this service works

SuVerse Freight — fuel receipt parser (freight.parse_fuel_receipt)

## Output

Returns a structured JSON object containing extracted fuel receipt fields such as vendor name, station location, transaction date and time, fuel type, gallons purchased, price per gallon, total amount, and any available truck or driver identifiers — ready for use in accounting, IFTA reporting, or expense management systems.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "auto",
    "text",
    "llm",
    "ocr"
   ],
   "type": "string"
  },
  "text": {
   "type": "string"
  },
  "pdf_base64": {
   "type": "string"
  },
  "image_base64": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/suverse-freight-fuel-receipt-parser-41fa4e2a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.suverse.io](https://www.zero.xyz/host/api.suverse.io/llms.txt)