Optimize a route via the Circuit for Teams (now Spoke) Public API

domain: developer.dispatch.spoke.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Note the rename: Circuit for Teams' former developer docs at developer.team.getcircuit.com now redirect to developer.dispatch.spoke.com, and the product/API is now branded "Spoke" — update any bookmarked "Circuit" URLs.
  2. Generate an API key from your Spoke Dispatch settings page under Integrations > API.
  3. Authenticate with the key as HTTP Basic (the key as username, empty password) or as a Bearer token against the base https://api.spoke.com/public/v1.
  4. Import stops into a Plan (via the Stops or Batch Import Stops endpoints), then call the Plan's optimize endpoint, which returns an operation you poll for the result rather than an inline response.
  5. Once optimized, a Plan can contain multiple Routes, each associated with a Driver; call the distribute endpoint to send each driver their finalized route.
  6. Respect the API's rate limits: 5 req/s for write endpoints (1 req/s for single driver creation — use Batch Import Drivers instead), 10 req/s for reads, and just 3 req/min for optimize/re-optimize calls given their long-running nature.

Known gotchas

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans