Slide
Slide is a modern, security-first Business Continuity and Disaster Recovery (BCDR) platform built exclusively for Managed Service Providers (MSPs). Founded by Datto creator Austin McChord, Slide pairs on-premise Slide Box appliances with the Slide Cloud to deliver always-encrypted, block-level backup, snapshot management, file and image restores, and virtualization. Its open REST API (api.slide.tech) gives MSPs full programmatic control to integrate, extend, and automate agents, devices, backups, snapshots, restores, networks, clients, users, alerts, and audit logs within their existing tooling. The platform uses AES-256 and ZFS native encryption, offers month-to-month subscriptions, and is SOC 2 Type 1 certified.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Slide the way a machine reads it — 18 machine-readable artifacts across 14 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 — Slide scores 52.3/100 (developing), with a separate agent-readiness read of 51/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 Slide
Each block below is one kind of artifact we hold for Slide. 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 14
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.
Slide Accounts API
Everything about [accounts](#model/account)
Slide Agents API
Everything about [agents](#model/agent)
Slide Alerts API
Everything about [alerts](#model/alert)
Slide Audits API
The Audits API from Slide — 4 operation(s) for audits.
Slide Backups API
Everything about [backups](#model/backup)
Slide Clients API
Everything about [clients](#model/client)
Slide Devices API
Everything about [devices](#model/device)
Slide Networks API
Everything about [networks](#model/network)
Slide Restores (File) API
Everything about [file restores](#model/filerestore)
Slide Restores (Image) API
Everything about [image exports](#model/imageexport)
Slide Restores (Push) API
Everything about [push file restores](#model/filerestorepush)
Slide Restores (Virtual Machine) API
Everything about [virtual machines](#model/virtualmachine)
Slide Snapshots API
Everything about [snapshots](#model/snapshot)
Slide Users API
Everything about [users](#model/user)
Scroll within the panel for all 14 ·
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.
slide-mcp.yml
MCP SERVERSecurity Posture 3
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 Slide — 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 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 5
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/slide · machine-readable index on apis.io