Obtain a Routific API key and include it in every request as the Authorization: Bearer YOUR_API_KEY header with Content-Type: application/json.
For jobs with 60 or fewer stops, POST your fleet and visit data to https://api.routific.com/v1/vrp; for larger jobs use https://api.routific.com/v1/vrp-long to avoid timeouts.
Structure the request body with a visits object (keyed by stop ID, each with location lat/lng and optional time_window start/end, duration, and load) and a fleet object (keyed by vehicle ID, each with start/end location and optional shift times and capacity).
For vrp-long, the response returns a job_id; poll GET https://api.routific.com/v1/jobs/{job_id} at intervals (default 1000 ms) until status is finished.
Parse the solution object: each vehicle key maps to an ordered array of stops with arrival_time, finish_time, and any unserved visits; surface unserved stops for manual reassignment.
Push the optimized stop sequence back to your dispatch system or delivery app for driver navigation; re-submit to /vrp-long with updated inputs if real-time changes occur during the day.
Known gotchas
Time windows must be specified in HH:MM format relative to the fleet shift start — mixing absolute timestamps with relative windows produces silently incorrect routes.
Routific bills per optimization request; avoid tight polling loops or unnecessary re-optimizations during a single shift to control costs.
Unserved visits in the solution are not errors — they indicate stops that cannot fit within vehicle capacity or time constraints; always check and handle this array before dispatching.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp