Fleetmatics
Fleetmatics was a fleet management, telematics, and GPS vehicle tracking SaaS company whose Reveal platform tracked commercial vehicles, drivers, and mobile assets for small and mid-sized fleets. Founded in Dublin and later headquartered in Massachusetts, Fleetmatics IPO'd on the NYSE in 2012 and was acquired by Verizon in 2016 for about USD 2.4 billion, becoming the core of Verizon Connect. Its Reveal platform exposes a documented REST API and webhook suite - the Fleetmatics Integration Manager (FIM) / Reveal Integration Services APIs - covering vehicles, drivers, GPS positions and history, trips and segments, driver status and safety, hours-of-service logbooks, geofences (places), groups, and non-powered asset tracking. The API gateway still runs on Fleetmatics-branded hosts (fim.api.us.fleetmatics.com); access is gated to Reveal customers and approved integration partners who request Integration Manager and Reveal REST credentials before calling the documented endpoints. The Fleetmatics brand now redirects to Verizon Connect.
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 Fleetmatics the way a machine reads it — 2 machine-readable artifacts across 1 API, 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 — Fleetmatics scores 14.9/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.
How we profile Fleetmatics
Each block below is one kind of artifact we hold for Fleetmatics. 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 1
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.
Fleetmatics Reveal API
The Fleetmatics Reveal API - delivered through the Fleetmatics Integration Manager (FIM) / Reveal Integration Services - exposes REST endpoints for vehicles, drivers, real-time ...
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 Fleetmatics — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fleetmatics · machine-readable index on apis.io