Meet fOS
fOS is "your dispatcher, multiplied" — an operator, not a chatbot. It runs the freight loop (find, price, bid, negotiate, execute, learn) using the same tools and economics as the TOVR platform, across web, voice, and external assistants.
fOS is the AI dispatcher — "your dispatcher, multiplied." It is an operator, not a chatbot: its job is not to chat, but to move real freight deals through a real loop, using the same tools and the same economics a human dispatcher would. It sits on top of the TOVR platform and consumes APEX — it does not invent its own facts.
What "operator, not a chatbot" means
A chatbot answers questions. fOS does the job: it searches for loads, prices a chain, makes an offer, negotiates a rate on a live call, confirms a win, and learns from the outcome. Every capability it has is a tool wired to a concrete platform action or a decision-grade read — never free-form text pretending to be data. If fOS states a chain's profit, that number came from the cost engine; if it quotes a market rate, that came from APEX. See Cost grounding.
The mission loop
Everything fOS does serves one loop:
find → price → bid → negotiate → execute → learn
A tool earns its place in fOS only if it moves a deal through this loop, produces a read that changes the very next action, is a real reference table a dispatcher consults, or is plumbing a surface needs to function. The loop is the organizing principle of the whole system — it is detailed in The mission loop.
fOS versus TOVR versus APEX
It is worth being precise about the boundary:
- TOVR is the platform — the domain, the cost engine, freight chains, compliance, procurement. It is the source of truth.
- APEX is the market-price service. It answers "what does this lane pay?"
- fOS is the operator on top. It drives the platform: it decides what to do next and invokes the tools that do it. It holds no economics of its own; it reads TOVR and APEX.
How fOS is built, briefly
fOS is a single tool layer that runs unchanged across every channel. Tools return data plus
render hints; each channel decides how to present it. That is why the same get_chain_economics
call becomes an interactive card in the web app, spoken numbers on a voice call, or a JSON
result for an external assistant. The channels are covered in
Surfaces; the tools in
Tool arsenal.
Trust and safety
Because fOS can take real actions — make offers, bill commission — it is built with explicit guardrails: money-moving actions are idempotent and require confirmation, under-specified requests are clarified rather than guessed, and the walk-away price floor is never revealed to a counterparty. These are covered in Guardrails.
Where to go next
- The loop, stage by stage: The mission loop.
- Why fOS never fabricates a number: Cost grounding.
- The safety model: Guardrails.
- The channels fOS runs on: Surfaces.
Known gaps & limitations
Honest limitations of the current APEX service — the unpaginated corridors endpoint, per-instance rate limiting, the inert outlier detector, and the aggregation refresh cadence. Documented so consumers can plan around them.
The mission loop
fOS runs one loop — find, price, bid, negotiate, execute, learn. Every tool serves a stage of it. This page walks the loop stage by stage and explains the inclusion principle that decides what earns a place as a tool.