Salesforce adds AI spending limits, with automated shutdown controls due in January
The Agent Fabric update pairs budget caps available now with planned evaluations that can trigger intervention when an agent’s quality slips.
Loading page…
The Agent Fabric update pairs budget caps available now with planned evaluations that can trigger intervention when an agent’s quality slips.
Listen to this story
Salesforce’s Agent Fabric expansion makes budget enforcement available before its evaluation-driven intervention workflow: FinOps Dashboard, Model Wallet, cost policies and an Agent Kill Switch are generally available, while Agent Evals and API Evals are scheduled for beta in November 2026 and general availability in January 2027. The distinction matters to buyers: automatic shutdown after a failed evaluation is still a roadmap item, so Salesforce advises basing purchasing decisions on released capabilities. Its claim of up to 75% lower token use comes from company test scenarios, not a promised reduction in customer bills.
FinOps Dashboard and Model Wallet provide consolidated spending views and hard limits that stop requests before costs exceed a budget.
Agent Evals is designed to test agents against quality thresholds in production and initiate predefined responses, subject to organizational approval rules.
API Evals will generate functional and performance tests from API specifications to catch breaking changes before production.
Salesforce is promising to stop failing AI agents, not just flag their mistakes. Its October 27, 2026 Agent Fabric announcement pairs spending limits available now with evaluations designed to trigger intervention. But the full automated shutdown path remains ahead: agent evaluations enter beta in November, and the triggered kill switch is scheduled for January 2027.
Agent Fabric is Salesforce’s shared management layer for governing agents across platforms. The expansion brings quality checks, budget enforcement and predefined responses into that layer, aiming to connect detection with action.
Agent Evals is designed to generate tests before deployment, then evaluate agents, language models and MCP servers against defined quality thresholds in production. A failed evaluation can initiate a predefined intervention, including the Agent Kill Switch, with approval when the organization’s policy requires it.
Salesforce illustrates this with a hypothetical retailer switching an order-support agent to a cheaper model. Tests detect inaccurate delayed-order answers and request approval to quarantine the agent. The team then revises its instructions and retests before restoring it. This is an intended workflow, not a customer result.
API Evals addresses a different failure point: changes to the application programming interfaces an agent depends on. Salesforce says it generates functional and performance tests from API specifications to catch breaking changes before production.
The FinOps Dashboard and Model Wallet give budget owners a consolidated view of AI spending and hard limits that stop requests before costs exceed budget, Salesforce says.
Salesforce says its Cost Optimization Policies can reduce token usage by up to 75% through semantic caching, payload compression and response trimming. That figure comes from company test scenarios, not a guaranteed deployment saving. It measures token usage rather than a demonstrated reduction in a customer’s total AI bill.
For buyers, the delivery split is consequential. Salesforce cautions that purchasing decisions should rest on fully released capabilities. The immediate purchase case rests on available controls; evaluation-driven intervention remains a scheduled addition.
Loading discussion...
Join the conversation
Explain when stopping bad answers should outweigh keeping the service running.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.