Every tool your
MSP runs,
connected to your AI.
18 native integrations across PSA, RMM, security, documentation, networking, monitoring, backup, distribution, automation and Microsoft 365. If your vendor publishes an OpenAPI spec, the rest is a paste job.
today
tools
spec
The catalogue
20 of 20 shown
Service desk tickets, companies, contacts, configuration items and time entries.
Tickets, boards, companies, members, time entries and risk scoring across your whole client base.
Ticket management, client lookup and SLA tracking asked for in plain language.
Endpoint monitoring, device audits, alerts, patch status and site management.
Device monitoring, offline detection, patch compliance, disk health and alert management.
Combined PSA and RMM for smaller MSPs. Tickets, customers, assets, alerts and invoicing.
DNS policies, threat reports, query logs, managed networks and domain categories.
EDR incidents, agent status and endpoint threat visibility across every client.
Graded SaaS alerts, event search, MFA posture and mailbox rule checks across Microsoft 365 and Google Workspace.
Companies, IT assets, knowledge base articles, passwords, procedures and activity logs.
Organisations, configurations, passwords, flexible assets and contacts.
Network device inventory, discovery, alerts, config backups and multi tenant monitoring.
Open alerts, monitored resources, device groups, collectors, maintenance windows and dashboards.
Backup monitoring, device health, vault usage and AutoVerify status.
Marketplace subscriptions, renewals, invoices and vendor spend.
Author and revise workflows, publish and unpublish them, and see which automations are failing.
Tenants, users, MFA posture, licences, Intune devices and standards drift across Microsoft 365.
Microsoft 365 baseline alignment, per policy drift, Secure Score and admin posture across customer tenants.
IT automation, patch scheduling and endpoint health for Kaseya managed environments.
Threat detection, incident response and endpoint health from one interface.
Not on the list?
Paste the spec.
We read your OpenAPI file, index every path and schema, and build the tools from it. The AI works strictly from that index, so it cannot invent an endpoint that does not exist.
Paste the spec
A URL or the raw JSON. We validate it, then index every path, schema and auth method.
Tools get generated
Reads become query tools. Writes become action tools, which means they land in the approval queue like any other change.
Same rules apply
Custom connectors sit inside the same permission model and the same audit trail as the native ones.
Connecting a tool is
not the same as
handing it over.
Every integration you connect lands inside the same permission model. An admin decides, per person and per tool, who can read it, who can propose a change and who can let that change run.
read the security model →Credentials stay in the vault
Each tool's keys are encrypted with a key that belongs to your workspace. Your AI provider only sees the result of a call.
Read tools run, write tools wait
Reads are exposed automatically. Anything that changes a record is held with its exact payload until a person approves it.
Per integration, per person
Finance can read Pax8 and nothing else. A first line tech can see devices but not passwords. You set it, we enforce it twice.
Everything is logged
Every call is written down with the person, the tool and the result, whether it was allowed or refused.
Connect your first
tool this afternoon.
Native tools are ready as soon as the credentials are in. Custom connectors are ready as soon as the spec is.