Kaseya previewed an API-driven version of its Kaseya Intelligence platform at the Connect Europe conference in Prague on June 16–18, 2026, marking a decisive shift toward interoperability in agentic IT. The move allows managed service providers (MSPs) and IT teams to invoke autonomous IT workflows not only from within Kaseya’s own ecosystem but also from external AI work surfaces such as Anthropic’s Claude and Microsoft Copilot.

The demonstration at Prague’s Cubex Centre underscored a growing industry belief that AI-driven IT management should not be locked into a single vendor’s interface. By exposing Kaseya Intelligence through a robust API, the company is betting that its automation engine will become the default backend for AI assistants across the enterprise, regardless of which chatbot or copilot an organization prefers.

What Is Kaseya Intelligence?

Kaseya Intelligence, first introduced in 2025, is the company’s agentic AI platform designed specifically for IT service delivery. Unlike traditional RMM (Remote Monitoring and Management) tools that rely on static scripts or human-triggered actions, agentic AI can reason about IT problems, plan multi-step resolutions, and execute them autonomously with human-in-the-loop oversight when needed.

The platform understands natural language requests—such as “Patch all Windows servers missing critical updates” or “Reset MFA for all new hires who haven’t enrolled”—and translates them into sequences of API calls, script executions, and configuration changes across an MSP’s entire tool stack. Built on a large language model fine-tuned for IT operations, Kaseya Intelligence can handle tasks ranging from ticket triage and routine maintenance to complex disaster recovery scenarios.

An API-First Approach to Agentic IT

The new API preview takes this capability a step further by decoupling the natural language interface from Kaseya’s own applications. Until now, MSP technicians had to interact with the agentic engine through the Kaseya One dashboard or its integrated virtual assistant. With the API, any conversational surface—be it a custom web portal, a chat tool like Slack or Teams, or a standalone AI assistant such as Claude or Copilot—can relay user instructions to Kaseya Intelligence and receive real-time status updates.

Kaseya’s API is designed to be RESTful and WebSocket-compatible, enabling both stateless query-response patterns and persistent streaming for long-running operations. An MSP using Microsoft 365 and Copilot, for instance, could type into a Copilot chat: “@Kaseya, generate a security compliance report for client Acme Corp and flag any systems missing endpoint protection.” Copilot would parse the intent and forward the instruction via the API, while Kaseya Intelligence would orchestrate the data gathering, produce the report, and push a summary back to the chat.

Opening the Door to Claude and Copilot

The explicit support for Anthropic’s Claude and Microsoft Copilot is no accident. Both AI assistants have gained significant traction among enterprise users—Claude for its long-context reasoning and safety-focused design, and Copilot for its deep integration with the Microsoft ecosystem. By enabling these assistants to act as frontend to its automation engine, Kaseya is effectively piggybacking on the user interfaces that IT professionals already use daily.

During the Connect Europe keynote, Kaseya demonstrated a live scenario where a technician asked Claude, “What caused last night’s performance degradation on our SQL cluster?” Claude, via the API, queried Kaseya Intelligence, which in turn analyzed logs across multiple monitored endpoints, correlated events, and returned a root cause analysis along with a proposed remediation plan. The technician simply approved the plan, and the agent executed the fix without ever leaving the Claude conversation.

A similar flow was shown with Microsoft Copilot, where a security analyst typed a natural language command to quarantine all devices that had generated a specific malware alert in the past hour. Copilot relayed the command to Kaseya Intelligence, which executed the quarantine across the affected endpoints and updated the ticket in the PSA system automatically.

What This Means for MSPs

For managed service providers, the API represents a profound workflow shift. MSP technicians often juggle dozens of tools—RMM, PSA, backup, security, documentation—each with its own interface. Agentic automation has already begun to reduce that context-switching by allowing technicians to express intent once and letting the AI handle the multi-tool orchestration. Now, with the API, that orchestration can be invoked from whichever interface the technician prefers, be it a dedicated AI chat, a team collaboration platform, or even a custom-built client.

Early adopter MSPs at Connect Europe expressed cautious optimism. “We’ve been using Kaseya Intelligence for a year, and it’s cut our ticket resolution time by 30 percent,” said one managed services director who requested anonymity because his firm is still evaluating the API. “But having it available in Copilot means our Level 1 techs, who live in Teams and Outlook all day, can trigger complex automations without even opening the Kaseya console. That’s a game-changer.”

Another benefit is training. The API’s multi-frontend approach reduces the learning curve for new technicians who may already be comfortable with a particular AI assistant. Instead of learning yet another dashboard, they can apply their existing conversational skills.

Security and Compliance in an Agentic World

Giving an autonomous AI the ability to execute infrastructure changes across hundreds of endpoints, however, raises serious security questions. Kaseya executives stressed that the API retains the same granular role-based access control (RBAC) as the interactive console. Every action initiated through Claude, Copilot, or any other external surface is subject to the same permission model: the AI can only perform tasks that the authenticated user is authorized to do.

Furthermore, all commands are logged with a full audit trail. At Connect Europe, Kaseya’s CISO demonstrated how the platform timestamped every step of an automated ransomware containment workflow, including which AI persona initiated the action and at what time. This audit log is designed to meet SOC 2 and ISO 27001 requirements, which is critical for MSPs servicing regulated industries.

Multi-factor authentication is enforced at the API gateway, and Kaseya plans to support open authentication standards such as OAuth 2.0 and SAML to allow integration with existing enterprise identity providers. The company also hinted at a forthcoming “confirmation mode,” where the AI would propose high-risk actions and wait for explicit human approval before proceeding—similar to the “human-in-the-loop” paradigm already popular in AI safety research.

Agentic IT and the Competitive Landscape

Kaseya is not alone in pursuing agentic IT. Rivals like ConnectWise, Datto (owned by Kaseya, but still operating semi-independently), and NinjaOne have all announced AI copilots of their own. However, Kaseya’s decision to open its engine to third-party assistants sets it apart. Most competitors are taking a walled-garden approach, building AI directly into their dashboards and hoping technicians will stay within that ecosystem.

The API-first strategy aligns with broader industry trends toward composable IT toolchains. Gartner has predicted that by 2028, 60% of IT operations tools will expose agentic APIs, allowing AI assistants to orchestrate across multiple platforms. Kaseya appears to be positioning itself not just as a tool vendor but as the “brain” that coordinates the entire MSP stack.

Microsoft’s involvement is particularly noteworthy. While Copilot is a natural frontend, Microsoft has its own endpoint management and security products (Intune, Defender) that overlap with Kaseya’s portfolio. By making Kaseya Intelligence accessible from Copilot, Microsoft tacitly acknowledges that enterprises use multi-vendor environments and that no single AI can have deep integrations with all tools. The API can fill that gap.

Anthropic, too, sees value. Claude’s enterprise version already supports custom tool use, and the Kaseya integration showcases how AI can go beyond conversational Q&A to perform real-world actions. For Anthropic, such partnerships strengthen Claude’s position as a general-purpose enterprise assistant.

Technical Details and Early Access

Kaseya Intelligence’s API is available as a developer preview to select MSPs and would-be integrators who apply through the company’s beta program. General availability is expected later in 2026, though no firm date was given. Pricing has not been disclosed, but company representatives indicated it would be consumption-based, likely tied to the number of API calls or the volume of automated actions.

The API documentation, published at the Kaseya Developer Portal, covers endpoints for intent submission, action status retrieval, and webhook notifications. Developers can register a callback URL to receive push updates as automated tasks progress. The API also supports bulk operations, enabling one command to be applied across multiple clients—a feature MSPs with large portfolios will appreciate.

During the breakout sessions, a Kaseya product manager demonstrated building a lightweight integration with Slack’s bot framework in under 30 minutes. The integration allowed a Slack channel to dispatch IT commands and receive asynchronous updates, all routed through the Kaseya Intelligence API. Such rapid development underscores the platform’s flexibility and could spur a cottage industry of custom connectors.

Real-World Use Cases Highlighted at Connect Europe

Several scenarios were explored on stage to illustrate the API’s potential:

  • Automated onboarding: A new customer’s tenant provisioning was initiated via a Copilot chat in a Teams sales channel. The API invoked Kaseya Intelligence to create active directory structures, deploy agents, set backup policies, and generate welcome documentation—all within 15 minutes.
  • Compliance audits: An MSP used Claude to ask, “Are all our healthcare clients HIPAA-compliant for data encryption?” The AI parsed the request, queried Kaseya Intelligence, which scanned all managed endpoints and reported three non-compliant nodes, then offered to remediate them automatically.
  • Proactive maintenance: A recurring maintenance schedule was set up entirely through a natural language conversation with Claude: “Every Sunday at 2 a.m., run Windows updates on all servers in client group Gamma, and if any fail, create a priority ticket.” The API translated this into a scheduled workflow that runs weekly.

The Path Ahead for Agentic IT

Kaseya’s API announcement comes at a pivotal moment for the IT service industry. The global shortage of cybersecurity professionals has pushed MSPs to automate aggressively, and the rise of AI assistants in the workplace has conditioned users to expect chat-based interactions with all their tools. By 2027, analysts project that over half of all IT support interactions will involve some form of AI agent.

However, challenges remain. Trust in autonomous agents is still fragile. A poorly scoped automation could, for instance, accidentally take down a critical production system. Kaseya’s answer is the aforementioned “confirmation mode” and strict RBAC, but the industry will need to establish best practices for agentic governance—much like the DevOps community did for CI/CD pipelines a decade ago.

Interoperability standards are also nascent. While Kaseya’s API is a step forward, the dream of a universal agentic mesh—where AI assistants from different vendors can seamlessly delegate tasks to one another—is still a few years away. Industry consortia will likely form to tackle this, and Kaseya’s early move gives it a seat at the table.

Conclusion

With the preview of its Intelligence API at Connect Europe, Kaseya is charting a course toward a more open, composable future for agentic IT. By making its autonomous engine available to Claude, Copilot, and ultimately any external work surface, the company is acknowledging that the power of AI-driven automation comes not from owning the interface, but from delivering reliable, secure actions regardless of which interface the human chooses. For MSPs, the API promises to further collapse the boundary between thinking about IT work and doing it—one natural language command at a time. As the technology matures and governance frameworks emerge, agentic IT may well become the default operating model for the managed services industry.