If you are building an AI agent that covers freight, the tender is where your demo becomes a liability question. Preparing a tender requires load context, carrier eligibility, rate sanity, and company policy — and executing one binds your customer to a carrier. Headless Haulbase exposes tendering as an explicit, approval-aware action so your agent can do the work without ever being the last line of defense.
The tender flow through the API
- 1Read the loadThe agent pulls current load state: stops, equipment, references, workflow position, and prior carrier activity.
- 2Prepare the tenderA prepare_tender command validates the carrier, rate context, and load readiness — with dry-run support for testing the decision.
- 3Get the policy answerThe response is explicit: allowed, approval_required, blocked, or missing_context. The agent always knows its standing before anything commits.
- 4Deliver the approval packetWhen approval is required, the system creates a reviewable packet — load, carrier, rate, evidence, and the agent's reasoning — for a human decision.
- 5Record the resultApproved or rejected, executed or expired: every step writes an audit record tied to the company, load, agent, and approver.
Built for machine callers
- Signed machine-to-machine requests identify the agent, company, load, and requested action.
- Idempotency keys make retries safe — a network blip never becomes a double tender.
- Duplicate and conflict detection answers at the API layer, before a human ever sees a bad packet.
- Approval rules are company policy, configured by the customer — not behavior your agent has to hardcode.