Esc
Guides
Build on the freight spine.
Start with the first call, then wire authentication, MCP clients, webhooks and error handling. Every guide is short and to the point.
Get started
Core concepts
MCP quickstartLogistics MCP server quickstart: connect Claude, Cursor or any MCP client to Navo24 and let the model track containers, compare sailings and plan loads.Connect Navo24 to any AI assistantAdd the Navo24 container-tracking MCP server to Claude, ChatGPT, Codex, Gemini, Grok, Hermes Agent, OpenClaw, Kimi, Qwen, DeepSeek or any other MCP client, with an API key or your TrackingMCP sign-in.Navo24 MCP serverOne MCP address, mcp.navo24.com, for distance and transit time, places, CO2e, parcel, vessel, road and rail tracking, demurrage free time and flight schedules.Errors and rate limitsResponse envelopes, error codes, and the usage headers that ride on every call.Billing and usageWhat TrackingMCP counts, what it bills, what stays free, and how to read your own usage.
Guides
WebhooksRegister an HTTPS endpoint, verify the HMAC signature, and let a Navo24 product push events to you instead of polling. One model across ocean, air and the rest of the family.Identifiers and portsThe references the APIs take: container numbers, bills of lading, AWBs, and UN/LOCODE ports.DCSA event feedThe same tracking events in the industry-standard DCSA format, so a client that already speaks the standard plugs in without a mapping table.SDKs and clientsGenerate a typed client from the OpenAPI spec, or call the API directly with the snippets.Embed the Navo apps on a client siteEmbed container tracking on your website, plus freight rates, sailing schedules and AI mode, in your own brand with one script tag and a domain-locked key.Navo Maps: map and place searchPut a Navo map on a page, add place search and reverse geocoding, and show ports, airports and rail terminals. MapLibre, Leaflet and plain HTTP.