← All guides

Locus product guide · Updated

AI credits: how credit-based pricing works

AI credits are a prepaid unit that customers spend on AI work, with each action priced in credits instead of dollars. Vendors value them very differently: a GitHub AI Credit is worth $0.01, a Salesforce Flex Credit $0.005, and a Locus Pro credit $0.001. A credit model works when one credit has a fixed dollar value, every action has a published credit price with your margin built in, and expiry rules are stated before customers buy.

How much is one AI credit worth?

There is no standard. Each vendor picks a dollar value and decides what a credit buys. The values below come from vendor pages. Prices checked November 10, 2026.

How much is one AI credit worth?
VendorValue of one creditWhat credits pay forExpiry rules
GitHub Copilot$0.01 per GitHub AI CreditChat and agent work; code completions use no creditsThe monthly allowance resets each cycle; Pro includes $15
Salesforce Agentforce$0.005 ($500 per 100,000 Flex Credits)Agent actions; one action in its examples is 20 credits, or $0.10Not stated on the pricing page
LovablePlan rate of $0.25 on Pro and $0.50 on BusinessBuilding, chat, hosting, AI calls in deployed apps and some connectorsPlan credits roll over for 2 months; top-ups last 12 months
Locus Pro$0.001 (1,000 credits per $1)Paid API, data and model calls at catalog priceIncluded monthly credits expire each period; purchased credits never do

Why do AI products sell credits instead of dollars?

One balance can cover many kinds of cost. Lovable uses a single credit balance for building, chat, hosting, AI calls inside deployed apps, and connectors such as Perplexity and Firecrawl. GitHub charges AI credits for chat and agent sessions, while code completions stay unlimited on paid plans.

Credits also let you change what an action costs without changing plan prices, and prepaid credits bring in cash before your providers bill you.

The cost is clarity. When a credit has no fixed dollar value, customers cannot compare prices or predict a bill. A quiet change in credits per action then reads as a hidden price rise.

How do I set the credit price of each action?

Fix the dollar value of one credit first. Then price each action from its cost and a target margin: credits = cost ÷ (1 − margin) ÷ credit value, rounded up to a whole credit.

The example uses a $0.01 credit and a 40% target margin. Costs are Locus Pro catalog base prices from November 10, 2026. The research task is Claude Sonnet 5.5 with 20,000 input and 2,000 output tokens, plus three Brave web searches.

Rounding up to whole credits adds margin on cheap actions. A credit that is too large forces big rounding. One that is too small makes prices hard to read.

How do I set the credit price of each action?
ActionYour costCredits chargedPriceActual margin
Verify one email (Hunter)$0.00511$0.0149%
Transcribe a 30-minute recording (Deepgram)$0.130322$0.2240.8%
Research task with 3 web searches$0.150926$0.2642.0%

Should AI credits expire?

Treat credits you give away apart from credits customers buy. Included and promotional credits can expire each period. Purchased credits that disappear feel like a lost payment and invite disputes.

Real rules: Locus Pro's included monthly credits expire at period end, and purchased credits do not. Lovable rolls unused plan credits over but expires them 2 months after issue on monthly plans, and expires top-ups after 12 months. GitHub's included allowance resets every month.

If you run credits on Stripe Billing, a credit grant never expires unless you set an expiry date. Stripe's rules also bar using billing credits as gift cards or stored value, or to pay other businesses.

How do I give each customer a credit balance with Locus Pro?

Locus Pro Enterprise keeps one credit balance for each customer of your product, at 1,000 credits to the dollar by default. Customers top up by card through Locus-hosted checkout or the embeddable balance widget. Or you sell credits your own way and allocate them from your pool.

Each call names the customer with X-Locus-End-User and draws their balance at the catalog base price plus your markup. Example: Deepgram transcription is about 4.343 credits per audio minute in the catalog, so a 30-minute recording costs 130.29. With a 25% markup the customer pays about 162.86 credits and you keep about 32.57, roughly $0.033.

The customer sees a balance in credits. You see charges, margin and usage grouped by customer in the ledger and analytics. Locus Pro prices only the calls it runs, so credits for your own features, such as seats or exports, belong in your billing system.

How do I choose a credit design?

Credits suit products where the cost per action varies and buyers want to prepay. Plain dollar prices are clearer when you sell one kind of usage.

  • Publish a fixed dollar value per credit, even if the product shows only credits.
  • Price each action in whole credits from cost plus margin, and publish the table.
  • Show an estimate or a check-in before expensive actions. Lovable pauses a long build when it crosses a check-in level, 20 credits by default.
  • Let purchased credits last at least a year, and let included credits expire.
  • Put many cost types on one balance only if customers can see where their credits went.
  • If your credits pay for third-party API calls, Locus Pro gives you the balance, the calls and a per-customer ledger in one place.

Frequently asked questions

Are AI credits the same as tokens?

No. Tokens are what a model provider bills you for. Credits are a unit you define and sell. One action can use thousands of tokens and still cost a fixed number of credits.

How many credits should a plan include?

Size the allowance to what a typical customer uses in a month, priced at your margin. Most customers then use most of it, and heavy users buy more. Look at your real usage spread before you set the number.

Can I change how many credits an action costs?

Yes, but announce it. Changing the credits per action changes the real price. Publish the price table, date each change and give notice before it applies.

What happens when a customer runs out of credits?

Pick one rule and show it: stop the action, ask for a top-up, or bill overage. Locus Pro rejects a call with HTTP 402 before it runs when the customer balance is too low.

Implementation references

Use these first-party references for current request contracts and account requirements. Tool availability, prices, and negotiated terms can change.

Sources

Third-party details were checked on November 11, 2026. Vendors change pricing and features often, so confirm on their site before you decide.

Related guides