FAXP | Freight Agent eXchange Protocol

Why FAXP Exists

Freight teams still lose hours to mismatched formats, re-keying, and manual handoffs. FAXP gives builders a neutral message envelope and interoperable capability model so agent-to-agent booking workflows can run across systems without custom one-off integrations.

Protocol Boundary

What FAXP Is

FAXP is an open, vendor-neutral agent-to-agent freight booking protocol that standardizes discovery, bidding, verification handoff, and booking confirmation using signed, validated, replay-protected messages.

What FAXP Is Not

FAXP is not a TMS, not a load board, not dispatch software, not telematics/tracking infrastructure, not document custody workflow (BOL/POD), not payment/settlement rails, and not a centralized operations host for verifier services.

FAXP does not determine regulatory eligibility; it authenticates protocol messages and can transport optional verifier evidence.

Audience Focus

Primary audience (v1 focus - contributions, feedback, early integrations)

TMS vendors and load board developers integrating protocol messaging in production stacks.
Agentic and AI developers (including A2A-aligned communities) building orchestration workflows quickly.
Large shippers and enterprise logistics teams already piloting agentic AI.

Secondary audience (after v1 stability and vendor tooling matures - broader adoption and validation)

Mid-sized brokers and 3PL operators who feel daily integration pain and can trial demos.
Small carriers and independent operators (adopt via broker/load board layers once tooling is accessible).

Pain Points We Address First

Manual re-keying and inbox/phone thrash from mismatched TMS and load board formats.
AI freight agents blocked by proprietary APIs and vendor lock-in.
No neutral, interoperable way to express agent booking capabilities and optional trust-related evidence across systems.

v1 Scope

Includes: opportunity discovery through booking confirmation, standard envelopes, validation rules, replay and TTL controls, signing, verification handoff fields, conformance artifacts, and governance checks.

Excludes: dispatch execution, live tracking/telematics, document custody (BOL/POD), invoicing, payment, settlement, and centralized FAXP-hosted verification operations.

Sponsorship Opportunities

FAXP is open infrastructure for the freight ecosystem. If your team wants to accelerate adoption with implementation support, events, or verifier tooling sponsorship, Contact Us.

Start Building

Read the AI Freight Booking overview.
Read the Protocol Spec.
Review the FAQ.
Contribute on GitHub.

Open Freight Interoperability for AI Agents