Usage, Run Credits, and AI Credits
MergeLoom billing is organized around review outcomes and managed AI usage.
The two most important concepts are run credits and Cloud AI credits.
Run Credits
Section titled “Run Credits”Run credits cover PR/MR outcome allocation. They apply to Cloud Hosted and Self Hosted plans.
Run Credit Events
Section titled “Run Credit Events”Use this table when a run fails, is blocked, or needs recovery.
| Event | What normally happens |
|---|---|
| Ticket is denied before execution | No review output is created. Fix intake, assignment, routing, or eligibility, then resync or move the item back to ready. |
| Run is blocked before code changes | Check job detail and Billing. Treatment can depend on the workspace plan and where the block happened. |
| Validation fails before PR/MR creation | No review request is published. Required validation failures block output; credit treatment can depend on plan. |
| PR/MR is created or updated | A run credit can be used because MergeLoom produced review output. |
| Retry Publish succeeds | A prepaid run credit can be used because MergeLoom creates or updates review output from stored branch artifacts. |
| Continuation comment starts another run | The new attempt has its own audit, validation result, and usage record. |
| Cloud Hosted model call starts | Cloud AI credits can be reserved and then settled from measured usage. |
If run credits are exhausted, fix Billing before debugging provider settings.
Cloud AI Credits
Section titled “Cloud AI Credits”Cloud AI credits are for Cloud Hosted model usage through MergeLoom-managed provider access.
Cloud AI credits are separate from run credits:
- run credits track PR/MR outcome allocation
- Cloud AI credits track managed AI provider usage
- Self Hosted provider costs are normally paid directly to your provider
Cloud Hosted workspaces can require verified email and a verified payment method before cloud execution is available.
Self Hosted Provider Billing
Section titled “Self Hosted Provider Billing”In Self Hosted mode, MergeLoom runs inside your environment and uses your configured provider path.
That means:
- your provider account receives provider charges
- your worker stores local provider readiness and execution evidence
- MergeLoom run credits still apply to product usage
- Cloud AI credit balances usually do not apply to Self Hosted provider calls
Plan-Gated Features
Section titled “Plan-Gated Features”The UI may show locked or upgrade-required states for:
- audit retention or export
- Code Audit export
- review notifications
- Context Engine capacity
- model choices
- cloud concurrency
- worker concurrency
- advanced Quality Agent controls
Use the Billing page to confirm the current plan before assuming a feature is broken.
Payment Method and Abuse Prevention
Section titled “Payment Method and Abuse Prevention”Cloud Hosted free workspaces may need a verified card before managed cloud execution is available. This does not necessarily mean the workspace has moved to a paid subscription; it can be required for abuse prevention and usage beyond free allowances.
Self Hosted workspaces do not need the same cloud payment card gate to run their own worker and provider path.
Common Questions
Section titled “Common Questions”Does a failed run use a run credit? Check the event matrix above, then confirm the final state in Billing and job detail. The main distinction is whether MergeLoom produced or recovered review output.
Does Retry Publish use a run credit? For prepaid plans, Retry Publish can require and debit a run credit because it can create the PR/MR from stored branch artifacts.
Where do I see cost estimates? Use Analytics, Billing, Ticket Audit, Cloud Audit, and Context Engine audit where available.
Where do I change plan or buy packs? Use Billing in the customer controller. If the action is not available in your workspace, contact MergeLoom support.