The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Salesforce discusses partner concerns over new AI agent billing model (opens in a new tab)

Readers will learn how Salesforce plans to charge Flex Credits for external AI agent interactions via MCP and APIs, and what partners are urging the company to adjust regarding predictability and friction.

Salesforce has introduced a pricing model requiring external artificial intelligence agents to register on the platform and consume Flex Credits for every successful call made through the Model Context Protocol or direct application programming interfaces. The initiative tracks each interaction as a Headless Platform Interaction, shifting costs away from traditional seat licensing toward usage-based billing for agentic traffic.

The announcement triggered significant pushback from implementation partners and independent architects who warned that per-action charges would create financial friction and discourage developers from building around the platform. Critics noted that customers already face heavy seat costs and questioned whether the market would accept paying for every individual request made by automated systems.

In response to the community reaction, Salesforce leadership initiated direct conversations with key ecosystem stakeholders to address these concerns. Participants emphasized the need for transparent pricing structures, additional platform value to justify the fees, and mechanisms that allow partners and administrators to continue leveraging artificial intelligence tools without unexpected production expenses.

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

Worth reading?

Using Agentforce Vibes Skills to inspect and configure your Salesforce org (opens in a new tab)

Readers will learn how to access the prebuilt Skills library in Agentforce Vibes and use them to inspect, modify, and deploy metadata changes through a plan and verify workflow.

Why read this

The guide demonstrates practical administration tasks like creating reports and Record-Triggered Flows without writing code.

The article introduces Agentforce Vibes as a browser-hosted Visual Studio Code instance configured specifically for Salesforce development and administration. Although it functions as a developer environment, the piece emphasizes its value for administrators by focusing on the Skills feature, which bundles instructions for distinct configuration actions into reusable packages.

Administrators can browse the preinstalled Skills library through the Toolkit menu after launching Vibes from Setup. The system automatically detects verbs in user prompts and maps them to the appropriate Skills, allowing the agent to execute tasks efficiently without manual selection. Users can also manually add new Skills to expand the toolkit over time.

Changes made through Vibes follow a strict plan, verify, and deploy sequence. Modifications are initially written to the virtualized local filesystem rather than directly to the connected org. Administrators review the generated change plan, approve it, and then trigger deployment using built-in commands or conversational prompts, with the agent handling connection tokens and API calls behind the scenes.

The author strongly recommends testing these workflows in trial environments such as Scratch Orgs, Developer Edition, or sandboxes. Example use cases include creating Custom Objects, adding fields, generating Permission Sets, running SOQL queries, and building Record-Triggered Flows. While early deployments may encounter errors or require multiple attempts, the structured approach provides a safe way to explore AI-assisted platform configuration.

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

Worth reading?