Submit a WorkWave Routing Engine Optimization API request for recurring pest/lawn treatment routes
domain: doc.wwre.workwave.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate against the WorkWave Routing Engine (WWRE) API
Build the waypoint list for the day's or week's recurring treatment stops
Submit the job to the Optimization API, including constraints like vehicle count and time windows
Retrieve the optimized single- or multi-day execution result
Feed the optimized stop order back into the dispatch/scheduling system
Known gotchas
WWRE is a separate WorkWave product/API from PestPac's own API and from WorkWave Route Manager (WWRM) -- each has distinct documentation and access processes
Optimization jobs can cover single or multiple execution days, so request payloads must specify the correct scope or results won't reflect the intended planning horizon
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?