The Loadcircle assistant answers operational questions and performs gated actions using the same engines and rules as the REST API. It is rule-based โ no API key, no external model, no data leaves the deployment.
POST /api/v1/assistant with { "message": "..." }| Intent | Example | Result |
|---|---|---|
| Overview | overview | jobs, workers, exceptions, routes summary |
| Jobs | how many active jobs / job-001 / complete job-001 | list, detail, or state transition |
| Workers | available workers | available driver list |
| Price | price London to Birmingham | suggested price, bid range, confidence |
| Lane | lane london-birmingham | history, carriers, margin |
| Margins | margins | all lane margins and seasonal variation |
| Fraud | fraud signals | anomaly signals per lane |
| Auto-bid | auto bid c-001 on london-birmingham | bid if confidence > 0.75, acceptance > 0.85, trusted |
| Exceptions | open exceptions / resolve exception exc-123 | unresolved list or resolution |
| Help | help | intent guide |
Every action the assistant takes is logged to the agent audit log (GET /api/v1/hermes/log) with the same logAgentAction path used by the Hermes engine, and every auto-bid goes through the same gating as the REST endpoint:
auto-bid fires only if ALL hold: confidenceScore > 0.75 acceptanceProbability > 0.85 carrier is trusted bid amount = suggestedBidMin
POST /api/v1/assistant
{ "message": "price London to Birmingham" }
โ { "reply": "london-birmingham: suggested customer price ยฃ596 ยท ...",
"performed": ["generate_signal:london-birmingham"],
"data": { "signal": { ... } } }london-birminghamc-001