TruVideo
TruVideo is a video-intelligence and omnichannel communication platform for service businesses, built for the automotive service market and expanding into aviation, insurance, and commercial trucking. It lets dealers, service advisors, and technicians capture and share videos, run AI features (noise cancellation, real-time sentiment analysis, and a multilingual virtual assistant), and drive SMS/messaging conversations tied to repair orders. TruVideo's developer surface is SDK-first — modular on-device capture SDKs for iOS, Android, .NET, React Native, and Capacitor — plus a REST Platform API (v2) covering authentication, repair orders, videos, messaging, customers, files, and reporting.
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 TruVideo the way a machine reads it — 14 machine-readable artifacts across 11 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 — TruVideo scores 43.9/100 (thin), with a separate agent-readiness read of 47/100 (agent ready). 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 TruVideo
Each block below is one kind of artifact we hold for TruVideo. 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 11
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.
TruVideo Authentication API
The Authentication API from TruVideo — 2 operation(s) for authentication.
TruVideo Chat API
The Chat API from TruVideo — 4 operation(s) for chat.
TruVideo Customers API
The Customers API from TruVideo — 1 operation(s) for customers.
TruVideo Dealers API
The Dealers API from TruVideo — 1 operation(s) for dealers.
TruVideo Files API
The Files API from TruVideo — 4 operation(s) for files.
TruVideo Messages API
The Messages API from TruVideo — 3 operation(s) for messages.
TruVideo Repair Orders API
The Repair Orders API from TruVideo — 5 operation(s) for repair orders.
TruVideo Reports API
The Reports API from TruVideo — 2 operation(s) for reports.
TruVideo Support API
The Support API from TruVideo — 1 operation(s) for support.
TruVideo Users API
The Users API from TruVideo — 1 operation(s) for users.
TruVideo Videos API
The Videos API from TruVideo — 3 operation(s) for videos.
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
truvideo-mcp.yml
MCP SERVERSecurity Posture 2
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 TruVideo — 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 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
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/truvideo · machine-readable index on apis.io