Navo24 Navo24
Freight, connected

Navo. Your Platform, Your Rules.

The operating layer for freight, built for people, ready for agents. Never dark, with one connected data spine across tracking, schedules, rates, loading and more. Use it yourself, wire it into your stack, or hand it to an agent. With Navo you have limitless customization.

Start free See how it's built
TrackingRatesSchedules
Ask Navo anything
Try
Try
Try
Try

No login needed · 239 carriers · DCSA-normalised · 0–5 min event freshness

Pick the sailing

Cross-checked against 72,000+ sailings, so the departure you choose is the one that actually sails.

Price the lane

Daily spot rates on the same spine as the schedule, so the lane you priced is the lane you booked.

Plan and track the box

Load it to the standard, then follow it to discharge. Web, API, MCP: the same data in all three.

Why we built the spine

Status lives in twelve tabs. It shouldn't.

Carrier portals that don't agree with each other. Status you check by hand, one site at a time. A delay you hear about after your customer does.

You. A dashboard for checking status, comparing lanes, planning a load.
Your systems. REST and webhooks for your TMS or internal tools.
An agent. MCP-native: query and act on the same events you read.

Underneath Navo24 there is one connected data layer instead. Nothing is prepared separately "for AI". It is the architecture from the first connector.

Why teams pick Navo24

The numbers behind the feed

Every figure here is measured, not marketed: the same numbers the data spine runs on

Carriers covered 239 146 direct connectors
Sailings monitored 72,000+ across 5,000+ lanes
AIS positions recorded 110,000+ 2,700+ vessels on file
Event freshness 0–5 min cross-checked across 2–3 sources
24/7

A fix crew that never sleeps

An AI engineering agent watches every connector around the clock: it detects breakage, diagnoses it, and drafts the fix within minutes, with humans reviewing every change. That is why we are navo24.

DCSA

The standard the majors built

Every event normalised to the DCSA standard: the schema MSC, Maersk, CMA CGM, Hapag-Lloyd and ONE created and adopted themselves. Drops into your TMS without a translation layer.

MCP ×3

AI-native from day one

First-party MCP servers for tracking, schedules and loading: your agents buy and query without a sales call. No incumbent (Terminal49, Vizion, project44) ships one.

Also counted: 2,700+ vessels on file 55,000+ port calls observed 66,000+ schedule revisions caught production database, July 2026

Ready to stop checking manually?

Start with one component. No card, no commitment.

The suite

Different tools. One spine.

trackingmcp.com

TrackingMCP

Container visibility across 239 carriers, normalised to one standard.

aircargomcp.com

AirCargoMCP

Air waybill tracking with Cargo-IMP milestones.

schedulesmcp.com

SchedulesMCP

72,000+ sailings, 5,000+ lanes, reliability scoring.

loadingmcp.com

LoadingMCP

CTU Code and IMDG-compliant load planning.

freightratesmcp.com

FreightRatesMCP

Daily ocean spot rates with trend analysis.

More instruments on the way

Every tool has a free tier and the same API shape. Pick one, the rest plug in later.

Not screenshots

The suite, doing the thing

Live examples: ETA prediction, demurrage exposure, MCP calls, load plans, lane reliability and port congestion. Real responses, not mockups.

ETA prediction
Rotterdam arrival14 Sep 09:40+2 days vs carrier
Demurrage exposure
Free time left6 days+3 boxes at risk
8 of 14 free days used
MCP call
tools/call track_container
args: { "id": "MSCU8142203" }
 
200 OK 142 ms
status: "AT_SEA"
eta: "2026-09-14T09:40Z"
The journey
Discharge, Rotterdam14 Sep 09:40+2 days, berth window moved
Gate out
Loaded
At sea
Discharge
Lane reliability
CNNGB → NLRTM 78% on time
CNSHA → DEHAM 64% on time
VNSGN → USLAX 41% on time
Port congestion
Rotterdam, vessels waiting11+3 this week
Agentic workflows

Tell it what you need, in plain language

Find a container, book the most reliable sailing to Rotterdam, check a load against IMDG rules, in one message. Not a bolt-on chatbot: the agent works on the same data spine you already use.

MSC · departs 06 Sep 78% on time · USD 1,940 per 40HC
Pricing

Start free. Grow when you need to.

Free

$0

5 active containers, 100 MCP calls/month, no card required.

Start free

Team

Most teams
$35/ 10 shipments

For growing ops teams who need more volume and multi-user access.

Contact us

Enterprise

Custom

Custom limits, SLAs, and support for high-volume operations.

Talk to sales
Before you commit

The questions people ask first

What exactly is Navo24?

Freight tools on one normalised data spine: container tracking, air waybills, sailing schedules, load planning and ocean spot rates. Each works on its own (dashboard, REST API, webhooks and an MCP server), and they share the same events, so the lane you priced is the lane you track.

Is the free tier actually free?

Free: 5 active containers and 100 MCP calls a month, no card. When you pass it, tracking stops updating until you upgrade. Nothing is invoiced silently.

What's MCP, and do I need to care if I'm not using AI?

No: the dashboard and the REST API work standalone, and most customers never touch MCP. Yes, later: if you want an agent to query or act on this data, the server is already there: you don't migrate anything.

Read all →

Navo24

Start with one component

Track a box, book a sailing, or pack a container, today. Free tier: 5 active containers, 100 MCP calls a month, no card required.

From the blog

Notes from the freight desk

All posts →