Instant
Runs inline in the request and answers with full results. The operational modules — billing, J1, chassis stock and bookings, the calculator — are instant on purpose: a dispatcher wants the answer now.
Features
Thirteen automation modules and three Motive fleet mirrors. Each is a self-contained capability with its own API route, carrier handler registry, database records and dashboard page — so you can adopt one, or all of them, without changing how the rest behave.
Execution model
Your TMS and your operators share the same doors. What differs is only how long Neo keeps working after it answers.
Runs inline in the request and answers with full results. The operational modules — billing, J1, chassis stock and bookings, the calculator — are instant on purpose: a dispatcher wants the answer now.
Registers a cron on the Central-Time clock — or a single moment, for a timed chassis booking — and keeps running: read results back, edit the watchlist, pause, resume or retrace on demand. The database, not the queue, is the source of truth for every schedule.
The Motive mirrors — geofences, drivers, vehicles — have no API route at all. They sync nightly, optionally every quarter hour, and exist so the other modules can measure a wait or a lane instead of guessing it.
The catalogue
Live today unless marked experimental or next release. Coverage per carrier is on the integrations page.
Trace inbound containers across BNSF, CN, CP, CSX, NS and UP for ETA, last free day, storage and customs holds and the full event history. Run once, or put a watchlist on a Central-Time schedule and get emailed only when something moved — with a morning brief that says what is at stake today.
BNSF · CN · CP · CSX · NS · UP
Trace outbound bookings for earliest receiving date, rail ingate cutoffs, vessel and port-of-load details and revision tracking — the same instant-or-scheduled model, live progress and notification pipeline as import.
COSCO · Evergreen · MSC · ONE · Yang Ming
Batch-check empty-return locations for containers across ten shipping lines, inline, with a well-formed row per container — even for a line that is not wired yet. Schedule it and get told only when a return location changes.
CMA CGM · ZIM · COSCO · Evergreen · Hapag-Lloyd · HMM · Maersk · MSC · ONE · OOCL
One public page read per pool, no login: CCM's return grid, DCLI's seven region pages and FlexiVan's twelve pools across 108 depots. Every depot comes back with the sizes it takes, its published hours and whether it is open right now. Run once, or schedule it and be told when a depot gains or loses a size.
CCM · DCLI · FlexiVan
Read TRAC's pools one market at a time, CCM's grid for today or tomorrow, or any of DCLI's seven region pages — up to five checks in one request — and list every location with its count. A row with stock books in one click; every location keeps a 30-day history. A check is a read: nothing is booked unless the dispatcher books.
TRAC · CCM · DCLI
Reserve chassis by size, class, pool, region, depot and date. TRAC end to end; CCM through its dated grid across all 89 depots, cancellable with a reason; DCLI as a release request emailed to the depot's contact with the reply read back. Timed bookings fire at a Central-Time moment and retry until booked.
TRAC · CCM · DCLI
Look up to ten chassis at once in the public GIER registry for ownership, current IEP, pool, license plate and FHWA inspection — reCAPTCHA solved per chassis so nobody on your team has to — with results pushed live to the page as they land.
GIER registry
Submit empty rail billing per container: Yang Ming over its portal, Evergreen, Hyundai, Maersk, MSC and ZIM over direct steamship-line email. Every letter is signed with your company identity and logged with its Message-ID.
Yang Ming · Evergreen · Hyundai · Maersk · MSC · ZIM
The sibling module for loaded containers: Maersk over direct email, ZIM over its dispatch form with hazmat routed by email. Destination comes back as an output, not a guess.
Maersk · ZIM
Download ingate/outgate records for containers, trailers and chassis at Class I rail ramps, up to fifty pieces of equipment from one yard per run — and enrich them with measured dwell from your Motive geofences.
BNSF · CN · CSX · NS · UP
Drop one to fifty delivery-order PDFs on the form, or send signed links from your TMS. Neo recognizes the layout, prefills the form, and returns reference numbers, bills of lading, pickup and delivery locations and per-container details — import and export flavors — with every assumption it had to make listed beside the row.
Import: GOLDEN · OEC · OOCL · FNS · YANGMING · MAGID · MAERSK — Export: OEC · EUSU
Your overweight rules — by equipment, lane and permit — kept as a versioned table and applied wherever a weight shows up: a parsed delivery order, a laden billing, a J1 gate record. Validate one to five hundred boxes in a call, or let the verdict appear inline where the dispatcher already is.
Your rules, your lanes
Back-calculate the earliest and latest departure time from the delivery appointment: measured yard loading times, measured lane transit between yards your fleet actually runs, a driver hours verdict and a ready-to-send driver message. The module reports its own accuracy and suggests tuning — nothing self-adjusts.
Your fleet's own lanes
Read-only mirrors of your Motive geofences (with per-yard wait statistics and who is inside right now), licensed drivers (with hours-of-service and live locate) and vehicles (with a stored day-by-day location trail). Nightly sweeps, optional quarter-hourly refreshes, CSV everywhere.
Motive
Roadmap
Four planned modules, each built the way the live ones are: its own route, audit trail and dashboard page. No dates here — the changelog records what shipped, and the order can change when a customer needs one sooner.
Watch a move through Motive: stuck at the ramp, detention, late, arriving.
Register a shipment as one container move with ordered stops — rail pickup, chassis depot, customer warehouse, empty return — and Neo watches the assigned truck through Motive every few minutes. It derives arrived, departed and dwell per stop with a GPS cross-check, and raises the action each situation calls for.
Any yard or customer site in your Motive geofences
The load, its stops and its driver in one record the modules share.
A shipment record that the tracing, chassis, billing and monitoring modules all hang off: import the day's list from your TMS or a sheet, assign a driver, see every portal fact about the container beside the stops it has to make, and swap a driver or a stop without re-keying anything.
Your TMS, or a spreadsheet
Book the container pickup the way Neo books the chassis.
Reserve container pickups at the pools and depots that take appointments, with the same shape as chassis reservation: book now or at a Central-Time moment, retry until booked, keep the receipt as evidence, cancel from the API or the dashboard.
Pools and depots that take pickup appointments
A broken chassis reported to the pool without a dispatcher on hold.
When a driver reports a flat, a light out or a brake problem, Neo files the breakdown with the pool that owns the chassis, keeps the ticket and its replies on the chassis's timeline, and tells the dispatcher what the pool decided — repair on site, swap, or tow — so nobody sits on the phone.
TRAC · DCLI
Get started
A thirty-minute walkthrough on your own Chicago lanes and carriers. We will show a live trace on one of your ramps, a scheduled watchlist and the dashboard your team would open every morning.