Assistant Guide

This guide is for operators using the Loadcircle assistant day-to-day. It explains what the assistant can do, what it will never do without the right conditions, and how to audit what it did.

Reading the answers

The assistant is read-only until you ask it to perform an action. Read-only answers cover:

Overview — counts of jobs, workers, exceptions, routes
Pricing — suggested customer price, bid range, confidence per lane
Margins & fraud — lane margins and anomaly signals
Status — any job, worker, or exception by ID

Performing actions

Say this	What happens
complete job-001	Job transitions to COMPLETED
resolve exception exc-001	Exception marked resolved
price Bristol to Cardiff	Generates a pricing signal for the lane
auto bid c-001 on london-birmingham	Places a bid only if all gates pass

Auto-bid gating

The assistant never bypasses the pricing engine's rules. A bid is placed only when:

lane confidence score > 0.75,
carrier acceptance probability > 0.85,
the carrier is marked trusted.

Otherwise it explains which gate failed (for example “acceptance 0.35 below 0.85”). This matchesPOST /api/v1/bid/auto exactly.

Audit trail

Every action is logged to the agent activity log with the agent name assistant, the action performed, the entity targeted, and a timestamp. Review it underAgents in the Console or via GET /api/v1/hermes/log.

If an auto-bid was placed, the log entry includes the lane, carrier, and bid amount so you can reconcile it against the pricing panel.

Good practice

Quote the exact lane slug (london-birmingham) or give both towns (price London to Birmingham)
Use carrier IDs (c-001) when bidding
Confirm suspicious pricing with the Fraud signals intent before acting