The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Salesforce plans agent identities and metered billing for Agentic API calls (opens in a new tab)

You will learn what Agentic Identity and Headless Platform Interactions are, which calls count toward Flex Credits, and when the transition deadlines and production-only billing rules apply.

Why read this

The exact multiplier is still unannounced.

Traditional integrations

  • Existing pricing kept
  • Existing security kept

Registered agents

  • Counted as HPIs
  • Drawn from Flex Credits
Traditional integrations keep existing terms, while agentic interactions move to the new HPI model

Salesforce has described upcoming changes to AIforce and the Headless Toolkit in its help documentation. The main changes are agent-specific security features, agent registration, and a consumption-based billing model. Agentic Identity would give AI agents their own identity rather than having them act under the identity of the human they assist, allowing separate credentials, finer permissions and better oversight.

Successful calls by registered agents, whether through MCP or direct APIs, will be counted as Headless Platform Interactions and drawn from Flex Credits, monitored through Digital Wallet. The author stresses that the Flex Credits multiplier has not been announced, agentic consumption is not yet metered, and Salesforce will give 30 days’ notice before metering begins. Traditional integrations keep their existing pricing and security arrangements.

Transition timing differs by customer type: new customers must register agents via APIs within three months of the Agentic Identity availability notice, existing API customers migrate at renewal, and MCP server users have three months from notice. Sandboxes, Scratch Orgs and Developer Edition orgs will not consume Flex Credits for HPIs. The author argues architects will need to plan for call volumes, permissions, monitoring and cost forecasting for multi-call agent tasks.

Read the original at dev.to (opens in a new tab)

Worth reading?

Salesforce announces Agentic Identity and flex credit adjustments for Model Context Protocol servers (opens in a new tab)

Readers will understand how Model Context Protocol servers connect Salesforce to external systems through natural language prompts.

Why read this

They will also learn about the upcoming November changes to the flex credits model and the new Agentic Identity framework for agent permissions.

The article introduces Model Context Protocol servers as a standardized interface for linking artificial intelligence hosts to enterprise systems like Salesforce. It outlines a three-part architecture comprising a host application, a client, and a server that securely exposes tools and resources. This design aims to replace custom integrations by allowing large language models to automatically discover and execute connected capabilities.

Practical examples demonstrate how sales and support teams can retrieve pipeline data or automate cross-platform workflows using simple natural language commands. These scenarios eliminate the need to manually switch between separate applications and navigate multiple forms to complete routine tasks.

Financial and governance impacts are also addressed, noting that agent-driven calls will begin consuming standard flex credits in November. The piece explains the introduction of Agentic Identity to distinguish between standard user operations and scoped agent permissions. Testing environments including Sandboxes and Scratch Orgs remain exempt from these billing changes, allowing teams to evaluate the technology safely before production deployment.

Read the original at Nebula Consulting (opens in a new tab)

Worth reading?

Recommended

New Flex Credit pricing for AI agents risks pushing customers toward ungoverned architectures (opens in a new tab)

Readers will learn how Salesforce plans to charge Flex Credits for AI agent interactions through MCP and direct APIs, and why this pricing structure creates financial pressure to bypass governed platform access.

Why read this

The article outlines practical steps for modeling usage volumes and optimizing agent workflows to control costs without compromising security.

Salesforce intends to bill Flex Credits when third-party AI agents successfully call into the platform via MCP or standard APIs. This pricing strategy conflicts with the company’s push for structured, governed machine access, creating a financial incentive for customers to minimize platform interactions.

Charging per successful interaction can lead to double billing alongside external AI vendor costs. Because autonomous agents generate significantly more API calls than human users, the cumulative expense grows quickly. Teams facing these costs may resort to duplicating data externally or routing logic outside Salesforce to avoid fees, which undermines the intended security and traceability benefits of Agentic Identity and the Headless Toolkit.

The author advises teams to accept the current policy while proactively modeling worst-case usage scenarios to forecast expenses. Practitioners should track exact interaction volumes, prepare data for negotiations with account executives, and optimize agent designs to reduce unnecessary calls. The guidance emphasizes maintaining governed architectures rather than building workarounds that violate platform policies.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?