Document extraction built for logistics engineering and operations teams.

Bills of lading, rate confirmations, commercial invoices, airway bills, and every logistics doc your pipeline handles. We've seen it all. Every field is validated, typed, and traced to its source.

80+
Rate-con broker formats prebuilt
JSON
Validated against your schema
Minutes
To configure a new broker format
SOC 2
Type II · audit-ready provenance
rate_confirmations/landstar
landstar_ratecon_sample▾ 100%▾ 1/2
ExtractionValidations 0Errors 0
{ }
Rate Confirmation
L
LANDSTAR
Load Information
Load numberL-7714208
PO / ReferencePO-44912
CarrierApex Truckline LLC (MC# 882104)
Equipment53′ Dry Van
Pickup
ShipperNorthstar Manufacturing
Address2200 Industrial Pkwy, Toledo, OH 43615
Pickup date / time04/18/2025 · 0800–1200
Delivery
ConsigneeHeartland Distribution Center
Address4180 Logistics Blvd, Atlanta, GA 30336
Delivery date / time04/19/2025 · 1400 appointment
Rate Detail
ChargeDescriptionAmount
Line haul724 mi @ $2.61/mi$1,889.64
Fuel surchargeFSC included$215.00
Detention$45/hr after 2 hrsAs accrued
▶ Total all-in rate$2,104.64
1{
2"load_number": "L-7714208",
3"po_reference": "PO-44912",
4"broker": "Landstar",
5"carrier": {
6"name": "Apex Truckline LLC",
7"mc_number": "882104"
8},
9"equipment": "53ft Dry Van",
10"pickup": {
11"shipper": "Northstar Mfg",
12"city": "Toledo, OH",
13"date": "2025-04-18",
14"window": "08:00-12:00"
15},
16"delivery": {
17"consignee": "Heartland Dist",
18"city": "Atlanta, GA",
19"appointment": "14:00"
20},
21"line_haul": {
22"miles": 724,
23"rate_per_mile": 2.61,
24"amount": 1889.64
25},
26"fuel_surcharge": 215.00,
27"total_rate": {
28"value": 2104.64,
29"validated": true
30}
31}

Trusted by teams turning documents into production data

The platform

Sensible turns logistics documents into your data layer.

An API call sends a rate confirmation, bill of lading, invoice, or customs manifest to Sensible. A SenseML config (yours, ours, or built together) defines what to extract. The platform returns structured JSON validated against your schema, with source coordinates per field. Engineers ship extraction in days instead of months. Ops and AP teams stop re-keying. Compliance gets a clean trail.

API & SDKs

REST API with Python and Node SDKs, plus webhook support for async processing.

View the docs →

Off-the-shelf configs

get started in minutes using configs our team has already built for the most common doc types

Browse logistics configs →

Schema & provenance

Type validation, cross-field reconciliation, and source-coordinate trace per field. Every output is auditable.

Managed services

Don't want to own the configs? Sensible's team builds, tests, and maintains extractions for you.

Learn about managed services →
How it works

From document to structured data, in four steps.

The same pipeline whether you're running a single-page rate-con or a 40-page customs packet. Sync or async. Same auth, same schema contract.

Step 01

Send the document

POST a PDF, scan, or fax-image to the extraction endpoint with the SenseML config that matches the broker or carrier format.

POST /v0/extract
config: ratecon-landstar
Step 02

Hybrid pipeline runs

Layout-based rules locate fields. LLM parsing handles ambiguous sections, tables, and prose. SenseML constrains both halves to your schema.

OCR → layout → LLM → type cast
Step 03

Validate every field

Schema enforcement, type checks, cross-field reconciliation, and confidence scoring. Low-confidence fields surface for human review.

schema → types → cross-ref → confidence
Step 04

Deliver to your stack

Validated JSON returns sync or via webhook. Plug into your TMS, freight settlement system, AP automation, customs broker portal, or warehouse.

{ fields: {…}, source_coords: {…} }
Partner with us

We build the extraction layer. You ship product.

Plenty of teams would rather not write document parsers, monitor model drift, or maintain configs across format changes. Sensible's services team can handle all of it.

What you give usSample documents · target schema · target throughput
What you get backA working extraction endpoint, configs in your environment, downstream integrations wired up
PricingSame per-document rate as self-serve. No separate build fees.
01

Custom configs

SenseML for any layout your team handles. Rate-cons, BOLs, niche broker forms, airway bills, delivery orders. Versioned in your environment.

02

Integration delivery

Webhooks, batch jobs, email and EDI intake, downstream mappings into your TMS, freight settlement system, AP automation, or warehouse.

03

Drift & format maintenance

When a broker changes a rate-con layout or a model's behavior shifts, we update the configs. Your pipeline keeps shipping. Engineering team stays on product work.

04

White-glove onboarding

High-volume teams get a dedicated solutions engineer through go-live. Schema design, test coverage on real documents, monitoring and alerting.

Customer story

How Proforma Global expedites customs compliance with Sensible.

Customs compliance moves at the speed of paperwork. Proforma Global routes commercial invoices, customs forms, and shipping manifests through Sensible to ship cleared loads faster, with field-level provenance for audit.

Read the full story →
80+Rate-con broker formats supported
JSONValidated against your TMS schema
MinutesTo configure a new broker format

SOC 2 Type II

Audited annually

HIPAA-ready

Available on Enterprise

Field-level provenance

Every extraction traceable

Per-document pricing

Predictable, no surprises

FAQ

Questions logistics teams ask.

What logistics document types does Sensible support?
Rate confirmations from 80+ brokers, bills of lading, commercial invoices, packing lists, customs manifests, freight invoices, delivery orders, PODs, and shipping invoices. Each ships as a starter config in the logistics library.
How does Sensible handle different broker and carrier formats?
Each broker layout is its own SenseML config. Configs are versioned, testable, and deployable through CI/CD. New broker or carrier formats become new configs without changing your API integration.
Why not just prompt an LLM directly?
LLMs with structured outputs return syntactically valid JSON, but they don't enforce that line-haul totals reconcile, that an FSC is calculated correctly, or that a weight or quantity actually appears on a specific page. Sensible runs deterministic validation on top of the model output and traces every field back to its source coordinates, so a downstream system never gets a hallucinated value.
How does this compare to building extraction in-house?
First version of an in-house build usually works. The cost shows up later: model deprecations, broker format drift, prompt regressions, the audit trail you didn't build, the human-review queue you didn't design. Sensible runs that infrastructure so engineering time stays on your product. SenseML is open and MIT-licensed, so the configs are yours to fork if you ever want to take it back in-house.
Can Sensible handle customs and cross-border documents?
Yes. Customs invoices, certificates of origin, phytosanitary certificates, airway bills, and broker-specific manifests are all supported. Configs ship in the logistics library and can be forked for partner-specific layouts.
How is pricing structured for logistics volumes?
Per-document pricing regardless of page count or complexity. Trials start on the Growth plan for 14 days. View pricing →
Get started

Start extracting logistics documents today.

14-day free trial on the Growth plan. Pre-built logistics configs included. No credit card required.