Circuit
Circuit, operating under the Spoke brand, provides a logistics platform that enables businesses to manage deliveries, drivers, and dispatch operations through a modern API. The service offers tools for route planning, driver tracking, and real‑time delivery analytics, supporting integration with third‑party systems via RESTful endpoints. Circuit’s platform is designed for scalability and includes comprehensive documentation, SDKs, and support resources for developers building transportation and logistics solutions.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Circuit the way a machine reads it — 19 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Circuit scores 35.9/100 (thin), with a separate agent-readiness read of 25/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
OpenAPI spec found at https://developer.dispatch.spoke.com/openapi-v1.json belongs to Spoke, not Circuit.
The documentation is public — a person can read it, but a machine cannot. This one is Circuit's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://developer.dispatch.spoke.com/openapi-v1.json→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from Circuit's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/getcircuit-com/"
title="Circuit on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/getcircuit-com.svg"
alt="Circuit Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/getcircuit-com/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/getcircuit-com/"
title="Circuit on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/getcircuit-com/card.svg"
alt="Circuit Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Circuit
Each block below is one kind of artifact we hold for Circuit. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Circuit Couriers API
Look up the couriers that deliver your orders.
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 Orders API
Create, submit, and track delivery orders, and download their printable PDF labels.
Circuit Pickup Locations API
Look up the pickup locations your orders ship from.
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 within the panel for all 14 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Getcircuit Com Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Circuit API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Circuit — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/getcircuit-com · machine-readable index on apis.io
This is an independent, third-party profile of Circuit, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.