Your dispatcher,
multiplied.
Not a chatbot — an operator. fOS wraps any frontier model in 60+ proprietary freight tools: it searches and bids across seven exchanges, prices every chain to the cent, runs the negotiation, and now takes the dispatch call itself.
Models are commodities. The freight layer is not.
It doesn't suggest. It does.
Pick a dispatch scenario and watch the agent loop play out — every thought, every tool call, every structured result. This is the real harness: the tool names and classifications are pulled straight from production.
Read badges: read never mutates · write mutating, can require confirmation · ui renders an interface. fOS classifies every tool, so writes and auth are gated by design.
Sixty-plus tools, not sixty prompts.
Every capability fOS has is a typed, classified tool with a strict input schema — built and maintained by us, not improvised by the model. Filter by what you need.
Fleet & vehicles
Load search & bidding
Chain economics
Market intelligence
Outreach & CRM
Live negotiation
Gmail & Calendar
Session & context
It takes the call.
fOS's voice layer runs a full real-time loop on every call — listening, reasoning over the same tools, and speaking back inside a sub-second budget. The negotiation tools fire live, and anything outside its mandate escalates to a human instantly over SMS.
Live call state
One harness. Every surface, any model.
The same typed tools compose into whichever surface you're shipping — and run on whichever model you trust. MCP-native for Claude, with thin adapters for everyone else.
Three surfaces
Five providers
Plug fOS into your own stack.
Connect over our public MCP server in a single config block, or import the tools directly and hand them to any model. Same envelope, same classifications, everywhere.
# Claude Desktop / any MCP client
{
"mcpServers": {
"tovr-fos": {
"command": "npx",
"args": ["-y", "@tovr/nova-mcp"],
"env": { "TOVR_API_KEY": "sk_live_…" }
}
}
}
# → 60+ dispatch tools + skills, instantly available01Classified by default
Every tool is tagged READ_ONLY, WRITE, AUTH_ONLY or UI_ONLY. Mutating actions can demand a CONFIRMATION_REQUIRED step — the model can't quietly place a bid.
02Typed schemas, real backends
Inputs are validated with Zod; tools run against live exchange adapters and your Supabase data with encrypted, vaulted credentials — not scraped guesses.
03Generative UI, not walls of text
Results carry an internal_instruction so the agent renders a card and stays terse, instead of reading numbers back at the user.
Put an agent on the desk.
See fOS run your real lanes, your real shippers — on the model you choose.
Tool names, classifications and surfaces shown are drawn from fOS's production harness; Gmail & Calendar tool identifiers are representative of that group. Agent traces and the live-call panel are scripted reconstructions using realistic data, for demonstration.