Direct carrier integrations
Use direct API lanes whenever the carrier exposes stable structured data and the route can stay fast, deterministic, and low-touch. No browser execution required.
FlowMint tracks across 15+ major shipping lines through direct carrier integrations, browser-backed routes, vessel pages, terminal-specific lanes, and manual recovery paths — while keeping one customer-facing shipment contract.
Every coverage layer feeds the same delivery surface. Customers always receive one status, one timeline, and one contract.
Use direct API lanes whenever the carrier exposes stable structured data and the route can stay fast, deterministic, and low-touch. No browser execution required.
Use browser lanes when direct APIs are incomplete but the page state can still be normalized into JSON-first evidence and one stable delivery contract via FlowNUC.
Terminal-specific and vessel-detail paths extend coverage where carrier-level status is delayed, ambiguous, or commercially insufficient for downstream systems.
Local browser intervention and review lanes remain inside the same orchestration model so rare edge cases do not require a separate customer-facing workflow or carrier portal.
The carrier directory shows the detailed carrier, source, and lane matrix — including which routes stay cloud-first and which require FlowNUC browser execution.