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?

Recommended

Implementing email verification workflows in Salesforce beyond standard Validation Rules (opens in a new tab)

You will learn how to distinguish between email formatting checks and actual deliverability verification, and how to build a reliable workflow using Custom Fields, flows, and external APIs.

Why read this

The piece outlines trigger points, error handling, and monitoring metrics to maintain CRM data quality.

The article distinguishes between email validation, which enforces syntax through a Validation Rule, and email verification, which confirms domain existence, mail server configuration, and mailbox deliverability. Standard format checks cannot prevent bounces or identify disposable addresses.

It recommends placing verification at record creation, during field updates, or through bulk cleanup processes. A practical workflow involves creating a Custom Field, defining trigger events, calling an external verification service via API or managed package, and applying business rules to route verified, invalid, or risky addresses accordingly.

Developers are advised to handle inconclusive results gracefully, avoid redundant processing, maintain audit trails, and respect consent and privacy requirements. The author notes that while custom integrations offer flexibility, native applications can reduce maintenance overhead, and ongoing monitoring of bounce rates and verification metrics ensures the workflow actually improves data quality.

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

Worth reading?