AGENTS LIVE ACROSS 42 TRADE LANES

The Operating Stack for Autonomous Supply Chains

The Operating Stack for Autonomous Supply Chains

The Operating Stack for Autonomous Supply Chains

Deploy AI agents that plan, book, reroute, and reconcile global freight — grounded in a shared context layer, persistent memory, and native integrations into the systems your operation already runs on.

READ THE DOCS

AGENTS RUNNING

1,284

EVENTS / SEC

18,402

SHIPMENTS UNDER MGMT

96,117

EXCEPTION AUTO-RESOLVE

94.6%

[01] — CONTROL TOWER

One console. Every lane, every agent, every exception.

One console. Every lane, every agent, every exception.

Agents surface every decision they take — with the evidence, the alternative options, and a one-click override.

Agents surface every decision they take — with the evidence, the alternative options, and a one-click override.

meridian://control-tower/lanes

LIVE

◈ Lanes

◇ Agents

◇ Exceptions

◇ Memory

◇ Integrations

SHIPMENT

LANE

AGENT

ETA Δ

STATUS

MRD-88412

SHA → RTM · Ocean FCL

reroute-agent

−2.1d

REROUTED

MRD-88409

ICN → LAX · Air

booking-agent

0.0d

BOOKED

MRD-88371

HAM → JNB · Ocean LCL

customs-agent

+0.4d

IN REVIEW

MRD-88355

NQZ → DUS · Rail

reconcile-agent

−0.8d

SETTLED

MRD-88340

SIN → OAK · Ocean FCL

demurrage-agent

−0.2d

DISPUTED ✓

AGENT ACTIVITY

14:02:11 reroute-agent detected congestion at RTM · evaluated 3 alternates

14:02:14 → rebooked via ANR · saves 2.1 days · $0 penalty

14:03:02 customs-agent flagged HS-code mismatch on MRD-88371 · escalated to ops

14:04:47 reconcile-agent matched 214 invoices against rate cards · 3 disputes opened

14:05:10 ✓ memory updated · carrier reliability score CMA-CGM ↓ 0.03

[02] — AGENT RUNTIME

Agents run the loop. Continuously.

Agents run the loop. Continuously.

01 / SENSE

Ingest every signal

Vessel positions, port congestion, EDI messages, rate feeds, and weather — normalized into one event stream.

02 / PLAN

Reason over context

Agents pull contracts, SLAs, and carrier history from the context layer to score every feasible plan.

03 / ACT

Execute in your tools

Book, amend, file, and notify — directly in your TMS, ERP, and carrier portals through native connectors.

04 / VERIFY

Learn from outcomes

Every result is checked against intent and written back to memory — so the next decision is sharper.

reroute-agent · trace 4f2a91

EXIT 0 · 3.4s

$ meridian trace 4f2a91 --follow

$ meridian trace 4f2a91 --follow

[sense] port.rtm congestion_index=0.87 (+0.21 in 6h) · source: p44/webhooks

[sense] port.rtm congestion_index=0.87 (+0.21 in 6h) · source: p44/webhooks

[plan] retrieved 12 docs from context.layer (contracts, sla, carrier.history)

[plan] retrieved 12 docs from context.layer (contracts, sla, carrier.history)

[plan] candidates=3 · scored on cost, eta, co2, sla_risk

[plan] candidates=3 · scored on cost, eta, co2, sla_risk

[act] rebook MRD-88412 via ANR · booking.confirm → sap.tm ✓ · flexport ✓

[act] rebook MRD-88412 via ANR · booking.confirm → sap.tm ✓ · flexport ✓

[verify] eta_delta=−2.1d · penalty=$0 · sla_status=met

[verify] eta_delta=−2.1d · penalty=$0 · sla_status=met

[memory] episode written → lane:sha-rtm · carrier reliability updated

[memory] episode written → lane:sha-rtm · carrier reliability updated

[03] — CONTEXT LAYER + MEMORY

Agents are only as good as their context.

Agents are only as good as their context.

Meridian maintains a unified context layer over your entire operation — contracts, rate cards, SLAs, carrier performance, and live network state — versioned, permissioned, and queryable by every agent.

01 · EPISODIC MEMORY

Every decision, outcome, and override is stored as an episode — replayable and auditable.

02 · SEMANTIC MEMORY

Distilled knowledge about lanes, carriers, and seasonality — continuously refreshed from outcomes.

03 · SHARED STATE

Agents never act on stale data — one consistent world model across the whole fleet.

ERP / TMS

EDI / API

TELEMETRY

DOCS / OCR

▼ ▼ ▼ ▼

CONTEXT LAYER

normalized · versioned · permissioned

▲ ▼

AGENT RUNTIME

booking

reroute

customs

reconcile

▲ ▼

EPISODIC MEMORY

decisions · outcomes · overrides

SEMANTIC MEMORY

lanes · carriers · seasonality

agents/reroute.py

PYTHON · SDK v2.4

from meridian import Agent, context, memory

from meridian import Agent, context, memory

@Agent.on(event=”lane.congestion”)

@Agent.on(event=”lane.congestion”)

def reroute(shipment):

def reroute(shipment):

ctx = context.query(

ctx = context.query(

“contracts, sla, carrier.history”,

“contracts, sla, carrier.history”,

lane=shipment.lane,

lane=shipment.lane,

)

)

plan = shipment.plan(ctx, optimize=[“eta”, “cost”, “co2”])

plan = shipment.plan(ctx, optimize=[“eta”, “cost”, “co2”])

result = plan.execute(approve_below=”$2,500”)

result = plan.execute(approve_below=”$2,500”)

memory.write(episode=result) # agents learn from every run

memory.write(episode=result) # agents learn from every run

[04] — BUILT FOR ENGINEERS

Define agents in code. Ship them like software.

Define agents in code. Ship them like software.

A typed SDK, local simulation against replayed network history, version-controlled policies, and CI-gated deploys. Guardrails and spend limits are declarative — no prompt spaghetti.

→ Simulate agents on 24 months of replayed lane history

→ Declarative guardrails, budgets, and approval gates

→ Full trace on every run · export to your observability stack

[05] — INTEGRATIONS

Native to the stack you already run.

Native to the stack you already run.

Bidirectional connectors with field-level mapping. Agents read and write where your team already works — no rip-and-replace.

Bidirectional connectors with field-level mapping. Agents read and write where your team already works — no rip-and-replace.

SAP TM

ERP / TMS

ORACLE OTM

ERP / TMS

FLEXPORT

FORWARDING

PROJECT44

VISIBILITY

EDI X12 / EDIFACT

MESSAGING

SNOWFLAKE

DATA CLOUD

DATABRICKS

LAKEHOUSE

NETSUITE

ERP

KAFKA

EVENT STREAM

SLACK / TEAMS

APPROVALS

“We stopped staffing a night shift for exception handling. The agents catch a rolled booking before our forwarder even emails us — and they’ve already priced the alternatives.”

“We stopped staffing a night shift for exception handling. The agents catch a rolled booking before our forwarder even emails us — and they’ve already priced the alternatives.”

VP GLOBAL LOGISTICS · FORTUNE 200 ELECTRONICS

“The context layer is the unlock. Our agents negotiate with carriers using our actual contracts and our actual history — not a generic model’s guess.”

“The context layer is the unlock. Our agents negotiate with carriers using our actual contracts and our actual history — not a generic model’s guess.”

HEAD OF SUPPLY CHAIN TECH · GLOBAL RETAILER

−38%

−38%

EXPEDITE SPEND, FIRST 90 DAYS

11 min

11 min

MEDIAN EXCEPTION → RESOLUTION

99.98%

99.98%

RUNTIME UPTIME, TRAILING 12M

$214M

$214M

FREIGHT SPEND UNDER AGENT MGMT

[06] — GET STARTED

Put agents on your network.

Put agents on your network.

Connect a lane, replay your history, and watch agents work it — before they touch production.