Integrations and APIs for Bots and Your Systems
Bring the systems and AI agents you already run into the conversation. Sover gives your developers 50+ REST methods, a Python client library and MCP, so a bot or an agent can post an event into the chats you authorize and answer the people in them.
Overview
Your Systems, in the Conversation
Sover provides a Bot API for building integrations that bring messages and actions into the communication environment, through two interfaces: the REST API, optimized for speed, and MCP (Model Context Protocol), optimized for universality. A bot joins the chats it is added to with rights similar to a regular user’s: it sends and receives messages, can be mentioned and appears in search.
The Outlook plugin brings Sover calendar and meetings into Outlook. Sover is user-hosted, so each integration connects to servers you control and is scoped to the systems, conversations and actions you agree.
Capabilities
What You Can Connect
-
50+ REST Methods
Send text, files, images, audio, video and stickers and update what was sent; read group history and unread messages; manage groups, channels and workspace members; start and end calls; read calendar events.
-
Bots as Chat Members
Add a bot to workspaces, groups and channels, appoint it administrator and mention it in a chat. It sends and receives messages like any member.
-
Commands and Buttons
People drive a bot with tappable commands and up to 20 buttons under a message, including links that open a browser or another application.
-
Python Client Library
A Python client library implements the Bot API contract, so your developers write the bot’s logic instead of low-level API calls.
-
Outlook Plugin
View your calendar, schedule meetings and join Sover video calls from Outlook. The plugin covers calendar and meetings, not chat.
-
IREX Alarm Notifications
With the IREX Ethical AI Platform, IREX alarm notifications arrive in dedicated security spaces in Sover.
Sover with IREX -
MCP for AI Agents
Any MCP-capable agent connects to the chats you authorize without custom code, alongside the REST API.
Agentic bots -
High-Speed Chat Export
Bots and agents export a chat’s history in bulk through the REST API or MCP, for archiving, review or agent context.
Bulk export -
Active Directory Sync
People and their departments sync one way from Microsoft Active Directory into the Sover enterprise address book.
Directory sync
AI Agents
AI-Powered and Agentic Bots, over REST or MCP
Connect AI-powered bots and the agents you approve. They take part in your chats as members, within the limits your security policy sets, through the interface that suits the task.
REST API: Optimized for Speed
Use the 50+ REST methods, directly or through the Python client library, for routine and high-volume work. Direct calls answer fast and spend fewer of an agent’s tokens.
MCP: Optimized for Universality
Any agent that speaks the Model Context Protocol connects without custom code. Use it for one-off tasks, when an agent looks something up or acts in a chat on request.
Works with the agent harnesses your team already uses
- Claude
- ChatGPT
- Grok
- Cursor
- Hermes
- OpenClaw
Product names are trademarks of their respective owners.
High-Speed Chat Export
A bot or an agent exports the history of a chat it has access to in bulk, through the REST API or MCP: for archiving, compliance review, or the context an agent works from. Each agent’s access to history is granted under your security policy.
Sover with IREX
IREX Alarms and Ask IREX in Your Chats
Sover connects to the IREX Ethical AI Platform. IREX alarm notifications arrive in real time in dedicated security spaces, where the team on duty sees the event and discusses it in context.
Ask IREX, shipping in beta on selected instances, lets users search the IREX archive for people, vehicles and events in natural language from a Sover chat. IREX agentic AI runs each request under the IREX platform’s Case ID and audit-logging controls.
Both require the IREX platform; neither is standalone video analytics in Sover.
Sover and IREX are related parties. They share one team, and Sover is majority-owned by IREX co-founder Nik Ptitsyn.
Sover on irex.aiIllustration with invented content. Ask IREX is shipping in beta on selected instances and requires the IREX platform.
Directory Sync
Your Enterprise Address Book, Synced from Active Directory
Sover syncs people from Microsoft Active Directory into its enterprise address book. Each person is placed in their organization by the company or department your directory records, so colleagues find each other in Sover under the structure they already know.
The sync runs one way: Active Directory stays the source of truth, and the changes you make there flow into Sover. Administrators can still add people by hand or provision them from a CSV file in the back-office console.
How It Works
From a Bot to a Working Integration
-
Appoint a Bot Administrator
Your organization designates an employee to administer bots. That person creates, edits and stops bots through Bot Creator, a dedicated bot inside the app.
-
Issue the Bot’s Token
Each bot gets its own access token, valid for one year by default. The administrator can extend it, generate a new one or revoke it.
-
Add It to the Right Chats
Add the bot to the workspaces, groups and channels it serves, and agree the source system, the target conversations and the actions it may take.
-
Connect Your System
Your developers call the REST methods, directly or through the Python client library, or connect an agent through MCP, so an event reaches the chat and people reply to it in context.
Included
What Is Included, and Where the Limits Are
Included
-
The Sover Bot API. 50+ REST methods for messages, groups and channels, workspace members, calls and calendar events.
-
MCP for AI agents. Connect the agents you approve through the Model Context Protocol, alongside the REST API.
-
A Python client library. It implements the Bot API contract for your developers.
-
Bulk chat export. High-speed export of chat history through the REST API or MCP.
-
Active Directory sync. One-way sync of people and their departments from Microsoft Active Directory into the enterprise address book.
-
Bot administration in the app. Create, rename, describe, activate, stop and re-token bots through Bot Creator.
-
Interactive messages. Commands, up to 20 buttons per message, and links that open a browser or another application.
-
The Outlook plugin. Calendar viewing, meeting scheduling and joining Sover video calls from Outlook.
-
IREX alarm notifications. Delivered into dedicated security spaces when you run the IREX platform.
Stated Limits
-
Bots have fewer rights than people. A bot cannot create groups, channels or workspaces, cannot transfer ownership and cannot start secret chats.
-
No buttons in information channels. Messages with buttons are not supported there.
-
Files go through the platform. A file is uploaded into Sover; delivering files only as links to your own servers is not supported.
-
Rate limits apply. The Bot API rate-limits each bot; confirm the quotas for your installation.
-
Outlook is not a chat client. Chat, file sharing and message search are not available in Outlook; confirm the supported Outlook version for your rollout.
-
IREX features need IREX. Alarm notifications and Ask IREX require the IREX platform, and Ask IREX is shipping in beta on selected instances.
-
Agents act under your policy. Agree each agent’s permitted actions, its access to history and its deployment scope before it goes live.
-
Each integration is scoped. A notification alone is not a complete incident-management workflow; agree what each bot may do before it goes live.
Where It Runs
Integrations Where Teams Respond
- First Responders & Alerts Bot notifications and IREX alarms bring an event into the chat where the team on shift reviews it and responds. Learn More
- E-Government Services A national operator can build its own services for citizens as bots on the Sover Bot API. Learn More
- Government Agencies Agencies connect their own systems to the chats they run on their own servers, one scoped integration at a time. Learn More
- Critical Infrastructure Operational events from the systems that run a network reach the people on duty, in context. Learn More
Live Example
This Page’s Contact Form Runs on Sover
The form below is a working Sover integration. When you send it, a bot carries your request into our team’s chat.
-
You Send the Form
Your name, work email and message leave this page for our relay.
-
A Bot Posts It
A Sover bot posts your request through the Bot API into a designated chat.
-
Agents Help Our Team
AI agents in the chat help our team prepare the answer, and a person replies to you as soon as possible.
Keep Reading
Questions, or Ready for a Briefing?
Contact Sales
Tell us about your organization. This form runs on Sover: your request is posted to a designated chat, where AI agents help our team reply as soon as possible.
Can Sover connect to our business systems?
Sover provides a Bot API for building integrations that bring messages and actions into the communication environment. Scope each integration around the source system, target conversations, permitted actions, and deployment requirements.
Does Sover provide a Python client for bot integrations?
Yes. The documented Bot API includes a Python client library alongside its REST methods. Use the API reference for the methods and requirements applicable to the integration.
What can a Sover bot be used for?
A bot can deliver operational messages into an authorized conversation, helping a team review an event and discuss it in context. The available actions depend on the bot's permissions and the integration; a notification alone is not a complete incident-management workflow.
Can Sover integrate with Outlook?
Yes. Sover has an Outlook plugin for calendar and meetings. It is not a chat client; confirm the supported Outlook version and deployment configuration for the planned rollout.
Does Sover support AI agents?
Yes. Sover supports MCP and chatbot APIs for AI-agent participation under the customer's security policy. The permitted actions and deployment scope should be agreed explicitly, including any access to history or participation in conferences.