What is the difference between a freight REST API and an MCP server?
A REST API is called by your own code with fixed endpoints and you decide how to present the result. An MCP server exposes the same capabilities as tools that an AI agent can discover and call by itself, so the assistant fetches live data instead of guessing. Navo24 offers both over the same data.
Which identifiers can I use to track an ocean shipment?
Container numbers, bill of lading numbers and booking numbers are the usual references. A container number follows ISO 6346: three owner letters, a category letter, six digits and a check digit. Check the format on your side first to reject typos before a lookup.
Why do two tracking sources show different statuses for the same box?
Carriers and terminals name and time their events differently, and some estimates are typed by hand rather than computed. Mapping events to a common model such as DCSA event types, and showing the source of each ETA, removes most of the disagreement.
Can I book freight through the rates API?
No. FreightRatesMCP returns indicative ocean FCL lane rates and rate history for planning and quoting context. Navo24 is a data and software platform, not a forwarder or carrier, so it does not sell space or handle cargo.
How do I stop an AI assistant inventing ETAs?
Give it a tracking tool and instruct it to answer only from the tool result, quoting the vessel, port call and timestamp. When the tool returns no data, the assistant should say so rather than estimate. MCP tools make this straightforward because the model calls the source directly.