AI agents in logistics and freight

Freight is a chain of requests between shippers, brokers, carriers, forwarders, terminals and customs: quote this lane, accept this load, where is it now, why is it late, who pays for the damage. The structured parts already move as EDI or through carrier and customs portals. Exceptions, such as a missed appointment, a detention charge or a damage claim, are where the back-and-forth lives, and where agents that can negotiate within set limits would change the most.

Where agents meet today

EDI transaction sets

X12 defines the motor freight messages for tendering, status and invoicing:

X12 set	Name	Direction
204	Motor Carrier Load Tender	Shipper or broker to carrier
990	Response to a Load Tender	Carrier to shipper or broker
214	Transportation Carrier Shipment Status Message	Carrier to shipper or broker
210	Motor Carrier Freight Details and Invoice	Carrier to payer

These messages carry the transaction well. They carry negotiation poorly: a 990 accepts or declines a tender, but a counter-offer on rate or pickup window happens elsewhere. That gap is where an agent exchange fits, ending in an updated 204 or an agreed status the EDI systems can record.

Ocean and customs

In container shipping, the Digital Container Shipping Association publishes an electronic bill of lading standard with open APIs, applicable to original bills and sea waybills. At the Canadian border, carriers and freight forwarders transmit advance commercial information to the Canada Border Services Agency electronically before goods arrive, within time frames that depend on the mode. Importers settle duties through CBSA’s CARM system, where they register in the CARM Client Portal and post financial security to get goods released before payment.

Customs filings are regulated submissions with their own channels. An agent can prepare and check them. It doesn’t replace them.

An exception, step by step

Illustrative: a carrier’s agent reports that a truck will miss its delivery appointment by three hours. The shipper’s agent asks the receiving warehouse’s agent for the next open dock slot, proposes it to the carrier’s agent, and records the new appointment against the shipment. If the change triggers a detention or redelivery charge, the agents record who agreed to it, so the 210 invoice later matches.

Top use cases

Use case	Who talks to whom	Where it starts
Quotes, tenders, tracking and exceptions	Shipper or broker agent and carrier agent	Spot quotes, a declined tender, a late 214
RFQ to purchase order	Buyer agent and carrier or 3PL agent	Lane bids and contract freight
Invoice disputes and collections	Payer agent and carrier agent	A 210 that doesn’t match the rate, or an accessorial nobody approved
Vendor onboarding and KYC	Shipper or broker agent and new carrier agent	Authority, insurance and banking checks before the first load

Cargo loss and damage claims sit inside the first use case: the claim starts as a structured request with deadlines, and a denial or a disputed valuation is a point to hand to people.

Regulatory considerations

This section describes the rules as their regulators publish them, checked on 26 September 2026. This is not legal advice.

United States

• Broker and forwarder financial responsibility (FMCSA). Since 16 January 2026, if a broker’s or freight forwarder’s available financial security falls below $75,000 and is not restored within 7 calendar days, FMCSA suspends its operating authority. An agent that tenders freight to a broker has a reason to check that authority is active at the time of the tender, not only at onboarding.
• Cargo claims (49 CFR Part 370). A claim is a written communication filed with the carrier that identifies the shipment, asserts liability for loss, damage, injury or delay, and claims a specified or determinable amount. The carrier must acknowledge it within 30 days unless it has already paid or declined, and must pay, decline or make a firm settlement offer within 120 days, with a written status update every 60 days after that. Those are clocks an agent-filed claim starts, so both sides need a record of when the claim was received.
• Ocean detention and demurrage billing (Federal Maritime Commission). The FMC’s billing rule took effect on 28 May 2024. It requires specific information on each invoice and a 30-day issuance deadline, and failing either removes the billed party’s obligation to pay. On 20 November 2025 a federal appeals court set aside the section that limited which parties may be billed and upheld the rest, according to the FMC.
• Contracts formed by agents. Under the federal E-SIGN Act, a contract may not be denied legal effect solely because electronic agents were involved in forming it, as long as each agent’s action is legally attributable to the person to be bound.

Canada

• Advance commercial information (CBSA). Carriers and freight forwarders must send advance data electronically before arrival, including house bills for consolidated freight. An agent that books cross-border freight inherits these deadlines through the carrier or forwarder.
• Duties and release (CBSA CARM). Importers register in the CARM Client Portal and post security for release prior to payment.
• Contracts formed by agents. Ontario’s Electronic Commerce Act, 2000 states that a contract may be formed by the interaction of electronic agents. Other provinces have their own electronic commerce statutes, so the governing law of each shipping contract matters.

Personal information in freight is limited, mostly driver and consignee details. Where it appears, federal and provincial privacy law applies as in any other industry.

Where to start

1. Start with status. Let a shipper’s agent ask a carrier’s agent where a load is and get an answer tied to the shipment identifiers the 214 already uses.
2. Add exceptions next. Appointment changes, late pickups and detention questions are high-volume and low-risk to settle by agent, and each outcome can be written back to the EDI record.
3. Keep tenders and invoices on EDI. Let the agents negotiate, then send the agreed result through the 204, 990 and 210 flow the partners already exchange.
4. Set limits in advance. Give each agent explicit ceilings, such as the maximum rate or accessorial it may accept, and a rule for when it must ask a person. Multi-turn tasks shows how an agent can pause for input without losing the thread.
5. Make retries safe and keep receipts. A duplicate tender or a double-paid invoice is expensive. Use idempotent request identifiers and keep a signed record of every agreement so claim and billing clocks can be proven later.