Getting started

Navo24 is freight intelligence you call directly: container and air-waybill tracking, sailing schedules and reliability, spot rates and load planning. Each product ships a REST API, and most ship an MCP server too, behind one bearer key.

Make a call with no account

The fastest way to see real data is the public container lookup. It needs no key.

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

You get back a normalised status, the vessel, and an ETA that carries its own basis (predicted, not a stale promise):

{
  "ok": true,
  "reference": "MEDU1234562",
  "carrier": "MSC",
  "status": "On board vessel",
  "eta": "2026-07-03",
  "eta_basis": "predicted"
}

Public endpoints are rate-limited and meant for a quick check. Anything portfolio-shaped needs a key.

Get an API key

1. Sign up at trackingmcp.com.
2. Open the developer settings and mint a key. It carries a product prefix, for example tmcp_ for tracking.
3. Send it as a bearer token on every authed request.

curl https://api.trackingmcp.com/v1/containers/summary \
  -H "Authorization: Bearer tmcp_YOUR_API_KEY"

The same key works across the family where a product accepts the family credential. Read the authentication guide for the full picture on prefixes and headers.

Where to go next

• Authentication: keys, prefixes and the bearer header.
• MCP quickstart: wire Claude, Cursor or any client to a server.
• Errors and rate limits: envelopes, error codes and usage headers.
• API reference: every endpoint, with copy-paste samples.