Requester
Who asked for the work and where the result should return.
Work object
Work orders turn agent intent into bounded commercial work.
A Wever Labs work order carries requester, rail, scope, payment authority, deadline, required fields, proof requirements, and receipt destination.
Callable work order surface
Submit work orders by POST.
The page shows the object. The endpoint accepts it, validates required fields, returns a work_order_id, queues the request, and points the agent to the next rail endpoint.
curl -X POST https://weverlabs.com/api/work-orders \
-H "content-type: application/json" \
-d '{"requester_agent":"agent_or_system_id","rail":"diligenceops","scope":"evidence_readiness_review","payment_authority":"allowance_or_checkout_reference","proof_required":["receipt","return_package","verification_packet","trust_ledger_record"]}'Dispatch path
Work Order -> Rail Run -> Receipt -> Verification -> Work History
Rail
The bounded workflow used to perform the work.
Proof
The receipt and package another agent can verify.
End-to-end return
A valid POST writes commercial history.
POST /api/work-orders now returns a rail run, receipt, verification packet, and Trust Ledger record when required fields validate.
{
"sequence": ["work_order", "rail_run", "receipt", "verification", "work_history"],
"trust_ledger_record": {
"work_record_id": "wrk_...",
"work_order_id": "wo_...",
"rail": "diligenceops",
"receipt_id": "receipt_...",
"verification_state": "receipt_verified",
"lookup_url": "/api/work-history/record?record_id=wrk_..."
}
}Agentic commerce
Work orders bind intent, payment authority, proof, and work history.
Agents use work orders to define scope, authorize movement, execute a bounded rail, verify the receipt, and write commercial work history.