One map, four interfaces
TrackJet exposes every capability through machine interfaces. Docs explain here; the normative reference lives at [/developers](/developers) and [/developers/api](/developers/api) — no duplicated specs that can drift.
REST + GraphQL
The commercial API: detection, tracking surfaces, carriers, webhooks, EPCIS. OpenAPI 3.1 at /api/v1/openapi.json. Start with the [quickstart](/docs/api-quickstart).
MCP (Model Context Protocol)
Twelve read-only tools for AI agents — detection, carrier info, transit statistics, delivery probability, timeline verification, truth assessment — served per the MCP spec. Connect Claude or any MCP client to https://trackjet.world and your agent can answer "is this container number valid and where does it track?" with live data. Tool list + config: [/developers](/developers).
SSE live streams
GET /api/v1/track/{number}/stream pushes events as they arrive where a licensed feed exists (DHL Group today); other numbers close immediately with no_live_feed — never fabricated events.
EPCIS 2.0
Supply-chain capture/query in the GS1 shape — see [EPCIS onboarding](/docs/epcis-onboarding).
Transparency endpoints (public, no key)
Proof, inclusion and root-history endpoints back the verification story — see [transparency for auditors](/docs/transparency-for-auditors). They are public because a transparency log you cannot read is theatre.
Changelog & status
API changes are announced in the [blog](/blog); live availability is on [/network-status](/network-status).