Editorial illustration of an iPhone screen showing WhatsApp settings leading to a third-party agent chat setup with an API key field and a separate dedicated chat interface.

WhatsApp’s iPhone beta is testing third-party agent chats set up from settings with an API key.

WhatsApp is testing third-party agent chats on iPhone in WhatsApp beta for iOS 26.37.10.70, available through TestFlight, and the biggest distinction is that these conversations do not use WhatsApp’s standard end-to-end encryption. In this limited beta, users can create up to five agents from WhatsApp settings by adding a name, profile photo, and API key. That turns WhatsApp into a front end for external agent services without requiring a separate app, but it also creates a different privacy boundary from a normal WhatsApp thread. The test is only live for a small number of beta users in select countries.

WhatsApp’s iPhone beta adds third-party agent chats

The iPhone rollout extends a feature WhatsApp had already started testing in Android beta, bringing the same basic agent setup into the iOS app. The flow sits inside WhatsApp settings rather than in a standalone tool, which means the feature is designed to plug directly into the existing app experience. For operators and business users, that is the practical shift: WhatsApp is experimenting with making external services reachable from within the chat app itself.

Each account can hold up to five agents, which puts a clear cap on the current test. For each one, the setup requires three concrete pieces: a name, a profile photo, and an API key. That structure suggests WhatsApp is treating these as distinct identities inside the app rather than as a loose add-on. It also means access is tied to whatever third-party service or bot the user connects, not to a built-in WhatsApp assistant.

Agent chats stay separate from normal WhatsApp threads

WhatsApp is drawing a hard line between these agent chats and the rest of a user’s account. An agent cannot see a user’s other chats, contacts, or device media, and it only gets access to content that the user explicitly shares in that dedicated conversation. In practical terms, the feature creates a contained workspace instead of giving an outside service broad visibility across the app.

The system is not limited to AI models. The same setup can also connect scripted bots, which broadens the possible use cases beyond generative AI and into simpler workflow automations. If a user wants to stop using one service or swap to another, WhatsApp also lets them reset the API key. That gives users a direct disconnect mechanism, even though the exact range of supported third-party services and tasks is still unclear.

The privacy tradeoff and rollout limits

The main caution is straightforward: these chats sit outside WhatsApp’s standard end-to-end encryption model. Messages are handled through a Meta-operated service, and the third-party developer connected to the agent may be able to access the conversation. For users who rely on WhatsApp’s default privacy protections, that changes how sensitive information should be treated inside an agent chat.

The feature is still narrowly scoped. It is limited to a small group of beta testers in select countries, there is no public launch date for a broader release, and disappearing messages are not supported in these chats. For now, the update matters less as a mainstream iPhone launch than as an early signal of where WhatsApp could go next: adding external agents and bots as a new workflow surface inside the app, but with rules and tradeoffs that differ from ordinary WhatsApp messaging.

Disclaimer: This article was created with the assistance of AI. Images are for illustrative purposes only.

About the author

Samarth Agrawal
Samarth Agrawal

Samarth Agrawal is an AI and technology professional who writes about WhatsApp, automation, and emerging AI trends. He focuses on simplifying complex tech updates into practical insights for businesses, creators, and everyday users