Signal · CO₂ · Track & Trace

The intelligent API hub for logistics platforms.

One integration, six APIs: AI-decoded disruption signals from the world's news, ISO 14083-aligned CO₂ calculation, DCSA-standard track & trace — plus compound intelligence that scores your shipments, routes, and ports across all three. Super-smart input data your customers can't build themselves.

DCSA T&T compliantISO 14083 · GLECUN/LOCODE native

The hub

Six APIs. One integration.

Three core products every logistics platform ends up rebuilding — and three compound APIs that only exist because the products share one knowledge graph: signals sharpen your ETAs, tracking legs feed your emissions math, and your shipments get scored against the world.

Foundation · Locations Every product speaks UN/LOCODE — the UNECE registry of 115,000+ trade locations across every transport mode. Nexus serves it clean: validated, geocoded, alias-resolved, with SMDG terminal codes — GET /v1/locations/NLRTM

01 · Signal Intelligence

From raw noise to routed intelligence

Every signal your platform receives has passed through four stages. The order matters — each stage adds structure the next one depends on.

Ingest

Continuous pull from global news event feeds in 100+ languages, plus AIS movements and customs bulletins. Deduplicated at the source.

news events100+ langsAIS

Understand

AI reads each story and extracts the logistics facts: what happened, where, to which commodity, and how severe — with a confidence score.

NERevent typingconfidence

Connect

Entities resolve into a living knowledge graph: ports link to regions, commodities to trade lanes, disruptions to downstream spillover.

UN/LOCODEgraph edgesspillover

Serve

Signals, risk indices, and AI advisories stream to your platform as versioned APIs and webhooks — super-smart input data, ready to use.

RESTwebhooksprovenance

01 · Signal Intelligence

Not headlines. Decisions-ready entities.

  • Port & region risk indices

    A rolling risk score per port and corridor, computed from event density, severity, and the graph's spillover edges — so you see Antwerp heating up while the strike is still in Rotterdam.

  • Commodity exposure mapping

    Every disruption is tied to the commodities and trade lanes it touches. Query "what threatens my grain flows this week" in one call.

  • AI advisories with provenance

    Each signal carries a suggested action and links back to the source articles that produced it. Your users can always ask "why?"

NLRTM · Labor disruptionconf 0.91
Strike enters day 3; grain terminals at standstill. Dwell forecast +2.1 days.
graincontainersspillover: BEANR
EGPSD · Transit frictionconf 0.84
Canal convoy scheduling delays adding ~18h to northbound transits.
energylane: ASIA–EUR
BRSSZ · Volume shiftconf 0.77
Soybean exports up 12% week over week; berth pressure expected to build within 10 days.
soybeanforecast

02 · CO₂ Calculator

Emissions your auditors will accept

  • ISO 14083 & GLEC methodology audit-ready

    Every figure is computed to the ISO 14083 standard using GLEC Framework emission factors — the numbers your customers can put straight into Scope 3 reports and tender responses.

  • Per-leg, well-to-wake breakdown

    Ocean, rail, barge, and road legs each get their own WTW and TTW figures, with the factor set and data quality declared per leg.

  • Primary data when you have it

    Pass actual fuel burn or carrier-declared factors and Nexus uses them; omit them and it falls back to GLEC defaults — always flagging which path produced the number.

POST /v1/co2/calculate
{
  "shipment": { "teu": 2, "weight_t": 21.4 },
  "legs": [
    { "mode": "ocean", "from": "CNSHA", "to": "NLRTM" },
    { "mode": "rail",  "from": "NLRTM", "to": "DEDUI" }
  ]
}

// 200 OK — ISO 14083 aligned
{
  "total_wtw_kgco2e": 1842.6,
  "total_ttw_kgco2e": 1479.1,
  "legs": [
    { "mode": "ocean", "wtw_kgco2e": 1694.0,
      "factor_source": "GLEC_DEFAULT_v3",
      "data_quality": "modeled" },
    { "mode": "rail",  "wtw_kgco2e": 148.6,
      "factor_source": "carrier_declared",
      "data_quality": "primary" }
  ],
  "methodology": "ISO14083:2023"
}
MSKU 705431-0 · booking NX-88213 · CNSHA → NLRTM
JUN 18 09:02
EQUIPMENT · GTIN · ACT
Gate in, full — Yangshan Terminal, CNSHA
JUN 19 22:47
EQUIPMENT · LOAD · ACT
Loaded aboard MV Nordic Star, voyage 226W
JUN 20 04:15
TRANSPORT · DEPA · ACT
Vessel departed CNSHA
JUL 17 06:00
TRANSPORT · ARRI · EST
Arrival NLRTM — +2.1d vs schedule: labor-strike signal applied to ETA

03 · Track & Trace

DCSA-standard events, signal-aware ETAs

  • DCSA T&T compliant standard

    Shipment, transport, and equipment events in the DCSA Track & Trace schema — the same event codes and classifiers (ACT / EST / PLN) the carriers themselves are adopting. No proprietary format lock-in.

  • One stream, every carrier

    Nexus normalizes carrier feeds, terminal data, and AIS positions into a single DCSA-shaped event stream per equipment or booking reference.

  • ETAs that read the news

    This is where the hub pays off: disruption signals adjust estimated events in the stream automatically, with the causing signal linked for provenance.

Compound intelligence

APIs only a hub can serve

Each product is useful on its own. Because they share one knowledge graph, Nexus can answer questions no single-purpose provider can: which of your shipments are exposed, which routing is safest and greenest, and whether a port is actually slowing down.

IMPACT · SIGNAL × T&T

Your shipments, scored against the world

Register watchlists of bookings, lanes, and commodities. Nexus joins live signals with tracking state and returns exposure per shipment — not a news feed, a risk radar for your cargo.

ROUTES · ALL THREE

Fastest, greenest, safest — in one call

Every routing option priced by all three products at once: ETA reliability from signals, CO₂e from the calculator, schedule adherence from tracking. Rank by what your customer values.

PERFORMANCE · AIS BASELINE

Baselines that make risk measurable

AIS-derived dwell and berth-wait medians per port, updated daily. A signal saying "congestion rising" lands harder next to a measured curve — and your models get a quantitative ground truth.

API

One key. Three product surfaces.

Versioned REST with webhooks for push. Every response declares its provenance — source articles for signals, factor sets for CO₂, event classifiers for tracking — so downstream systems can set their own trust thresholds.

Signal Intelligence
GET /v1/signals live extracted events
GET /v1/ports/{locode}/risk rolling risk index
GET /v1/advisories AI suggestions
CO₂ Calculator
POST /v1/co2/calculate ISO 14083 per-leg CO₂e
GET /v1/co2/factors GLEC factor catalog
Track & Trace
GET /v1/tracking/{ref}/events DCSA event stream
POST /v1/tracking/subscriptions push via webhook
Hub intelligence
GET /v1/impact your shipments × live signals
POST /v1/watchlists register what you care about
GET /v1/routes options scored on risk · CO₂ · ETA
GET /v1/ports/{locode}/stats dwell & congestion baselines
Locations · UN/LOCODE
GET /v1/locations/{locode} validate + full record
GET /v1/locations?q=… resolve names & aliases
curl · signals by port
# What's affecting Singapore right now?
$ curl -s https://api.nexus.dev/v1/signals \
    -H "Authorization: Bearer $NEXUS_KEY" \
    -d port=SGSIN -d min_confidence=0.8

{
  "signals": [{
    "id":         "sig_04QX8N",
    "event":      "FUEL_QUALITY",
    "severity":   "MEDIUM",
    "confidence": 0.86,
    "sources":    ["src:20260710-064100-1204"],
    "advisory":   "Verify bunker certs for SGSIN
                   liftings after 2026-07-04"
  }],
  "as_of": "2026-07-10T06:45:00Z"
}

Who plugs in

Built to be someone else's smartest input

Nexus isn't a dashboard your team has to watch. It's the intelligence layer that makes the platform you already built feel clairvoyant.

Freight platforms

Visibility plus foresight

Ship DCSA tracking and disruption warnings inside booking flows — and suggest alternate ports while competitors are still reading the news.

Shippers & BCOs

Scope 3 without the spreadsheet

Pull audit-ready ISO 14083 emissions per shipment straight into sustainability reporting and tender responses.

Commodity traders

Exposure at a glance

Map every open position to live port and lane risk. Get advisories when the graph says a supply corridor is tightening.

Marine insurers

Price risk on evidence

Feed rolling port risk indices with full source provenance into underwriting and claims triage models.

Put the whole hub behind your product.

Early access includes all three APIs — signals, CO₂, and track & trace — plus 90 days of historical signal backfill and integration support from the team.

© 2026 Nexus — The Intelligent API Logistics Hub LAT 51°57′N · LON 4°08′E · NLRTM