ISAAC Instruments
ISAAC Instruments is a Canadian provider of in-cab technology and fleet management for the trucking industry - electronic logging devices (ELD), telematics, hours-of-service (HOS) compliance, driver workflow, messaging, and fuel/performance analytics, delivered as a fully managed hardware-plus-software platform. ISAAC runs an "Open Platform" with a documented API that lets fleets and 80+ integration partners (TMS/dispatch, maintenance, fuel tax, visibility, safety/compliance) share ISAAC data with their chosen vendors. API access is partner-gated - vendors apply through the ISAAC partner program and the full API Guide and reference live behind the ISAAC InRealTime portal and Client Center rather than on a public developer site. The API surface documented here is modeled from ISAAC's public platform and partner materials; exact endpoints, base URLs, and authentication are provisioned to approved partners.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles ISAAC Instruments the way a machine reads it — 9 machine-readable artifacts across 8 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 — ISAAC Instruments scores 8.4/100 (minimal), with a separate agent-readiness read of 0/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. 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-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from ISAAC Instruments'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/isaac-instruments/"
title="ISAAC Instruments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/isaac-instruments.svg"
alt="ISAAC Instruments Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/isaac-instruments/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/isaac-instruments/"
title="ISAAC Instruments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/isaac-instruments/card.svg"
alt="ISAAC Instruments 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 ISAAC Instruments
Each block below is one kind of artifact we hold for ISAAC Instruments. 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 8
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.
ISAAC Vehicles API
Modeled interface for retrieving fleet vehicles and tractor/trailer assets configured on the ISAAC platform, including identifiers, VIN, and unit metadata used to correlate tele...
ISAAC Drivers API
Modeled interface for retrieving drivers and their profile, licensing, and assignment details as managed on the ISAAC platform. Endpoints are documented in ISAAC's partner API G...
ISAAC Hours of Service (ELD) API
Exports drivers' hours-of-service information captured by ISAAC's ELD - time spent in each duty status and distance traveled - for compliance, payroll, and TMS workflows. This c...
ISAAC Positions API
Modeled interface for GPS positions and location breadcrumbs used by visibility and tracking partners integrating with ISAAC telematics. Endpoints are documented in ISAAC's part...
ISAAC Trips API
Modeled interface for trips, stops, and route/dispatch data flowing between ISAAC and TMS/dispatch partners. Endpoints are documented in ISAAC's partner API Guide and provisione...
ISAAC Messaging API
Modeled interface for driver-to-dispatch messaging and in-cab workflow forms exchanged through the ISAAC platform. Endpoints are documented in ISAAC's partner API Guide and prov...
ISAAC Fuel and Performance API
Modeled interface for fuel consumption, idling, and driving-performance metrics used by fuel-tax (IFTA) and coaching partners. Endpoints are documented in ISAAC's partner API Gu...
ISAAC Events API
Modeled interface for vehicle and safety events (fault/diagnostic codes, safety-critical events) surfaced to safety/compliance and maintenance partners. Endpoints are documented...
Scroll within the panel for all 8 ·
Security Posture 1
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 ISAAC Instruments — 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.
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/isaac-instruments · machine-readable index on apis.io
This is an independent, third-party profile of ISAAC Instruments, 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.