Bird vs Infobip (2026)

An agent signs in to Bird through browser OAuth and then acts with a scoped, revocable grant. Through the hosted MCP server it sends email, SMS, WhatsApp messages and one time passcodes, orders phone numbers, adds sending domains and senders, and manages templates, contacts, audiences and preferences.

Grants cover only the overlap of what the client asked for, what the user approved and what the user holds, and owner and platform admin scopes can never be delegated. In the other direction, webhook destination connectors hand each inbound message to a Claude Managed Agents session or a Grok routine. Connections to the customer's own business systems are the customer's agent's to make.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

In the Tools section a customer adds three kinds of tool to each agent, a Component, an MCP server or an Exchange application, which let the agent call APIs, execute backend logic, retrieve external data and trigger automated workflows. Components encapsulate reusable logic and can orchestrate multiple API calls or backend processes for complex integrations.

MCP servers are configured with a name, endpoint URL, HTTP headers for authentication tokens, and an Allowed functions field naming which actions the server may take when called, so each connection is authenticated and scoped. Exchange applications are selected from a published integrations catalog. Underneath sits the messaging estate the agent acts through, more than fifteen natively integrated channels each with its own API, plus the modular CPaaS X stack.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

Events move to the agent and its output moves back out through Bird. Each inbound WhatsApp, SMS, Apple Messages or mailbox message is delivered as event JSON, failed deliveries are retried, and a webhook can be paused or deleted.

The sequence of steps an agent takes, its tools and its decisions run in the customer's agent platform, and for voice the customer's application owns speech, reasoning and business tools while Bird carries the call.

There is no workflow builder or multistep runtime for agents inside Bird, so a reminder sequence or an escalation path is something the customer's agent or its own scheduler runs.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

An AI agent can be set up as an orchestrator that coordinates other agents. The customer adds subagents from a list, and the orchestrator delegates tasks to specialized agents, combines their responses and controls conversation routing, with the agents table showing how many subagents each orchestrator has connected. Each agent's Description field is what other agents read to decide when to call it.

Beneath that, Automation Studio builds journey flows and chatbots that route on rules, triggers and Customer Profiles data, and the Agent connector element drops an AI agent into a chatbot so deterministic flows and autonomous agents combine in one path. Agents themselves execute multi-step tasks, calling tools in sequence to reach a goal.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

Inbound WhatsApp, SMS, Apple Messages and agent mailbox email each fire an event, whatsapp.received, sms.received, amb.received and email_mailbox.message_received, that a webhook delivers to the agent and that starts a new agent run. MCP Events let an MCP client subscribe to events such as new mail and receive each as a signed webhook. Voice calls reach a customer built voice application over SIP, and agent mailboxes give an agent an address of its own.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Agents work across WhatsApp, SMS, RCS, MMS, email, voice, live chat, video, in-app messaging, mobile push, Viber, Messenger, Instagram, Telegram, Apple Messages for Business, Kakao, Line and Zalo, each with its own API page, all flowing through the same system.

Work starts in three ways, inbound when a customer reaches out on any supported channel, event-driven when Automation Studio journey flows are triggered by customer behavior or profile changes, and scheduled when journeys start on dates.

Voice is built in, with a Transfer call to AI agent element placing an agent inside an IVR flow, and Broadcast handles outbound at volume.

Sourceinfobip.com/docs/automation-studioread 2026-09-05

No knowledge base for an agent to search sits inside Bird. Its skills are instruction packs for the agent itself, one routing requests to the right CLI command group and one auditing a sending domain's authentication and mail records, and the knowledge base Bird runs is customer help for account setup, deliverability and billing. Grounding an agent in a company's own documents happens in whatever agent platform the customer runs. Templates, contacts and audiences in Bird hold messaging data, which an agent can read through the MCP server but which is not indexed for retrieval.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Knowledge agents are specialized agents for retrieving information from documents, URLs and files, built for FAQ-style interactions, and they sit alongside a Knowledge Base shared component available across AgentOS. Quality center has a dedicated Knowledge agents section that validates responses against expected answers and tracks quality over time, against a persistent body of content the customer curates. General-purpose AI agents reach the same material through tools and components. The Customer Profiles data platform is a separate database of customer profiles and events.

Sourceinfobip.com/docs/ai-agents/knowledge-agents/overviewread 2026-09-05

Every routed message starts a new session or run, and the agent receives the event payload for that message alone, so any history across messages lives in the customer's agent platform. Message records, contacts and audiences persist in the organization's region as the messaging data model, and an agent can look a contact up through the MCP server. Nothing in Bird stores what an agent learned about a person or hands it back on the next message.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Customer Profiles is AgentOS's customer data platform, holding person and company profiles, attributes, segments and behavioral events, with interaction history available to AI agents so they can personalize responses and make context-aware decisions across sessions.

Agents also carry session state within a conversation, and past sessions can be viewed through Session history.

Customer Profiles is a store the customer loads and queries, not state the agent forms and retains, and Infobip has no agent memory product, no scope, lifetime or deletion control for retained agent state, and no memory entry in the AgentOS product set.

Sourceinfobip.com/docs/customer-profilesread 2026-09-05

A person approves each agent's access on a consent screen that flags the client name as unverified, can revoke the grant at once under connected apps, and can pause a webhook to stop deliveries.

The outbound call tool prepares a call that a person reviews and places from the browser, template versions reach recipients only once submitted, and destructive tools carry annotations so the agent host can ask before running them.

Sends of email, SMS and WhatsApp go out when the agent calls the tool, with no Bird approval step in between, and handing a conversation to a person is left to the customer's own systems.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Guardrails are a field in the agent's Advanced settings with their own configuration page, where the customer selects content filters that detect and block harmful content in agent conversations, controlling what the agent can and cannot discuss. Release control sits with the customer too, since a configured agent stays a draft until a named version is created and explicitly activated for production, with earlier versions available to roll back to.

Each MCP server carries an Allowed functions list naming what it may do when called. When automation reaches its limit the conversation transfers to Inbox with the complete history, so the customer does not have to start over with the human agent, who works with an Inbox copilot. Infobip does not describe an approval step before an individual agent action goes out.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-guardrailsread 2026-09-05

Teams are organized into workspaces with member roles, API keys are scoped per channel with none, read or write access to email, SMS and WhatsApp, and agent access runs on OAuth grants limited to what the user holds and approved. Bird holds ISO/IEC 27001:2022, SOC 2 Type 2 and SOC 3 reports and HIPAA compliance, and its trust center supplies an ISO certificate bundle, statement of applicability and penetration test letters on request. Bird does not mention single sign on for its dashboard.

Sourcebird.com/securityread 2026-10-11

Infobip is audited regularly against ISO/IEC 27001, 27017, 27018 and 22301 and the ISAE 3000 standard, assessed annually, with certificates available for download at infobip.com/certificates and a full or summary copy of current reports provided on written request. It also holds a HIPAA attestation under SSAE 18, and its sub-processor list, data transfer agreement, data retention notice and privacy notice are all public at named URLs.

Single sign on works through any SAML 2.0 identity provider with SP-initiated flow, with identity-provider groups mapped to custom roles and re-synchronized on every login, and role-based access control with predefined and custom roles governs per-feature permissions. Admins can set two-factor authentication to be remembered or required at each login, and password validity and maximum login attempt policies, IP safelisting and separate API access permissions complete the controls. Infobip's identity, authentication and fraud prevention products are things it sells to its customers, not controls over the customer's own tenant.

Sourceinfobip.com/docs/essentials/manage-my-account/account-settingsread 2026-09-05

Audit logs record changes such as API key updates and member invitations, each webhook attempt shows the agent platform's response status and body or a failure reason, and call records and voice events track phone calls, with every message kept as a record in its region. That shows what reached the agent and what Bird sent. The agent's own reasoning and tool sequence are logged in the platform that runs it.

Sourcebird.com/securityread 2026-10-11

Insights and Analytics, one of the five AgentOS products, monitors AI agent performance, tool usage and session tracking through dedicated dashboards, with every interaction across all five products feeding it and the output covering performance metrics, root causes and AI-driven recommendations. Tool usage and session tracking record what an individual agent did, not only an aggregate.

From inside an agent, Go to Session history opens previous sessions with their analytics, and View as code renders the running configuration. Changes are tracked separately, since agents autosave up to ten draft versions, named versions are created and activated deliberately, and version history records what was live when. Infobip does not describe an immutable audit log with actor and timestamp for configuration changes.

Sourceinfobip.com/docs/insights-and-analyticsread 2026-09-05

Each organization picks the us1 or eu1 region at signup, starting from a guess based on location, and the choice is fixed afterward. The workspace, API keys, messages, recipient data and event logs stay in that region and are never copied across, with only sign in and account administration held globally. Keys carry their region in the prefix, and a request to the wrong region is refused with a 421 error.

Sourcebird.com/docs/api/regionsread 2026-10-11

AI agents are available only in five data centers, Europe (EU1), Sweden (SE1), Germany (FR4), India (MUNM) and United States (NY2), so an account sits in a named region across three continents and the customer can tell which.

Infobip publishes its full legal tier openly, a sub-processor list, a data transfer agreement, a data retention notice and a privacy notice, each at its own public URL, plus an infrastructure overview and network connectivity options.

Infobip offers no self service or other way for the customer to choose or move their region, placement appears to be set at account provisioning, and there is no on premise, private cloud or single tenant deployment.

Sourceinfobip.com/docs/ai-agents/ai-agents/overviewread 2026-09-05

Agent skills and plugins come for Claude Code, Codex, Cursor, OpenCode and Antigravity, including a CLI router skill and an email audit skill, plus AI builder guides and a setup prompt to paste into an existing agent. These equip an agent the customer already runs. Bird offers no ready made agents for support or sales.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Agent instructions can be filled from predefined templates, Appointment booking agent, Order status assistant and Sales representative, and Automation Studio has its own predefined and custom templates to speed up journey and chatbot creation.

Agents move as units, since an existing agent can be duplicated, exported to a .export file and imported into another workspace. Components are reusable logic blocks selected from a list and shared across agents. AgentOS itself ships as five named products a customer switches on. The template set is small, and there is no browsable marketplace of ready made agents.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

No model runs inside Bird. The customer's agent platform, whether Claude, Codex, Cursor, Grok or its own voice application, reaches Bird through the CLI, MCP or webhooks, and which model that agent uses is decided entirely outside Bird. The webhook connectors are set up for Claude Managed Agents and Grok, and any other platform receives the same event JSON through a plain webhook.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Under Advanced settings when configuring an AI agent, the Model field lets the customer select the LLM that best matches its requirements for reasoning capability, latency and cost, so each agent can run on a different model. It sits alongside Guardrails and structured output in the same settings panel, and the Instructions field acts as the system prompt for the underlying language model. Third party agents reaching Infobip through MCP are a matter of interoperability, not model choice.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

Every public endpoint sits in an API reference generated from an OpenAPI spec, with SDKs for TypeScript, Python and Go and a bird CLI for the shell. The MCP server comes in three forms, a hosted endpoint with the full tool catalog, a dynamic endpoint exposing only search and execute for clients with tool limits, and a local server inside the CLI. All three sign in through OAuth with dynamic client registration and PKCE, and their tools create and change Bird's own objects, such as messages, numbers, domains, senders, templates and contacts.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Infobip publishes an API reference, SDKs, release notes, an integrations catalog and a public roadmap, all reachable without a login, plus Postman collections, a GitHub organization and a developer Discord. Every channel is exposed as its own REST API, and the modular CPaaS X stack is sold specifically for platforms building on top.

On the agent side, MCP servers let an Infobip agent call outside systems with scoped allowed functions, and an agent's configuration can be viewed as code, exported to a portable file and imported elsewhere, with structured output constrained by a customer-defined JSON schema. Components let a developer encapsulate backend logic the agent then calls, and Exchange applications add partner integrations.

Sourceinfobip.com/docs/apiread 2026-09-05

Each webhook attempt can be inspected with the agent platform's response status and body or the reason a delivery failed, which traces why an agent did not run. Template versions stay away from recipients until they are submitted, so an agent's draft can go out as a test message and be checked on a real phone first. Testing what the agent itself says or does belongs to the agent platform the customer uses.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

AgentOS ships Quality center, a set of tools to monitor, evaluate and improve agent response quality, where the customer creates test groups, defines test cases, runs tests and reviews results to confirm agents behave as expected.

For Knowledge agents it validates responses against expected answers and tracks quality over time, producing a scored comparison. Separately, the build flow has a step before publishing, Test an AI agent, that validates agent responses and behavior, and agent versioning lets a team activate a specific version and roll back a bad one. The tests run against the customer's own agent.

Sourceinfobip.com/docs/ai-agents/quality-center/overviewread 2026-09-05

Agents use Bird through API calls, CLI commands and MCP tools for messaging, numbers and domains. No hosted browser, remote desktop or screen control is part of the platform. Even the outbound call tool stops short of acting on its own, preparing a call that a person reviews and places from the browser.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

An Infobip agent reaches other systems through three tool types, all programmatic, Components running backend logic, MCP servers called at an endpoint URL with scoped allowed functions, and Exchange applications from the integrations catalog, and its output side is the messaging estate of more than fifteen channels, each with its own API. AgentOS offers no browser control, hosted session, virtual desktop or interface automation, and nothing in the agent configuration offers a browser, a screen or a pointer.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05