# Fracht Bill-of-Lading & Air-Waybill Reference Parser

> Fracht Bill-of-Lading & Air-Waybill Reference Parser is a paid API for AI agents from fracht.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Parses and separates structured components from bill-of-lading (BL) or air-waybill (AWB) reference strings, returning null for missing fields and disclosing derivation methods for inferred values.

## Facts

- Endpoint: POST https://fracht.halowerk.com/v1/bl-parse
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fracht-bill-of-lading-air-waybill-reference-parser-f929bec3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N_-GCRodSVcGjqo0XZEcp

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 fracht-bill-of-lading-air-waybill-reference-parser-f929bec3 -d '<json body>'
```

Example prompt: Can you parse this bill of lading reference for me — MAEU123456789 — and break out all the components like carrier, serial number, and check digit? Auto-detect whether it's a BL or AWB.

## When to prefer this

Use this endpoint when you need to programmatically decompose a raw BL or AWB reference string into structured fields, especially when the document type is uncertain and auto-detection is needed. Prefer it over generic regex parsing when transparency about derivation method and missing-field disclosure is important for downstream logistics workflows.

## Known failure modes

- Reference string too short (below 3 characters) or too long (above 100 characters) — validation error
- Unrecognized or malformed reference format — components returned as null with all fields in unavailable_fields
- Ambiguous reference when kind=auto cannot determine document type — type field may be null
- Empty or missing reference field — request rejected with schema validation error

## How this service works

Separates common bill-of-lading and air-waybill reference components. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

A structured breakdown of the reference string into its recognized components (e.g. carrier prefix, serial number, check digit, document type), with null values and an unavailable_fields list for anything that could not be resolved, plus disclosure of derivation method and source/time-window metadata for inferred or source-backed values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "kind": {
   "enum": [
    "auto",
    "bl",
    "awb"
   ],
   "type": "string"
  },
  "reference": {
   "type": "string",
   "maxLength": 100,
   "minLength": 3,
   "description": ""
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fracht-bill-of-lading-air-waybill-reference-parser-f929bec3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fracht.halowerk.com](https://www.zero.xyz/host/fracht.halowerk.com/llms.txt)