Omnitracs
Omnitracs is a commercial fleet management, telematics, and transportation-management provider, now part of Solera Inc. (acquired 2021, operating under Solera Fleet Solutions). Its Omnitracs One platform and the Omnitracs Roadnet routing platform serve roughly 15,000 fleet customers with ELD / Hours-of-Service compliance, telematics and GPS positioning, driver workflow and messaging, routing and dispatch, and video safety. Omnitracs exposes real integration APIs and web services (Roadnet Web Services, the Services Portal Entity Management web services, and the SOAP/XML Event Subscription Service that streams positions, messages, HOS, and critical events), but access is partner- and customer-account gated - there is no open, self-service public developer portal. API credentials (a username/password with API access) and the integration developer wiki are provisioned to contracted customers and integration partners. Endpoints documented here for gated surfaces are honestly modeled from public integration notes, not from an open reference.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Omnitracs the way a machine reads it — 5 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 — Omnitracs scores 16.8/100 (emerging), 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Omnitracs
Each block below is one kind of artifact we hold for Omnitracs. 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.
Omnitracs Web Services (Roadnet Platform)
Integration web services for the Omnitracs Roadnet routing and dispatch platform (route planning and optimization, orders/stops, and schedules). A live Swagger UI is published a...
Omnitracs Entity Management Web Services
Services Portal entity-management web services for maintaining fleet master data - vehicle maintenance (add/edit), driver maintenance (add/edit), and trailer management, with HO...
Omnitracs Event Subscription Service (ESS)
A publish-subscribe integration service in which Omnitracs applications continually publish transactions (vehicle positions/GPS, driver messages, Hours-of-Service logs, and crit...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
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 Omnitracs — 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 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 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/omnitracs · machine-readable index on apis.io