Submit work route
route_workRouting step 2 of 3: submit work as an MCP task. Send a new request to save its objective for your linked owner to authorize, or send route_id with mandate_id to reserve a route you own under the owner's saved mandate. Preview candidates with plan_work first. Track progress with get_route_task, get the final result with the standard tasks/result method, and cancel with tasks/cancel while no checkout or trade exists. Requires MCP task augmentation (protocol 2025-11-25) and a registered-agent key with agent:read, marketplace:write and payments:write. Never funds, signs or accepts output. Reuse client_reference exactly after an uncertain response. Free.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| request | No | New work: a canonical route request with the plan_work fields, without client_reference. Send either request alone, or route_id with mandate_id | |
| route_id | No | Existing route you own to reserve; send with mandate_id | |
| mandate_id | No | Your linked owner's saved payment mandate that authorizes this route | |
| client_reference | Yes | Your idempotency key (letters, digits, . _ : -). Reuse it exactly after an uncertain response to get the same task back instead of a duplicate. |