How It Works
How Custody Works.
Custody reads both sides of every handoff, and the conditions in transit each source reported, from the systems already running the freight. It states agree, disagree, or unknown, then locks the result into one Evidence Pack.
Custody is in development. "At launch" marks connections planned for the first release.
Three answers only: agree, disagree, or unknown. Deterministic rules. Same inputs, same answer.
Three Steps. No New Work at the Dock.
Connect.
You send Custody your loads and facility records through a secure API, and we help your team integrate. Your carriers approve access to the records their systems already produce for those loads, and only those loads.
Record.
As the load moves, Custody builds the Evidence Pack from system records: every handoff, and the conditions in transit. On a temperature-sensitive load it compares what the shipper API, the carrier TMS, and the broker record each said the temperature should be, states agree, disagree, or unknown on that requirement, and reports what the trailer unit sent. No driver input. No scanning. No extra paperwork.
Hand It Over.
At delivery the pack is complete. Share it with the people who need it, and keep it for the day someone asks.
Connections
Both Sides of the Handoff.
For each handoff, and for the temperature each side required, the pack sets the shipper's record beside the carrier's record and states agree, disagree, or unknown. Deterministic rules produce every answer, so the same inputs give the same answer. Missing data is shown as missing. It is never filled in.
The Shipper's Side: the Custody API
Shippers send Custody what their systems already know, over a secure REST API with webhooks. Our team works with theirs on the integration.
- Tenders and the carrier of record
- PO, BOL, PRO, and load numbers
- Facility events: load-out, seal applied, gate out, gate in
- Shipping documents
The Carrier's Side
Read with the carrier's approval, for that shipper's loads only. Nothing for the carrier to build.
- Carrier TMS
- ELD and GPS, used to establish arrival and departure
- Shipping documents and proof of delivery
Carrier of Record
Federal authority and insurance status, recorded at tender and again at pickup. It is a timestamped fact in the pack, never a score or a rating.
Signed and Timestamped
Events are append-only. Every finished pack is signed and stamped by an independent timestamp authority, so any later alteration is detectable.
Partner Devices and Reefer Units
Trailer door and temperature events, electronic seals, and cameras, read through the device maker's own API with the owner's approval. Connected reefer telematics today are Thermo King TracKing and ORBCOMM. If the equipment is already on the trailer, its readings can be in the pack, reported as air temperature at the unit with their source.
Coming Soon.
EDI
Tenders, status messages, and ship notices over the EDI connections you already run.
ValveRide Shift
Load events and cargo shift detection from the vehicle itself, written straight into the pack.
Connected Systems
The Systems the Platform Already Speaks To.
The ValveRide Platform has working connections to the systems below, so a carrier running any of them has nothing new to install.
ELD and Telematics
Samsara / Motive / Geotab / Isaac Instruments / Omnitracs
TMS and Dispatch
McLeod / Trimble / Alvys / Magnus
Refrigeration and Trailer Telematics
Thermo King TracKing / ORBCOMM
Dock Scheduling
Opendock
Running something else? Any system with an API can connect. Product and company names are trademarks of their owners. A name here means a working technical connection, not a partnership or an endorsement.