{
  "id": "p_kWXbHI03jgOybW_e",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_kWXbHI03jgOybW_e",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You run maintenance for a mixed fleet. Some of it is road vehicles, but part of your world is vessels, or aircraft, or railcars. You are looking for software with an API that can tie your service work together, so you go to the APIs.io catalog and open a capability called Fleet Maintenance Management.\n\nThe definition looks like it was written for you. It describes preventive, corrective and heavy maintenance of vehicles, vessels, aircraft and rolling stock. It sits under Fleet & Mobile Asset Management in the Transportation & Logistics model, which comes from the Turbo EA capability model under CC BY 4.0. The catalog maps 21 API surfaces from 6 providers to it. That sounds like a healthy market.\n\nThen you read the providers, and the post behind this story points out what the definition hides: every one of the six works on road vehicles. None of them is rated strong. Capabilities themselves are not scored in the catalog; the providers that land on them are, and these six land in the middle and lower bands.\n\nDecisiv leads, with a Kin Score of 52.2, a developing band, and an Agent Readiness of 49.0, which the catalog labels agent-native. It contributes 10 of the 21 surfaces, nearly half. Its tags read like a service shop's workflow: cases, case line items, parts, and technician stories. That is the shape of corrective maintenance, and Decisiv is the only provider here that models it in that much detail.\n\nAutomile follows at 45.9, developing, with 4 APIs covering vehicle inspections and defect comments. Lytx scores 40.8, developing, with 2 APIs for DVIR from DriveCam and maintenance records from GO9. Then come three thin-band providers: Revvo at 36.0 with tire operations, Ryder System at 35.4 with service history, and Samsara at 31.8 with defects, DVIRs and maintenance across 3 APIs.\n\nTwo patterns stand out. The first is that inspection is the common denominator. Automile, Lytx and Samsara all land through driver vehicle inspection reports and defects. The pre-trip inspection is the part of fleet maintenance that regulation forces into software, so it is the part that has APIs.\n\nThe second is that the telematics leader is last. Samsara is the most recognizable name on the list, yet it has the lowest Kin Score. Its maintenance surface is three tag groups. Lytx, a smaller video telematics company, scores 9 points higher and posts more than double Samsara's Agent Readiness, 48.0 to 18.6.\n\nNow you look below the parent capability, hoping the breakdown will help. It has four children: Preventive Maintenance Scheduling, Corrective Maintenance Execution, Mandatory Inspection Compliance, which includes airworthiness and seaworthiness directives, and Heavy Maintenance and Overhaul, which includes dry-docking and heavy checks. Every one of them has 0 providers and 0 APIs.\n\nThat is the turn in this post, and it is the catalog being straight about its own record. The six providers map to the parent only, not to any of its parts. Nothing in the catalog lands on the aircraft, vessel or rail side of the definition. Even in rail, where Cedarai and Railinc publish railcar data, nothing reaches this capability. The wide definition promised more than the catalog's own mapping delivers.\n\nSo you adjust what you expected. A capability page with 21 surfaces and 6 providers is not evidence that your whole fleet is covered; it is evidence about trucks.\n\nWhat you take away is practical. If you maintain trucks, start with Decisiv for service events, and look at Lytx or Samsara for inspections. If you maintain aircraft, ships or railcars, this capability has nothing for you yet, and you should not read the breadth of its definition as coverage. If your real interest is predicting failures rather than recording them, the post points you to the Predictive Maintenance use case for the other side of the same problem.\n\nRead the original: https://apis.io/2026/11/14/fleet-maintenance-covers-ships-aircraft-and-rolling-stock-and-all-six-providers-are-trucks/",
  "title": "You maintain a fleet, and the maintenance capability turns out to be a trucks-only story",
  "topics": [
    "fleet-maintenance",
    "api-catalog",
    "transportation",
    "capability-coverage"
  ],
  "published_at": "2026-11-14T16:11:16.559Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}