Skip to content
Navo24 Navo24

Developer portal

Freight API for developers. Shipment data your code can call directly.

Send a container, an air waybill or a lane; get back status, route, milestones, schedules, rates and load plans. Every freight API here speaks REST, and most speak MCP as well, behind a single bearer key.

  • 12 APIs
  • 95 endpoints
  • 32 MCP tools

Your first call

Track a container in one request.

The public lookup needs no account. Paste a container number, a bill of lading or a booking, and read back a normalised status and a truthful ETA.

See the endpoint
curl -X POST 'https://api.trackingmcp.com/v1/track/public' \
  -H "Content-Type: application/json" \
  -d '{"reference":"MEDU1234562"}'

Get started in three steps.

  1. Make a call with no account The public container lookup needs no key. It is rate-limited per IP and meant for a quick check. Getting started
  2. Get an API key Sign up, mint a key in the developer settings, and send it as a bearer token on every authed request. Authentication
  3. Connect an MCP client Point Claude, Cursor or any MCP client at a Navo24 server and let the model call freight tools. MCP quickstart

The freight APIs

Browse the reference
api.trackingmcp.com

TrackingMCP

Where every container is, and when it will really arrive.

REST MCP 17 endpoints · 7 tools
api.aircargomcp.com

AirCargoMCP

Any air waybill, from acceptance to delivery, on one timeline.

REST MCP 12 endpoints · 3 tools
api.schedulesmcp.com

SchedulesMCP

Compare sailings the way a freight desk actually books them.

REST MCP 12 endpoints · 8 tools
api.loadingmcp.com

LoadingMCP

Plan the stuff inside the box, to the standard, not by eye.

REST MCP 7 endpoints · 6 tools
api.freightratesmcp.com

FreightRatesMCP

What a lane costs this week, before you brief a forwarder.

REST MCP 12 endpoints · 8 tools
api.navo24.com

DistanceMCP

How far and how long, door to door, by sea, river, road, rail or air.

REST 14 endpoints
api.navo24.com

MapsPlatformMCP

Find any city, port, airport or rail terminal, and put it on the map.

REST 10 endpoints
api.navo24.com

CarbonMCP

CO2e of any shipment, by sea, air, road or rail, per ISO 14083 and the GLEC Framework.

REST 3 endpoints
parcel.navo24.com

ParcelMCP

Track a parcel by its number: carrier detected from the number, every connected postal and courier source asked at once.

REST 2 endpoints
vessel.navo24.com

VesselMCP

Where a vessel is now, from live AIS, with its particulars and port calls.

REST 2 endpoints
road.navo24.com

RoadMCP

Truck route, distance, driving time and an ETA that counts driver rest, with progress from a shared live position.

REST 2 endpoints
rail.navo24.com

RailMCP

Rail route through terminals, transit time, and the status of a container with its rail moves.

REST 2 endpoints

REST

Plain HTTP, JSON out

Bearer-key auth, predictable envelopes and DCSA-normalised events. Copy-paste samples in curl, JavaScript and Python on every endpoint.

Browse the reference

MCP

Freight state as tool calls

Point Claude, Cursor or any MCP client at a server and let the model call tracking, schedules and load planning directly. Same key, same data.

MCP quickstart

Guides

All guides