Fleetworthy
Fleetworthy is a North American fleet compliance, safety, and technology company (Madison, WI) that combines the Bestpass, Drivewyze, and related brands into a single integrated platform for commercial trucking fleets. Its products span safety and compliance management (driver and asset compliance with real-time alerts, Driver Qualification File management, DOT audit readiness, IFTA and Form 2290 tax filing), unified toll management with nationwide coverage and dispute resolution, and weigh-station bypass across 925+ inspection sites. Fleetworthy exposes a RESTful Compliance API through an Azure API Management developer portal (developer.fleetworthy.com) with three published APIs — Read Reports, Asset Management, and Driver Management — letting integrators retrieve report data and files and create, read, update, and delete asset and driver records to automate compliance workflows and sync with external systems.
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 Fleetworthy the way a machine reads it — 6 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 — Fleetworthy scores 35.3/100 (thin), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fleetworthy
Each block below is one kind of artifact we hold for Fleetworthy. 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 3
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.
Fleetworthy Read Reports API
Read-only API to retrieve compliance reports and their associated files for your fleet, exposed through the Fleetworthy Compliance API portal (Azure API Management).
Fleetworthy Asset Management API
Create, read, update, and delete asset (vehicle/equipment) information to sync fleet asset data with external systems, exposed through the Fleetworthy Compliance API portal.
Fleetworthy Driver Management API
Create, read, update, and delete driver records and driver compliance data, exposed through the Fleetworthy Compliance API portal.
Security Posture 3
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.
Resources
Every other property we hold for Fleetworthy — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fleetworthy · machine-readable index on apis.io