# SuVerse Freight BOL/POD Parser

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

Extracts structured data from Bill of Lading (BOL) and Proof of Delivery (POD) freight documents provided as text or base64-encoded PDF

## Facts

- Endpoint: POST https://api.suverse.io/v1/freight/parse_bol_pod
- Price: $0.15/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-bol-pod-parser-fc701a90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LVT8LjJgBrQBLQLwtlmNr

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-bol-pod-parser-fc701a90 -d '<json body>'
```

Example prompt: I just received a BOL from my carrier — can you parse this PDF and extract all the shipment details like shipper, consignee, commodity, and freight charges? Here's the document as a base64-encoded PDF.

## When to prefer this

Choose this endpoint when you need to automatically extract structured data from Bill of Lading or Proof of Delivery documents in freight logistics workflows. It is ideal for TMS integrations, carrier invoice reconciliation, delivery dispute resolution, and back-office automation where manual data entry from paper or PDF freight documents is a bottleneck. It complements other SuVerse freight parsers for rate confirmations and fuel receipts when building a complete freight document automation pipeline.

## Known failure modes

- Unreadable or low-quality PDF scans may result in incomplete or inaccurate field extraction
- Documents that are not BOL or POD type may return empty or irrelevant fields
- Malformed base64 input will cause a parsing error
- Non-standard or proprietary BOL formats from obscure carriers may reduce extraction accuracy
- Missing required fields (neither text nor pdf_base64 provided) will return a validation error

## How this service works

SuVerse Freight — BOL/POD parser (freight.parse_bol_pod)

## Output

A structured JSON object containing extracted fields from the BOL or POD document, including shipper and consignee details, commodity descriptions, weight and freight charges, reference numbers, delivery dates, and any noted exceptions or signatures present in the document.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/suverse-freight-bol-pod-parser-fc701a90/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)