FAXP
AI Freight Booking
AI Freight Booking with FAXP: an open protocol for AI freight broker workflows, freight AI agents, and agent-to-agent freight booking interoperability.
AI Freight Booking needs a shared protocol layer. Without one, brokers, carriers, shippers, and software vendors rely on one-off integrations that slow automation and increase operational risk.
FAXP provides an open, vendor-neutral booking-plane protocol so AI Freight Agents can interoperate across systems with signed, validated, replay-protected messages.
What AI Freight Booking Means in Practice
AI Freight Booking is the machine-to-machine process of:
- Discovering compatible counterparties and opportunities.
- Exchanging bids and booking terms.
- Transporting optional verifier evidence for trust policy decisions.
- Confirming the booking with an auditable receipt.
Discover -> Bid -> Verify -> Confirm
AI Trucking Agents
AI trucking agents need consistent booking messages to evaluate loads, respond with rates, and confirm commitments without manual re-keying. FAXP standardizes this exchange across participating systems.
AI Freight Broker Workflows
AI freight broker workflows use FAXP to publish opportunities, negotiate terms, apply trust-policy checks, and issue booking confirmations with clear protocol semantics. The protocol focuses on booking interoperability while broker operations continue in existing TMS workflows.
Freight Broker AI Software
Freight broker AI software can implement FAXP to reduce custom integration work across TMS and load board environments. A shared protocol contract lowers maintenance overhead and improves cross-platform interoperability.
Freight AI Agents and Logistics AI Agents
Freight AI agents and logistics AI agents can use the same booking-plane contract to coordinate commercial decisions across broker, carrier, and shipper contexts. FAXP enables role-aware booking communication without requiring a single centralized marketplace.
Agent-to-Agent Freight Booking
FAXP is designed for agent-to-agent freight booking with signed, validated messages and explicit scope boundaries. It standardizes booking communication without taking over dispatch execution, document custody, or settlement rails.
Why Existing Workflows Break
- Mismatched TMS and load board interfaces force re-keying and manual follow-up.
- Proprietary APIs create lock-in and block cross-platform orchestration.
- Capability and trust signals are inconsistent across vendors.
How FAXP Supports AI Freight Booking
- Standardized envelope and message semantics for booking-plane events.
- Clear scope boundary: booking interoperability, not dispatch execution or settlement.
- Verifier-neutral evidence transport model.
- Conformance and governance posture designed for multi-implementation interoperability.
Where to Start
- Review the Protocol Spec.
- Explore implementation direction in the Roadmap.
- Join contributors on GitHub.