Meridian's pet-owner mobile app is a custom-built native app, not an Experience Cloud site. Product wants the Service agent's conversational experience embedded directly inside that app's chat screen, with the mobile team controlling their own UI while calling into the Agentforce backend for responses. Which mechanism should the mobile team use?
Select an answer to reveal the explanation.
Short Explanation
The Agent API is the loading dock built for exactly this: any custom app, in or out of Salesforce, backs a truck up and calls the agent directly. A native mobile app that isn't Experience Cloud is the textbook case for it.
Full Explanation
The Agent API exists specifically to let a custom or external application - one that is not a supported native channel like Experience Cloud, email, or Slack - call a deployed Agentforce agent directly and build its own UI around the responses. A native mobile app that Meridian built independently is precisely that case, so the mobile team calls the Agent API from their app.
The digital experience channel option is the closest-looking trap: it is a real, supported way to deploy an agent's conversational experience, but it is built for Experience Cloud sites specifically, with Salesforce providing much of the front-end chat surface. A custom native app is not an Experience Cloud site, so that channel deployment path does not apply here. MCP is for an agent consuming external models or tools as context, not for an external app consuming the agent's conversational output - the direction is backwards. The agent-to-agent protocol only applies when the other party is itself an Agentforce agent reasoning independently; a mobile app is a client application, not a peer agent.
Exam takeaway: Agent API is the integration point for embedding an agent into anything outside Salesforce's supported native channels.