Circuit

Circuit (operating publicly as Spoke; legal entity Circuit Routing Limited) builds last-mile delivery route-optimization software. Its products are Route Planner, a free driver app for uploading stops, optimizing multi-stop routes and navigating; Dispatch, a multi-driver delivery-management platform with route planning, live tracking and proof of delivery for courier operations; and Connect, a marketplace that lets retailers discover local couriers and track deliveries. The Spoke Public API (formerly the Circuit for Teams API) is an HTTP/JSON API that lets teams manage plans, stops, unassigned stops, drivers, depots, routes, members and long-running operations programmatically, optimize and distribute plans across drivers, run full-text stop search with a filtering DSL, and subscribe to webhook events for delivery workflows.

Circuit publishes 11 API contracts indexed on the APIs.io network, including Depots API, Drivers API, Live Plans API, and 8 more. Tagged areas include Company, Delivery, Logistics, Last Mile Delivery, and Route Optimization.

The Circuit catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Circuit’s developer surface includes authentication, documentation, API reference, getting-started guide, code examples, support, pricing, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.1/100 developing ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 published contracts 3 Agent Skills

Company Delivery Logistics Last Mile Delivery Route Optimization Dispatch Couriers Fleet Management Proof of Delivery Field Service Management

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Transport Operations Management

BC-2420

Live PlansLive StopsPlansStops

POST /plans/{planId}:reoptimize POST /plans/{planId}:redistribute POST /plans/{planId}/stops:liveCreate POST /plans/{planId}/stops/{stopId}:liveUpdate

Supply Chain Management

BC-520

DepotsRoutes

GET /routes/{routeId} GET /routes GET /routes/{routeId}/stops POST /depots

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 51.1/100 · developing

Contract Quality 12.4 / 21

Developer Ergonomics 9.6 / 17

Access Clarity 5.4 / 17

Operational Transparency 8.7 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/circuit/"><img src="https://apis.io/badge/circuit/card.svg" alt="Circuit on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 31.6 — up to +13.7 composite points
Contract Governance scores 4.5 — up to +11.5 composite points
Contract Quality scores 58.5 — up to +10.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/circuit/apis.yml: open an issue on github.com/api-evangelist/circuit to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 11

Individual APIs this provider publishes, each with its own machine-readable definition.

Circuit Depots API

Endpoints to operate on [Depots](/docs/models/depot) resources. This resource is currently read-only on the API.

Circuit Drivers API

Endpoints to operate on [Drivers](/docs/models/driver) resources.

Circuit Live Plans API

Endpoints to operate on [Plans](/docs/models/plan) resources when it's pending re-optimization and re-distribution. You must use these endpoints to apply the changes when any [L...

Circuit Live Stops API

Endpoints to operate on [Stop](/docs/models/stop) resources when the plan is already optimized and therefore not writable. All the endpoints return the field `pending`. This fie...

Circuit Members API

Endpoints to operate on Members resources.

Circuit Operations API

Endpoints to operate on [Operations](/docs/models/operation) resources.

Circuit Plans API

Endpoints to operate on [Plans](/docs/models/plan) resources.

Circuit Routes API

Endpoints to operate on [Routes](/docs/models/route) resources. This resource is currently read-only on the API.

Circuit Stops API

Endpoints to operate on [Stop](/docs/models/stop) resources. For any [Plans](/docs/models/plan) created before 2023-04-01 the stop collections and all related operations will no...

Circuit Team API

Endpoints to retrieve [Custom Stop Properties](/docs/models/customStopProperty).

Circuit Unassigned Stops API

Endpoints to operate on [Unassigned Stop](/docs/models/unassignedStop) resources.

Scroll for all 11

Open Collections 11

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Spoke Depots API

OPEN COLLECTION

Spoke Depots Drivers API

OPEN COLLECTION

Spoke Depots Live Plans API

OPEN COLLECTION

Spoke Depots Live Stops API

OPEN COLLECTION

Spoke Depots Members API

OPEN COLLECTION

Spoke Depots Operations API

OPEN COLLECTION

Spoke Depots Plans API

OPEN COLLECTION

Spoke Depots Routes API

OPEN COLLECTION

Spoke Depots Stops API

OPEN COLLECTION

Spoke Depots Team API

OPEN COLLECTION

Spoke Depots Unassigned Stops API

OPEN COLLECTION

Scroll for all 11

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Set up depots and drivers

AGENT SKILL

Build, optimize and distribute a delivery plan

AGENT SKILL

Search stops with the filtering DSL

AGENT SKILL

Rate Limits 1

Documented rate limits and quota policies.

Circuit Rate Limits

6 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Circuit Webhooks

ASYNCAPI

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Circuit V1 Overlay

3 actions · update · circuit-v1-openapi-original.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Circuit Authentication

http · 2 schemes

SECURITY

Circuit Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Webhooks

ErrorCatalog

Conventions

Lifecycle

DataModel

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Examples

Examples

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Learn 1

Tutorials, courses, talks, and written guidance

YouTube

YouTube

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

Deprecation

RateLimits

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

LinkedIn

Twitter

Twitter

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: circuit
name: Circuit
description: Circuit (operating publicly as Spoke; legal entity Circuit Routing Limited) builds last-mile delivery route-optimization
  software. Its products are Route Planner, a free driver app for uploading stops, optimizing multi-stop routes and navigating;
  Dispatch, a multi-driver delivery-management platform with route planning, live tracking and proof of delivery for courier
  operations; and Connect, a marketplace that lets retailers discover local couriers and track deliveries. The Spoke Public
  API (formerly the Circuit for Teams API) is an HTTP/JSON API that lets teams manage plans, stops, unassigned stops, drivers,
  depots, routes, members and long-running operations programmatically, optimize and distribute plans across drivers, run
  full-text stop search with a filtering DSL, and subscribe to webhook events for delivery workflows.
url: https://raw.githubusercontent.com/api-evangelist/circuit/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: stub
x-tier-reason: portfolio-lead
x-rebrand: getcircuit.com now redirects to spoke.com; public brand is Spoke, legal entity Circuit Routing Limited
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://spoke.com/favicon.ico
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
tags:
- Company
- Delivery
- Logistics
- Last Mile Delivery
- Route Optimization
- Dispatch
- Couriers
- Fleet Management
- Proof of Delivery
- Field Service Management
tags_raw:
- Company
- Delivery
- Logistics
- Last Mile
- Route Optimization
- Dispatch
- Courier
- Fleet
- Proof of Delivery
- Field Service
apis:
- aid: circuit:circuit-depots-api
  name: Circuit Depots API
  description: 'Endpoints to operate on [Depots](/docs/models/depot) resources.


    This resource is currently read-only on the API.'
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Depots
  properties:
  - type: OpenAPI
    url: openapi/circuit-depots-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-drivers-api
  name: Circuit Drivers API
  description: Endpoints to operate on [Drivers](/docs/models/driver) resources.
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Drivers
  properties:
  - type: OpenAPI
    url: openapi/circuit-drivers-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-live-plans-api
  name: Circuit Live Plans API
  description: 'Endpoints to operate on [Plans](/docs/models/plan) resources when it''s pending re-optimization and re-distribution.


    You must use these endpoints to apply the changes when any [Live Stops](#tag/Live-Stops) request returns `pending = true`.'
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Live Plans
  properties:
  - type: OpenAPI
    url: openapi/circuit-live-plans-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-live-stops-api
  name: Circuit Live Stops API
  description: 'Endpoints to operate on [Stop](/docs/models/stop) resources when the plan is already optimized and therefore
    not writable.


    All the endpoints return the field `pending`. This field indicates whether the

    change has been applied to the plan or if it''s pending a new optimization and distribution. On `pending = true`,

    you must use the [re-optimize](#tag/Live-Plans/operation/reoptimizePlan) and [re-distribute](#tag/Live-Plans/operation/redistributePlan)

    endpoints to apply the changes to the plan.'
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Live Stops
  properties:
  - type: OpenAPI
    url: openapi/circuit-live-stops-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-members-api
  name: Circuit Members API
  description: Endpoints to operate on Members resources.
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Members
  properties:
  - type: OpenAPI
    url: openapi/circuit-members-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-operations-api
  name: Circuit Operations API
  description: Endpoints to operate on [Operations](/docs/models/operation) resources.
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags: []
  tags_raw:
  - Operations
  properties:
  - type: OpenAPI
    url: openapi/circuit-operations-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-plans-api
  name: Circuit Plans API
  description: Endpoints to operate on [Plans](/docs/models/plan) resources.
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Plans
  properties:
  - type: OpenAPI
    url: openapi/circuit-plans-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-routes-api
  name: Circuit Routes API
  description: 'Endpoints to operate on [Routes](/docs/models/route) resources.


    This resource is currently read-only on the API.'
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Routes
  properties:
  - type: OpenAPI
    url: openapi/circuit-routes-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-stops-api
  name: Circuit Stops API
  description: 'Endpoints to operate on [Stop](/docs/models/stop) resources.


    For any [Plans](/docs/models/plan) created before 2023-04-01 the stop

    collections and all related operations will not be available.


    For any operations here you will need a Plan ID beforehand. You can retrieve an

    existing Plan by [listing your Plans](#tag/Plans/operation/listPlans) or you can

    [create a new one](#tag/Plans/operation/createPlan).'
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Stops
  properties:
  - type: OpenAPI
    url: openapi/circuit-stops-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-team-api
  name: Circuit Team API
  description: Endpoints to retrieve [Custom Stop Properties](/docs/models/customStopProperty).
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Team
  properties:
  - type: OpenAPI
    url: openapi/circuit-team-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
- aid: circuit:circuit-unassigned-stops-api
  name: Circuit Unassigned Stops API
  description: Endpoints to operate on [Unassigned Stop](/docs/models/unassignedStop) resources.
  humanURL: https://developer.dispatch.spoke.com/
  baseURL: https://api.spoke.com/public/v1
  tags:
  - Unassigned Stops
  properties:
  - type: OpenAPI
    url: openapi/circuit-unassigned-stops-api-openapi.yml
  - type: APIReference
    url: https://developer.dispatch.spoke.com/api/v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/circuit-capability-edges.yml
  name: Circuit Business Capability Map
- type: DomainSecurity
  url: security/circuit-domain-security.yml
- type: Authentication
  url: authentication/circuit-authentication.yml
- type: Website
  url: https://spoke.com/
- type: DeveloperPortal
  url: https://developer.dispatch.spoke.com/
- type: Documentation
  url: https://developer.dispatch.spoke.com/
- type: APIReference
  url: https://developer.dispatch.spoke.com/api/v1
- type: GettingStarted
  url: https://developer.dispatch.spoke.com/docs/v1/api-examples
- type: Examples
  url: https://developer.dispatch.spoke.com/docs/v1/api-examples
- type: Support
  url: https://help.spoke.com/
- type: Pricing
  url: https://help.spoke.com/en/collections/385323-spoke-help-products-pricing
- type: TermsOfService
  url: https://spoke.com/terms
- type: PrivacyPolicy
  url: https://spoke.com/privacy
- type: StatusPage
  url: https://status.spoke.com/
- type: Deprecation
  url: lifecycle/circuit-lifecycle.yml
- type: OpenAPI
  url: openapi/_original/circuit-v1-openapi-original.json
- type: Webhooks
  url: asyncapi/circuit-webhooks.yml
- type: ErrorCatalog
  url: errors/circuit-error-codes.yml
- type: Conventions
  url: conventions/circuit-conventions.yml
- type: RateLimits
  url: rate-limits/circuit-rate-limits.yml
- type: Lifecycle
  url: lifecycle/circuit-lifecycle.yml
- type: DataModel
  url: data-model/circuit-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/circuit-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/circuit-llms.txt
- type: Conformance
  url: conformance/circuit-conformance.yml
- type: ChangeLog
  url: changelog/circuit-changelog.yml
- type: Overlay
  url: overlays/circuit-v1-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/spoke-delivery/
- type: Twitter
  url: https://x.com/SpokeDelivery
- type: YouTube
  url: https://www.youtube.com/@Spokeapp
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Circuit API — frequently asked questions

Does Circuit have an API?

Yes. APIs.io lists 11 APIs from Circuit, including Circuit Depots API, Circuit Drivers API and Circuit Live Plans API, and 8 more.

Is there an OpenAPI specification for the Circuit API?

Yes. APIs.io indexes 11 OpenAPI specifications for Circuit, each linked for download from this page.

How do I authenticate with the Circuit API?

Circuit uses bearer-token authentication (http · 2 schemes). The details are profiled on APIs.io as Circuit Authentication.

Is the Circuit API ready for AI agents?

Circuit has a Kin Score of 51.1 out of 100 (developing) and an Agent Readiness score of 26.8 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/circuit"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/circuit/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/circuit/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.