Salesforce Headless 360: what it is, and why it is now called SIforce

By Giorgio Bonan. Updated October 21, 2026, published October 21, 2026.

Salesforce Headless 360 is the layer that exposes every Salesforce capability as APIs, MCP tools and CLI commands, so AI agents can work in Salesforce without its screens. Announced at TDX on 15 April 2026, it was renamed AIforce at Dreamforce in September, then SIforce on 9 or 10 October 2026.

Same layer, three names in six months. Most of the confusion around it comes from guides written under one name and read under another.

The three names, dated

The developer documentation still uses the Headless 360 name for the MCP server as of 21 October 2026. When you search the docs, search for "Headless 360"; when you read news after mid-October, expect "SIforce".

What it actually is

Salesforce's framing, in Parker Harris's words on the Salesforce Developers blog: why should you ever log into Salesforce again? The answer is a set of pieces that already existed, packaged together.

The Headless 360 MCP Server is the interesting part for sales teams, because it is what the Salesforce in Claude plugin calls. Instead of exposing thousands of features as separate tools, it offers four: Discover (search the available operations), Describe (read one operation's specification), Dispatch (run it) and Dispatch Read-Only. At beta launch it offered dozens of operations, most of them Setup tasks for admins, with the library growing each release.

What Agentforce Vibes brings with it

The Register's TDX report describes Agentforce Vibes as a browser-based IDE built on Visual Studio Code, with the Salesforce CLI, extensions and org metadata preconfigured. Its default model at launch was Claude Sonnet 4.5, with a plan mode and an act mode, and predefined skills such as creating custom tabs or generating flows. The free Developer Edition carried usage limits of 110 requests and 1.5 million tokens per month.

For a sales org, this matters less than it sounds: it changes how admins and developers build, not what sellers see.

Security model

Every hosted MCP transaction runs as the authenticated user, through an External Client App with the mcp_api scope. CRUD permissions, field-level security, sharing rules and permission sets all apply: if a user cannot do something in Salesforce, an agent acting for them cannot either. Salesforce's own guidance is to make clients ask for approval before any tool that changes configuration or deletes data, and to test configuration changes in a sandbox first.

What it will cost

Salesforce Help's "Understand AIforce Impact" article, published 17 September 2026, describes the billing model planned for November 2026:

• admins register each agent, which gets its own identity and can hold narrower permissions than a human user;
• every successful call from a registered agent, over MCP or API, counts as a Headless Platform Interaction, tracked in the Digital Wallet and paid in Flex Credits;
• the rates are listed as "TBA", and Salesforce will give 30 days' notice before metering starts;
• sandboxes, scratch orgs and Developer Edition orgs are not metered.

Until those rates are published, nobody can price a month of agent traffic precisely. The Salesforce MCP guide covers the API allocation that applies in the meantime.

What it changes for a sales team

• Your CRM data becomes the interface. Whatever an agent says about a deal comes from the fields and activities in the org. Stale close dates and empty next steps travel straight into the answer.
• Your admin's job grows. Registering agents, scoping their permissions and watching the Digital Wallet become routine work.
• The name will keep moving. Budget, security reviews and contracts should name the capability (hosted MCP servers, agent registration) rather than the brand of the month.