Route4Me MCP integration for AI agents.
Connect AI agents to Route4Me through 3 structured actions, including list optimizations, create optimization, and delete optimizations. Review authenticatio…
- 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 Route4Me integration exposes
The Route4Me Agent App exposes 3 provider-backed actions for location and productivity work. Its current contract lets an authorized agent list route4me optimization problems, or fetch one optimization by its id, create a route4me optimization problem from parameters and destination addresses, and delete one or more route4me optimization problems by 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 Route4Me account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Route4Me capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_optimizationsREADList Route4Me optimization problems, or fetch one optimization by its ID.
INPUTS: optimizationProblemId / state / limit / offset / startDate
create_optimizationWRITECreate a Route4Me optimization problem from parameters and destination addresses.
INPUTS: parameters / addresses
delete_optimizationsHIGH IMPACTDelete one or more Route4Me optimization problems by ID.
INPUTS: optimizationProblemIds
INPUT CONTRACTS
Know what the action needs before it runs.
list_optimizations
optimizationProblemIdOPTIONAL- The optimization problem ID to fetch directly.
stateOPTIONAL- The optimization state filter documented by Route4Me.
limitOPTIONAL- The maximum number of optimization problems to return.
offsetOPTIONAL- The result offset used for pagination.
startDateOPTIONAL- An ISO date string in YYYY-MM-DD format.
create_optimization
parametersOPTIONAL- The optimization parameters object accepted by Route4Me.
addressesOPTIONAL- The destination list to optimize.
delete_optimizations
optimizationProblemIdsOPTIONAL- The optimization problem IDs to delete.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Optimizations
List Route4Me optimization problems, or fetch one optimization by its ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_optimizationsControl Create Optimization
Create a Route4Me optimization problem from parameters and destination addresses. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_optimizationVerify with Create Optimization
Create a Route4Me optimization problem from parameters and destination addresses. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_optimizationSAFETY BOUNDARY
Operate Route4Me with explicit limits
- Authorize Route4Me 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_optimizations` 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 Route4Me rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Route4Me task completed successfully.
CONNECTION MODEL
API key
Route4Me API key passed as the api_key query parameter.
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 Route4Me.