Per-client credentials
Your TMS presents its own identity and secret on every call. Revoke one client and it stops within seconds; nobody else is affected.
Integrations
Neo drives carrier portals the way a dispatcher would — logged in, session kept warm, CAPTCHAs solved — and exposes the result over one authenticated API. Here is exactly what is live, per module.
Signs into the portals your operation already depends on
Coverage matrix
Coverage grows carrier by carrier, and a pending carrier degrades gracefully: you still get a well-formed row that says so, and the rest of the batch completes.
| Module | Live today | Coming |
|---|---|---|
| Empty Return Check |
|
|
| Empty Return (Chassis) |
|
|
| Import Tracing |
| Complete |
| Export Tracing |
|
|
| Rail Billing (Empty) |
|
|
| Rail Billing (Laden) |
|
|
| Chassis Reservation |
|
|
| Chassis Provider Lookup |
| Complete |
| Chassis Availability |
|
|
| J1 Gate Records |
|
|
| DO Parsing (import) |
|
|
| DO Parsing (export) |
|
|
A carrier that is not wired yet is never a hard failure: it returns a well-formed pending row, so a mixed batch still succeeds for the carriers that are live.
Your TMS
Neo was designed to be called by a transportation management system — and to hand back data clean enough to write straight into a shipment record.
Your TMS presents its own identity and secret on every call. Revoke one client and it stops within seconds; nobody else is affected.
POST to create, GET to read results back, PUT to edit a watchlist, PATCH to pause, resume or retrace. The same error envelope everywhere, validated before anything runs.
A TMS call can name the operator it acts for, so the request shows up as theirs on the dashboard — with the same ownership rules as one they typed by hand.
Geofences, drivers and vehicles are mirrored on a schedule; hours-of-service and live locations are read on demand; a truck's past day is collected once and kept. Each endpoint's measured limits are respected.
POST /api/cs/tracing/import
x-user-id: tms-prod
x-api-key: ••••••••••••••••
{
"execMode": "SCHEDULED",
"schedule": { "cron": "0 6-18/4 * * *" }, // Central Time
"items": [
{ "container": "MSCU5120347", "rail": "BNSF" },
{ "container": "TCLU8841201", "rail": "UP" }
],
"notify": {
"policy": "DAILY_DIGEST",
"digestAt": "06:00",
"recipients": ["dispatch@example.com"],
"watchFields": ["eta", "lfd", "holds"]
}
}
→ 202 Accepted { "processId": "req_9f3a…", "nextRunAt": "2026-10-01T11:00:00Z" }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.