One Cube. Five faces.
Each agent reuses the multi-tenant backbone, the eAdaptor integration, the user-billing infrastructure, and the brand system the previous one shipped. The order below is also the launch order.
CargoCube · Ops Agent
Live shipment lookup on hover. AI replies grounded in CW1 data. Six journey dates per container. Seven languages. Per-user usage analytics.
CargoCube · Service Agent
Resolve tier-1 customer queries autonomously (BL copy, shipment status, ETA). Triage and route the rest with a one-paragraph summary attached. SLA enforcement. KB RAG over your own SOPs.
CargoCube · Sales Agent
Quote drafting from customer history. Account-level shipment summaries on the CRM record. Lost-account early-warning. Win/loss tagging tied to shipments.
CargoCube · Finance Agent
Invoice reconciliation against shipment data. Aged-AR follow-up drafts. Margin-leak detection per job. Daily exception digest.
CargoCube · Compliance Agent
HS-code suggestions with audit trail. Document-vs-shipment cross-check. Sanctions screening notes. Customs declaration draft review.
Same backbone, every time.
Each new agent inherits this shared infrastructure on day one — which is why we ship them faster, and why they all behave the same way.
Shared CW1 grounding
One eAdaptor Next connection per tenant, reused by every agent. OAuth + JWT client assertion. No per-agent re-onboarding.
Per-tenant + per-domain auth
One API key per CW1 instance. Each key is locked to allowed email domains. A leaked key from one tenant cannot be used by anyone outside that tenant's domain list.
Per-user usage tracking
Every AI call is attributed to a user, a tenant, an agent. Pull CSVs for billing or internal review. Same schema across agents.
One brand, role-shaped
Same logo, same gradient, same voice. Each agent gets a secondary accent colour. The Cube has many faces.