Ocean freight · built as components
Ocean-freight intelligence your software can call directly.
Navo24 builds the three things ocean freight runs on — container tracking, sailing schedules and load planning — as composable MCP and API components. Take one tool today. Add the rest when you need them.
Drop in one component, or the whole suite. One reference in — truthful status out.
MCP-native
Every product ships as Model Context Protocol tools.
Speaks DCSA
Carrier events normalised to the industry standard.
REST + Webhooks
HMAC-signed events and a clean JSON API.
CTU Code · IMDG
Load planning to the rules cargo ships under.
AIS-aware
Live vessel positions feed every ETA.
One data layer
Tracking, schedules and loading share a spine.
The suite
Three tools. One spine.
Each is a complete product on its own domain, with its own free tier and its own API. They were built to be used apart — and to be worth more together.
TrackingMCP
Know where every container is — and when it will really arrive.
- Direct connectors to the major ocean carriers
- Events normalised to the DCSA standard
- HMAC-signed webhooks
SchedulesMCP
Compare sailings the way a freight desk actually books them.
- Hundreds of lanes, weekly refresh
- Reliability from observed arrivals
- Vessel-first, slot-sharing aware
LoadingMCP
Plan the stuff inside the box — to the standard, not by eye.
- CTU Code · IMDG · EN 12195
- Axle & floor-strength limits
- Centre-of-gravity checks
Why a suite, not three tools
The data flows one way — toward the thing you ship.
Tracking writes down what really happened. Schedules reads it to score which lanes keep their word. Loading plans the box that fills them. That is the whole point of a shared spine: the parts make each other smarter.
- Take only what you need
- Each product stands on its own — a tracking webhook, a schedule lookup, a load plan. Adopt one tool today; the rest are there when you want them. No platform migration, no rip-and-replace.
- They share one spine
- Tracking writes what really happened. Schedules reads it to score lanes. Loading plans the box that fills them. The data flows one way, toward the thing you ship — so the parts are worth more together than apart.
- Built for your software, and your AI
- Native MCP tools an assistant can call, a REST API your stack can hit, and webhooks that push. Plug a single component into what you already run — no front-end of ours required.
Read-only, one direction. No product depends on another to run.
Plug and play
Three ways to plug a component in.
No front-end of ours required. Wire a single tool into the AI assistant, the TMS or the spreadsheet you already run.
MCP tools
Native Model Context Protocol tools an assistant calls in plain language.
// any MCP client
"Where is MSCU1234567?"
→ get_container_detail REST API
A clean JSON API your stack hits directly — one reference, one response.
GET /v1/containers/MSCU1234567
Authorization: Bearer •••
→ 200 { status, eta, … } Webhooks
HMAC-signed events that push the moment something moves. No polling.
POST https://you.example/hook
X-Navo-Signature: sha256=•••
{ "event": "eta.changed", … } From the desk
Notes on moving boxes well.
22 Jun 2026
An alliance reshuffles — the service keeps its name, the ships change
When carriers redraw their networks, the service code often survives while the vessels, ports and transit underneath it move. Track the hulls, not the label.
22 Jun 2026
Blank sailings are climbing again — book the hull that still shows up
When carriers pull capacity to prop up rates, the nominal schedule starts lying. Book on reliability, not on the timetable.
22 Jun 2026
The Cape reroute, in transit days: what +10–14 does to your plan
When East–West services route around the Cape of Good Hope, the headline is the diversion. The number that hits your business is the extra transit.
Start with one component
Track a box, book a sailing, or pack a container — today.
Every product has a free tier and a five-minute first call. Pick the one that hurts most right now; the rest are here when you are ready.