How it works
Each action on the rate card is priced in credits or currency, ideally in proportion to what it costs you to serve. When upstream costs change, such as a new model that is cheaper or more expensive, you update the rate card rather than the credit price, so existing balances keep their value.
Keep the rate card in one place that both the product and the pricing page read. A rate card that lives in documentation while the code deducts different amounts is the usual cause of billing complaints.
Example
An assistant's rate card: a fast-model reply costs 1 credit, a reasoning-model reply 5 credits, an image 8 credits, and a 1-minute voice clip 12 credits. At $0.01 per credit, a user who sends 100 fast replies and 4 images spends 100 + 32 = 132 credits, or $1.32.
Rate card in Cred
Your rate card lives in your server code: each call to deduct names the credit type and amount for the action. Pricing tiers and the credit type's USD-per-credit rate set the money side, so you can change either without touching the other.
Pricing Tiers docsQuestions
- Should a rate card be public?
- Usually yes. Customers who can see that an image costs 8 credits can predict their spend, which reduces support tickets and refund requests.
- How often can I change a rate card?
- As often as costs change, but announce increases in advance. Changing what credits buy after customers have paid for them is the change most likely to feel unfair.
- Should the rate card be priced in credits or dollars?
- Credits keep the rate card stable when you change pack prices or run promotions, and let one balance cover actions with very different costs. Showing an approximate dollar value next to each action helps customers compare.
