OnFleet's public REST API is self-serve with docs at docs.onfleet.com, scoped API keys, and 14+ HMAC-signed webhook events. Official SDKs cover Node, Python, and Ruby. A hard 20 requests per second org-wide cap forces batching on bulk jobs, and route optimization is Enterprise-plan only.
OnFleet scores A on Supergood's API Report Card. OnFleet's public REST API is self-serve with docs at docs.onfleet.com, scoped API keys, and 14+ HMAC-signed webhook events. Official SDKs cover Node, Python, and Ruby. A hard 20 requests per second org-wide cap forces batching on bulk jobs, and route optimization is Enterprise-plan only.
OnFleet has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Onfleet is a cloud-based last-mile delivery orchestration platform founded in 2012 by David Vetrano, Mikel Carmenes Cavia and Khaled Naim out of Stanford and headquartered in San Francisco, CA.
Vertical: Fleet / Trucking / Logistics, specifically last-mile delivery dispatch and route optimization. Dispatchers, operations managers and drivers use Onfleet to: import or create delivery/pickup tasks (via dashboard, CSV, API or e-commerce integration); auto-dispatch and route-optimize across internal drivers, teams and outsourced courier partners; track drivers in real time with live GPS and dynamic ETAs; communicate with customers via branded SMS notifications, live tracking pages and two-way driver-customer chat; capture proof of delivery with photos, signatures, barcode scans and ID/age verification; manage compliance with custom completion requirements and manifests; and analyze delivery performance across drivers, teams, brands and regions.
8/10 within last-mile delivery dispatch SaaS. Onfleet is consistently ranked as a category leader on G2 and Capterra alongside Bringg, DispatchTrack, Routific, Tookan, Track-POD, OptimoRoute, Locus and NextBillion.ai.
Onfleet is the system of record for last-mile delivery operations across its customer base.
Founded 2012 in San Francisco.
**20 requests/second** is a hard org-wide ceiling, large back-fills or multi-team integrators must use batch endpoints or staggered jobs to avoid 429s and bans. Authentication is **HTTP Basic Auth with an API key**, no OAuth 2.0 / SSO flow for third-party app builders. Full sourced list under Sources below.
Common alternatives include Bringg, DispatchTrack, Routific, OptimoRoute, Tookan (Jungleworks), Track-POD. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. As of August 2026 there is no official OnFleet MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. OnFleet doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.