The licence is the easy part of a Vibes budget. The harder question is how much useful, reviewed work a team gets from the prompts it pays for. A generated Flow that needs a day of correction is not cheaper simply because generation took a minute.
Checked 30 October 2026. Salesforce lists Vibes consumption through Flex Credits and flat-fee access at $125 per user per month. Foundations provides a starting route. Before assigning licences, separate the exploration allowance in your org from the paid entitlement you intend to use.
Start with a small, reviewable job
A useful first job is a sandbox change with a clear owner and a visible result: add a validation rule, explain an existing Flow, or write a focused test around a known requirement. Avoid starting with a request to rebuild a whole business process. You need a baseline for correct output before you can judge speed or cost.
For example, a fictional returns team wants a Case field called Return_Approved__c. Before asking for automation, agree whether it means approved by policy, approved by a person, or refunded. Those are different states. Write one positive example, one rejection and one permission failure. This definition is a review tool you can keep even if the generated implementation is discarded.
How metered prompt usage becomes credits
The Vibes billing guide counts combined input and output tokens in blocks of up to 2,000, rounded up. The selected model maps to a prompt usage type, which has its own credit multiplier. Model choice can therefore affect consumption even when the price of a credit is unchanged.
A fictional request using 5,100 combined tokens produces three prompt units. If the applicable rate card assigns C credits to that usage type, the request consumes 3 × C credits. At $0.005 per credit, the cost is 3 × C × $0.005. Keep C as the current contractual multiplier; substituting the standard agent-action rate would mix two billing concepts.
A fair comparison with the flat fee
Take a four-person team as an illustration. Four $125 seats are $500 per month before other applicable charges. Compare that with the team’s observed metered spend across a representative month, rather than multiplying one unusually short prompt by an optimistic daily count. Include lengthy explanations, corrections and repeated attempts.
Flat-fee access still has conditions. The developer guide documents a premium allowance of 2,500 requests or 36 million tokens per user per org, whichever is reached first, resetting every 30 days after first use. Included-model fair use and the option to switch to metered use also matter. Check current model entitlements and the contract before enabling a paid fallback.
Measure accepted changes, not generated lines
Keep a simple pilot log: task, model, prompt units, wallet consumption, review minutes, defects and whether the change passed its acceptance checks. Count a change as complete only when someone has reviewed its permissions, behaviour and deployment result. A model can save typing while leaving the expensive decisions untouched.
For the returns example, ask a reviewer to test a permitted approval, an ineligible return, a missing policy field and a user without approval access. Inspect the actual metadata diff. Reject unexpected field additions or permission changes even when the happy path works. Retain the previous version and document how to restore it.
Give the assistant useful context
Explain which fields are authoritative, who owns them and which automations already write them. A populated field is not necessarily the correct source of truth; an empty one is not necessarily unused. FieldRat’s metadata readiness checklist shows how to assemble that evidence without treating a scan as permission to delete.
Vibes is a development workflow. A production customer-facing agent is a separate operating workload with its own permissions, evaluation and commercial terms. Use our Agentforce pricing guide for that distinction. For a delivery team, the practical goal is a smaller reviewable change, not a larger prompt.
Talk through the developer capacity and review process before buying seats for an entire team.
Set up a reviewable Vibes pilot
Define a small sandbox task, its acceptance checks and the usage log before buying seats for the team.
Four fields, no call required. We reply within one business day.
Frequently asked questions
Is Agentforce Vibes free?
Salesforce offers a way to get started through Foundations. Trial allowances and paid entitlements are different. Check the allowance assigned to your org before treating an experiment as an ongoing production budget.
Does one Vibes prompt equal one billing unit?
No. Metered prompt usage rounds combined input and output tokens up in 2,000-token increments. The model determines the prompt usage type and its Flex Credit multiplier. A long prompt can consume several units.
Does a flat fee remove all limits?
No. Salesforce documents premium-model allowances and fair-use conditions. Check the current billing guide and your contract, including what happens when an allowance is exhausted.