Loading

Understand the Salesforce Headless 360 Architecture

Publish Date: May 15, 2026
Description

What’s Changing

Headless 360 is a platform architecture announced at TDX 2026. The core idea: no browser required — the API is the UI. It decouples every layer of the Salesforce platform from the browser interface and exposes it to any AI agent, any model, or any tool. Headless 360 is a marketing umbrella term for a group of platform capabilities. It is not a single product or SKU.

Important: Headless does not mean Salesforce is removing its UI. It means Salesforce capabilities are no longer bound to a single interface. They can surface anywhere.

 

Why Salesforce Made This Change

The Agentic Enterprise requires AI agents that work not only inside a Salesforce browser tab, but where users are: in Slack, Microsoft Teams, ChatGPT, Claude, mobile apps, or custom-built applications. Before Headless 360, integrating Salesforce business logic into external surfaces required multiple months of custom middleware and API work. Headless 360 can compress that into days by making it the default, standardized way the platform operates. 

 

When Was This Released

Headless 360 was announced at TDX 2026 (April) in San Francisco. The following capabilities are Generally Available (GA) as of the announcement:

  • MCP (Model Context Protocol) — Salesforce Platform Hosted MCP Servers

  • Headless Experience Layer (HXL) — for rich messaging in Slack and ChatGPT

  • Agentforce Vibes 2.0 — supports Claude Sonnet and GPT-5 with free limited access in Developer Edition

  • DevOps Center MCP

  • Session Tracing

  • MuleSoft Agent Fabric, Agent Script (open source)

  • 60+ MCP Tools / 30+ Coding Skills

Rolling out May–June 2026: Testing Center, Salesforce Catalog.

 

The 4-Layer Architecture

Headless 360 is powered by the Salesforce Agentic Enterprise Architecture. Four independent platform layers: 

  1. Data 360 — A unified data foundation (System of Context) that gives AI and external tools accurate, silo-free information

  2. Business Logic — Apex, Flow, and business processes exposed as callable services

  3. Orchestration — Agent control via Agentforce and MuleSoft Agent Fabric, with multi-vendor support

  4. Headless Engagement Layer (HXL) — Deploy to any UI surface: Slack, Teams, ChatGPT, etc.

Resolution

How to Use Headless 360

 

MCP (Model Context Protocol) — Inbound access into Salesforce

MCP is the inbound path: how external agents and tools connect into Salesforce to read data and invoke business logic. 

Follow the developer documentation to get started: Salesforce Hosted MCP Servers.

 

Headless Experience Layer (HXL) — Outbound delivery to any surface

HXL is the outbound path: how Agentforce delivers rich, interactive experiences natively on external surfaces without a Salesforce UI. With HXL, the customer can:

  1. Configure the Agentforce agent once in Agent Builder.

  2. Deploy natively to supported surfaces. HXL for Slack and ChatGPT is GA. HXL for external surfaces including Microsoft Teams is in Beta, targeted for July 2026.

  3. No rebuilding of agent logic per interface is required. The same business intent, data access, and permissions defined in Agentforce travels with the agent to any surface.

 

Licensing Considerations

  • Basic MCP access is included in Enterprise Edition and above. No additional Agentforce SKU required.

  • Flex Credits apply for Agentforce actions invoked via MCP and Data 360 queries via MCP.

  • Pre-built Agentforce agents (SDR Agent, Service Agent, etc.) still require their own licenses.

 

Common Questions

Does Headless 360 mean Salesforce is removing the UI?

No. Headless 360 decouples capabilities from the UI but does not eliminate it. Users who need the Salesforce browser interface will continue to use it as before. Headless 360 makes Salesforce capabilities available beyond that interface, not instead of it. 

 

What is the difference between MCP and HXL?

MCP (Model Context Protocol) is the inbound path: how external agents and tools connect into Salesforce to read data and invoke business logic. HXL (Headless Experience Layer) is the outbound path: how Agentforce delivers rich, interactive experiences natively on external surfaces like Slack, Teams, and ChatGPT. Think of MCP as the "in" and HXL as the "out." 

 

Do customers still need Agentforce if they use Headless 360?

Yes. MCP is an access pattern, not a complete operating model. Agentforce provides the governance layer that no DIY solution has on day one: Testing Center, Session Tracing, configurable guardrails, observability, and full agent lifecycle management (build → test → deploy → monitor → improve). Without governance, agents produce unpredictable results in production.

 

Does licensing still apply when accessing Salesforce through an external AI tool like Claude?

Yes. Even when accessing Salesforce through an external AI tool via MCP, the request is authenticated and authorized through Salesforce's Trust Layer. The user or service account making the call must have a valid Salesforce license. Object- and field-level security still enforces what data is returned. The security model travels with the data, regardless of what surface accesses it. 

 

Is Headless 360 entirely new, or did these capabilities exist before?

Most individual pieces existed before — Salesforce has always had REST/SOAP APIs, MuleSoft could already orchestrate SAP <-> Salesforce flows, and Data 360 already had activations and segments. What is new is the integration that Salesforce business logic (Flows, Apex, and agents) is now directly callable via MCP tools out of the box, using an open standard that any AI tool can connect to.

 

Available API, MCP, Metadata and Skills

Associated Websites

Additional Resources

Trailhead: Salesforce Headless 360: Quick Look

Knowledge Article Number

005360285

 
Loading
Salesforce Help | Article