Unitrends
Unitrends, a Kaseya company, provides all-in-one backup and disaster recovery (BCDR) solutions that secure, defend, and recover data across on-prem data centers, cloud, SaaS, and endpoints. The platform spans Recovery Series backup appliances, Unitrends Backup software, endpoint backup, and the UniView / Unitrends MSP portal, with ransomware detection, automated recovery assurance testing, and BackupIQ intelligence. Developers get a UniView Portal Public API (OAuth 2.0 client credentials via login.backup.net) for customers, appliances, assets, backups, and BackupIQ alerts, plus a documented per-appliance REST API and a community PowerShell toolkit.
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 Unitrends the way a machine reads it — 15 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 — Unitrends scores 42.6/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Unitrends
Each block below is one kind of artifact we hold for Unitrends. 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.
Unitrends Agents API
The Agents API from Unitrends — 1 operation(s) for agents.
Unitrends Appliances API
The Appliances API from Unitrends — 1 operation(s) for appliances.
Unitrends Assets API
The Assets API from Unitrends — 2 operation(s) for assets.
Unitrends BackupIqAlerts API
The BackupIqAlerts API from Unitrends — 1 operation(s) for backupiqalerts.
Unitrends Backups API
The Backups API from Unitrends — 1 operation(s) for backups.
Unitrends Customers API
The Customers API from Unitrends — 1 operation(s) for customers.
Unitrends Domains API
The Domains API from Unitrends — 1 operation(s) for domains.
Unitrends DomainsEntra API
The DomainsEntra API from Unitrends — 1 operation(s) for domainsentra.
Unitrends DomainsV2 API
The DomainsV2 API from Unitrends — 1 operation(s) for domainsv2.
Unitrends DomainUsers API
The DomainUsers API from Unitrends — 1 operation(s) for domainusers.
Unitrends DomainUsersV2 API
The DomainUsersV2 API from Unitrends — 1 operation(s) for domainusersv2.
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.
unitrends-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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Unitrends — 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
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/unitrends · machine-readable index on apis.io