OptimoRoute MCP integration for AI agents.
Connect AI agents to OptimoRoute through 3 structured actions, including get orders, create or update orders, and delete orders. Review authentication, input…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the OptimoRoute integration exposes
The OptimoRoute Agent App exposes 3 provider-backed actions for location and productivity work. Its current contract lets an authorized agent retrieve one or more optimoroute orders by orderno or id, create, update, merge, or sync one or more optimoroute orders in one request, and delete one or more optimoroute orders by orderno or id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected OptimoRoute account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real OptimoRoute capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_ordersREADRetrieve one or more OptimoRoute orders by orderNo or id.
INPUTS: orders
create_or_update_ordersWRITECreate, update, merge, or sync one or more OptimoRoute orders in one request.
INPUTS: orders
delete_ordersHIGH IMPACTDelete one or more OptimoRoute orders by orderNo or id.
INPUTS: orders / deleteMultiple / forceDelete
INPUT CONTRACTS
Know what the action needs before it runs.
get_orders
ordersREQUIRED- The list of orders to retrieve from OptimoRoute.
create_or_update_orders
ordersREQUIRED- The list of orders to write to OptimoRoute.
delete_orders
ordersREQUIRED- The list of orders to delete from OptimoRoute.
deleteMultipleOPTIONAL- Whether delete_orders should remove all matches when one order selector matches multiple orders.
forceDeleteOPTIONAL- Whether delete_orders should ignore live-plan delete restrictions when possible.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Orders
Retrieve one or more OptimoRoute orders by orderNo or id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_ordersControl Create Or Update Orders
Create, update, merge, or sync one or more OptimoRoute orders in one request. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_or_update_ordersVerify with Create Or Update Orders
Create, update, merge, or sync one or more OptimoRoute orders in one request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_or_update_ordersSAFETY BOUNDARY
Operate OptimoRoute with explicit limits
- Authorize OptimoRoute with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_orders` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in OptimoRoute rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the OptimoRoute task completed successfully.
CONNECTION MODEL
API key
OptimoRoute API key passed with the key query parameter. Enable Web Service API and copy the generated key in Administration > Settings > WS API: https://optimoroute.com/api/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by OptimoRoute.