Loading…
Channels & APIs
Publish any agent, team or workflow to Microsoft Teams, Slack, WhatsApp, an email inbox or your website — and to other software over OpenAI-compatible APIs, A2A and MCP.
Capabilities
Signed Bot Framework requests with tenant checks. Senders run with their own member permissions.
Events API with signature verification and per-thread conversations.
Meta Cloud API with signature verification for customer conversations.
A Microsoft 365 mailbox polled every minute; replies in-thread and attachments flow into workflows.
Floating widget or full page with your avatar, greeting, quick replies, colors, size and position.
OpenAI-compatible /v1, A2A agent cards, ZeaIQ as an MCP server, webhooks and REST with scoped keys.
How it works
An agent, a team or a workflow — the same governance applies to all.
Teams, Slack, WhatsApp, email, website widget or API key.
Customize the widget in a live desktop and mobile preview.
Pause, rotate webhooks and watch every message in Agent Ops.
Open both ways
Call agents as OpenAI-compatible models, discover them through A2A agent cards, or let any MCP client use them as tools. Agents can also consume external MCP servers and OpenAPI specs.
from openai import OpenAI
# Any OpenAI client works — point it at ZeaIQ.
client = OpenAI(
base_url="https://your-instance.zeaiq.ai/v1",
api_key=ZEAIQ_API_KEY, # scope: agents:openai_compat
)
reply = client.chat.completions.create(
model="agent:6d85c1fb-0dc7-4529-a793-74d7e1d7c7d4",
messages=[{"role": "user", "content": "Summarize today's payment exceptions"}],
stream=True,
)Your brand, your website
Ten avatar presets or your own, up to four quick replies, three sizes, bubble or ask-bar launcher and a teaser message. A JS API opens, asks, closes and toggles the widget from your own buttons.
Widget customizer
Under the hood
The specifics your architects and security reviewers will ask for.
Works with
Every capability shares the same runtime, identity and governance.
Yes. Point any OpenAI-compatible client at ZeaIQ's /v1 endpoint and use agent:{id} or team:{id} as the model name.
On Teams and Slack, senders are mapped to members by email and run with their own permissions. Email and WhatsApp run as the connection owner.
Book a working session with our team. Bring a real use case — we'll build it with you and show the governance and ROI views alongside.
