Pull-quote: “The AI analyst is not a chatbot bolted on the side. It is the center of the platform.”
Why this matters
Most freight intelligence platforms have followed the same pattern with generative AI: keep the existing dashboards, add a chatbot in the corner, ship a press release. The chatbot answers FAQ-class questions and sometimes summarizes a dashboard. Senior freight analysts ignore it.
FreightCortex is built around the AI analyst, not the other way around. The analyst is a multi-tool agent with sixteen callable tools that can pull data, run statistical tests, run simulations, and produce structured outputs. It is more like a junior analyst with access to the full platform than like a chatbot.
The 16 tools
| # | Tool | What it does |
|---|---|---|
| 1 | query_corridor_metrics |
Lane-level KPIs (cost, transit time, capacity, on-time %) |
| 2 | query_carrier_metrics |
Carrier-level KPIs and ranking |
| 3 | query_origin_destination_flows |
OD-pair flows with filters |
| 4 | compute_anomaly_score |
Z-score / isolation forest / CUSUM on a metric series |
| 5 | run_capacity_simulation |
What-if capacity reduction or expansion |
| 6 | run_demand_simulation |
What-if demand shock scenarios |
| 7 | run_disruption_simulation |
What-if disruption (port closure, weather, strike) |
| 8 | run_routing_simulation |
Reroute optimization under constraints |
| 9 | run_modal_shift_simulation |
Mode-shift impact (truck ↔ rail ↔ intermodal) |
| 10 | run_emissions_simulation |
CO₂ impact under scenarios |
| 11 | run_network_stress_test |
Network-wide stress scenarios |
| 12 | compute_shortest_path |
Multi-modal shortest path |
| 13 | compute_betweenness |
Node centrality |
| 14 | compute_communities |
Network communities |
| 15 | generate_report |
Compose structured report from analytical session |
| 16 | generate_chart |
Render a specific chart type with provided data |
Each tool is a typed contract: inputs, outputs, and side effects are documented. Every call is logged with the requesting question, the parameters, the result, and timestamps.
Why typed tools matter
The single most important architectural decision in agent design is whether your tools have contracts. Untyped tools — give the model a vague description and let it improvise — are unreliable. Typed tools — with explicit input schemas, output schemas, and validation — are reliable.
FreightCortex’s analyst will not call a tool with an invalid input. The schema rejects the call before it reaches the data layer. That eliminates an entire class of failure that plagues unconstrained agents.
What this lets analysts do
A typical session: an analyst asks “what’s driving the cost increase on the Atlanta-Dallas corridor over the last quarter?” The analyst:
- Calls
query_corridor_metricsfor Atlanta-Dallas with a 90-day window - Calls
compute_anomaly_scoreon the cost series - Calls
query_carrier_metricsto see which carriers’ rates moved - Calls
run_capacity_simulationto test whether the increase tracks capacity changes - Generates a structured report with charts
This is fifteen minutes of senior-analyst work. With FreightCortex, it is one question and a structured answer with citations.
Closing
A chatbot bolted on a dashboard is a feature. An AI analyst at the center of the platform is a product. The difference shows up the moment senior analysts compare them in real engagements.
