Salesforce adds Agent Evals, API Evals and hard cost limits to its Agent Fabric control plane
Salesforce announced Agent Evals, API Evals and hard spending limits for Agent Fabric, its AI agent control plane, on 27 October 2026, with betas in November.
By Emre AlemdarPublished
Tech AI LatestSalesforce announced on 27 October 2026 new evaluation and cost features for Agent Fabric, its agent control plane. Agent Evals generates tests before deployment and keeps checking agents, LLMs and MCP servers in production, with an Agent Kill Switch for failures. API Evals tests APIs from their specifications. A FinOps Dashboard, Model Wallet and Cost Optimization Policies set hard spending limits. Agent Evals and API Evals enter beta in November 2026 and reach general availability in January 2027.
Key facts
- Announced: 27 October 2026 (Salesforce newsroom)
- Agent Evals: pre-deployment test generation plus production checks of agents, LLMs and MCP servers; beta November 2026, GA January 2027
- API Evals: functional and performance tests generated from API specifications; beta November 2026, GA January 2027
- Cost controls: FinOps Dashboard, Model Wallet and Cost Optimization Policies are generally available now; Salesforce says policies cut token use by up to 75% in test scenarios
- Scale claim: Agent Fabric handles over 1.2 billion requests a day, Salesforce says
- Pricing: not stated in the announcement
What Salesforce announced
Salesforce announced on 27 October 2026 an expansion of Agent Fabric, which it describes as an AI control plane for managing and governing agents across platforms. The company's argument is that agents can fail silently, giving wrong answers and running up costs without anyone noticing. Salesforce says Agent Fabric already handles over 1.2 billion requests a day.
The first new feature is Agent Evals. It generates tests before an agent is deployed, then evaluates agents, large language models and MCP servers in production against quality thresholds. When results fall short, it triggers predefined interventions, including the Agent Kill Switch, with approval steps where a team's policy requires them. The second is API Evals, which generates functional and performance tests from API specifications to catch breaking changes before production. Both enter beta in November 2026 and are scheduled for general availability in January 2027.
What the cost controls do
The cost features are available now. The FinOps Dashboard and Model Wallet give one view of AI spending and apply hard limits that stop requests before a budget is exceeded. Cost Optimization Policies use semantic caching, payload compression and response trimming, and Salesforce says they reduced token usage by up to 75% in test scenarios. The company gives no pricing for any of the new features.
Two further updates widen the scope of the control plane. A Custom Agent Scanner, in beta now with general availability in January 2027, extends discovery to internal environments, systems behind firewalls and third-party platforms, and catalogs agents, models, MCP servers and APIs in an Agent Registry. Open Policies for Federated API Gateways apply rules such as IP allowlisting or rate limiting across gateways from Azure, Apigee and Kong in one action; this is generally available now. A Triggered-Agent Kill Switch is due in January 2027.
Why it matters
Most agent frameworks ship evaluation as a developer tool. Salesforce is selling it as an operations layer that sits above agents built on other platforms, with the ability to quarantine an agent automatically. The example in the announcement shows the intended loop: a retailer moved its order-support agent to a cheaper model, scheduled tests caught inaccurate delayed-order answers, the system asked for approval to quarantine the agent, and the team fixed the instructions and returned it to production. Customer quotes come from ASICS Digital, Capita, GE Appliances and Newell Brands. Andrew Comstock, senior vice president and general manager for MuleSoft and Agent Fabric, is quoted saying enterprises can only scale agents as fast as they can keep them accurate and on budget.
Two claims in the announcement are worth separating from the product facts. The 75% token reduction is from Salesforce test scenarios, not customer deployments. The statistic that fewer than half of organizations evaluate agents on live traffic is attributed to a LangChain survey, and the 96% multi-platform figure comes from sponsored content.
What to watch next
The betas start in November 2026, so the first independent accounts of Agent Evals in use should appear before the January 2027 general availability date. Pricing is not stated, and the announcement names no specific models or agent platforms beyond the Azure, Apigee and Kong gateways. More coverage of agent products and governance is collected under AI Agents.
What changed
| Before | Agent Fabric offered an Agent Registry, an Agent Kill Switch and gateway policies, with no built-in evaluation of agents in production and no hard spending limits |
|---|---|
| After | Agent Evals and API Evals in beta from November 2026, a Custom Agent Scanner in beta, and generally available FinOps Dashboard, Model Wallet and Cost Optimization Policies with hard limits |
| Who it affects | Enterprises running agents across several platforms, MuleSoft and Agent Fabric customers, and teams responsible for AI spend |
Questions people ask
- When will Salesforce Agent Evals be available?
- Salesforce says Agent Evals and API Evals enter beta in November 2026 and become generally available in January 2027.
- What does the Agent Kill Switch do?
- It stops an agent when evaluations fall below a quality threshold, with an approval step where team policy requires one. The current Kill Switch is generally available; a Triggered-Agent Kill Switch is due in January 2027.
- How much do the new Agent Fabric features cost?
- Pricing is not stated in the announcement.
Sources
Reference pages
- Salesforce company
Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.
Comments
Loading comments.
