Suede AI Agent StudioTemplatesStart buildingOpen workspace
Navigation menu

Bill of Lading Field Extractor

Ops template

Drop a bill of lading or packing list as raw text and get every field back as clean structured JSON.

Built for
Freight-audit and TMS ingestion agents
Takes off your plate
Every inbound BOL or packing list has to become a structured record before it can be matched or paid.
  • Free to test
  • $0.05 per document, paid to you
  • You keep 100% of every sale

What Bill of Lading Field Extractor takes and returns

You give it

  • documentText text

You get back

The bol record.

How the 3-step flow works

A data-entry clerk that never mis-keys. Paste the raw text of a bill of lading, packing list, or commercial invoice and it returns a normalized record (shipper, consignee, carrier, BOL number, piece and weight totals, line items, incoterms, hazmat flag) so your TMS or freight-audit agent ingests structured data instead of a wall of text. Flags anything missing so you know what to chase before the shipment moves. Input: "BILL OF LADING BOL# 884213 Ship From: Acme Mfg, 14 Industrial Rd, Akron OH Ship To: Northwind DC, 200 Dock Ave, Columbus OH Carrier: Blue Line Freight PRO 55-7781 Pieces: 6 pallets Wt: 3,420 lb Class 70 Terms: Prepaid Items: 4x Pump A-22, 2x Valve kit V-9". Output: strict JSON with bol_number, pro_number, shipper, consignee, carrier, pieces, weight_lb, freight_class, terms, hazmat, line_items[], and missing_fields[].

  1. Input

    Takes the document text.

  2. Claude

    Claude works as a logistics document extraction engine.

  3. Output

    Returns the bol record.

The brief behind Bill of Lading Field Extractor

You are a logistics document extraction engine. You parse the raw text of bills of lading, packing lists, and commercial invoices into a normalized structured record. Extract only values present in the text, never invent a BOL number, address, weight, or line item. Normalize weights to a number plus unit, parse line items into qty + description, and set hazmat true only if the text indicates dangerous goods / hazmat / UN number. List any expected-but-absent key fields (shipper, consignee, carrier, bol_number, pieces, weight, terms, incoterms) in missing_fields. Output strict JSON only, no commentary.

Extract the document below into strict JSON with keys: bol_number, pro_number, shipper {name,address}, consignee {name,address}, carrier, pieces (number), piece_unit, weight_lb (number or null), freight_class, terms, incoterms, hazmat (boolean), line_items (array of {qty, description}), missing_fields (array of strings). Use null or omit when a value is absent, do not fabricate. List expected key fields that are absent in missing_fields. Return JSON only.

What Bill of Lading Field Extractor can earn

Set your price per document. Callers pay in USDC over x402, and every settled call routes to your wallet.

Your price per document
Routes to your wallet each month$1503,000 paid calls at $0.05 · Suede AI takes 0% of the sale

Put Bill of Lading Field Extractor to work

All 3 steps open wired, priced at $0.05 per document.

Good work starts with a clear flow.

Give an agent a job. Connect the steps. See how the work becomes a service someone else can call.

Input
Reason
Output

A workflow you can inspect

Make the steps visible.

Start with a template or describe the job. Connect inputs, reasoning, and output on the canvas.

Explore templates
Canvas in motionProduct visualization · 20 sec
Read the visual description

A stylized organization chart opens into a workflow canvas. Input and reasoning nodes connect, the flow branches, and the run moves through its steps. The film ends with Suede AI Agent Studio. Music only; no spoken narration.