Credits and Billing
Credits are the unit of consumption for ConnectWyze's rendering and processing features. Each workspace has its own balance.
What it is
Every workspace has a credit balance made up of two pools:
- Tier credits — allocated on a monthly cycle based on your plan. These reset on a configurable day of the month.
- Purchased credits — credits you buy on top of your tier allocation. These do not reset.
Credits are consumed when ConnectWyze does computational work: rendering an image, removing a background. Credits are not consumed for reading, editing, or previewing.
When you'd use it
- You want to understand what costs credits before launching a large workflow run.
- You need to check your current balance before a batch render.
- You want to review your credit usage history to understand which operations consumed the most credits.
- Your workflow job stopped with an "Insufficient credits" error and you need to add credits to resume.
Quick start (user)
Check your credit balance
Go to Settings → Billing (/dashboard/settings/billing). The page shows:
- Tier credits remaining and when they next reset
- Purchased credits remaining
- Combined available balance
View credit usage history
On the Billing page, the usage history table lists each credit-consuming operation: the operation type, credits used, and a timestamp.
Add credits
Contact your account manager or use the top-up option on the Billing page (/dashboard/settings/billing) to purchase additional credits. Purchased credits do not expire.
Settings reference
Credit pools
| Pool | Resets? | Source |
|---|---|---|
| Tier credits | Yes — monthly, on your plan's reset day | Included with your plan |
| Purchased credits | No | Bought separately; added to balance permanently |
Credits are drawn from the tier pool first, then from the purchased pool.
Operations and credit cost
| Operation | Credits consumed | Notes |
|---|---|---|
| Render a template image (workflow or API) | 1 per render | Cache hits are free — identical inputs within 24 hours return the cached result |
| Background removal | 1 per unique image processed | Hash-based dedup: the same source URL processed again is free |
| Regenerate an existing image | 1 per render | Same cost as a fresh render |
Pre-flight check
Before rendering, ConnectWyze checks that the workspace has enough credits. If the balance is insufficient, the operation is rejected immediately with an error:
Insufficient credits. This render needs N credits but you have M available. Add X more credits to continue.
Workflow jobs halt at the point of exhaustion — completed images are saved, and the remaining items are not rendered.
Cache behavior
The generate API and workflows cache render results by input fingerprint (template + variables + format + quality). A cache hit returns the stored image URL without performing a new render and without consuming credits. Cache hits are valid for 24 hours.
Troubleshooting
| Symptom | Fix |
|---|---|
| "Insufficient credits" on the generate API | Your workspace has no credits remaining. Purchase additional credits from Settings → Billing, then retry. |
| Workflow job stopped mid-run | The workspace ran out of credits during the job. Top up your balance, then re-trigger the workflow for the items that were not rendered. |
| Balance looks correct but API still returns 402 | There may be a concurrent workflow draining the balance. Wait for the running job to complete, then retry. |
| Usage history shows more credits than expected | Background removal charges once per unique source image URL. If the same URL was submitted with different options, each unique option set is a separate charge. |
| Tier credits did not reset on the expected day | Reset runs on the configured reset day of the month. Contact support if it has not processed within 24 hours of that date. |