Credits and usage
Orchestor credits and usage are in Early Beta. Credit costs, allowances, and expiry rules may change. Before running observations or purchasing credits, check your current plan and the terms shown on screen.
Credits measure work performed in Orchestor, including AI answer observations. Tracking more prompts or AI engines increases the number of observations you run.
Your plan allowance determines the scope you can configure. Credits measure consumption when work runs. See Subscription plans for prompt, engine, and brand allowances.
Organization allowances and workspace usage
Organization usage shows client and pitch workspace quotas and the measurement AI platform allowance. These allowances belong to the organization and do not change when you switch workspaces or change the default workspace.
The measurement AI platform allowance is the plan's included limit per workspace. Client and pitch limits may differ; this is not a pool of AI slots consumed across all workspaces.
Current workspace usage shows prompt usage and configured measurement AIs for the selected workspace. Purchased AI add-ons apply to their target workspace. An unresolved contract is shown as unknown, never as free or unlimited.
Observation costs
The basic observation unit is 1 prompt × 1 AI engine × 1 day = 1 credit.
For example, observing “What is the best CRM for a small business?” once a day across two AI engines for 30 days gives an estimate of 60 observations.
| Observation scope | Calculation | Estimated credits |
|---|---|---|
| One prompt on one AI engine for one day | 1 × 1 × 1 | 1 |
| One prompt on two AI engines for 30 days | 1 × 2 × 30 | 60 |
| Ten prompts on two AI engines for 30 days | 10 × 2 × 30 | 600 |
These examples estimate standard observations. They do not mean that every API call or agent task costs one credit. Check the usage recorded for the work you run.
Credit types
Balances are tracked in three categories.
| Type | What it includes | Expiry |
|---|---|---|
| Included credits | Credits granted for a billing period under your subscription | End of that billing period |
| Purchased credits | Credits granted through an additional purchase | According to the purchase terms |
| Promotional credits | Credits granted for offers such as a free diagnostic | The expiry set when granted |
Credits closest to expiry are used first. Expired credits cannot be used. Purchased credits without an expiry are used after credits with an expiry date.
Unused included credits do not roll over beyond their billing period. A promotional balance is separate from the allowance included with each subscription period.
Check your balance
- Select the workspace you want to check.
- Open Settings → Plan and usage.
- Check the balance under Usage credits.
A dash means the balance was not retrieved. It does not mean the balance is zero. Reload the page and check again.
Credits are reserved before work begins, then settled when it finishes. While work is running, the available balance and settled usage may not add up to the total credits granted.
Review usage by period
The usage API returns request counts and credits used for each period. Use it to review automated workflows or compare periods.
| Item | What to check |
|---|---|
| Reporting period | Whether start and end times cover comparable periods |
| Request count | How much observation or API activity changed |
| Credits used | How many credits were consumed over the same period |
Use GET /v1/usage to retrieve usage. If has_more is true, use next_cursor to retrieve the next page. Request counts and credits used are separate measures and may differ.
When you reach a limit
Limit behavior follows the workspace's subscription and overage policy. When the workspace is set to pause at its limit, new work cannot start if it exceeds the available balance. When overage is permitted, excess usage is recorded separately.
Before expanding your observations, review the prompts, AI engines, and frequency you track. Change your plan if you need more tracking capacity. Adding credits and increasing a plan's prompt or brand allowance are separate actions.
Additional credit purchases
An additional purchase adds credits separately from your included balance. It does not increase plan allowances such as prompt or brand counts.
Purchases from Settings are currently in preparation. A disabled payment button does not submit a payment. Purchased credits that have already been granted are included in your available balance.
Before purchasing, review the credit amount, discount, tax, total, and payment method. Expiry follows the terms shown at purchase.
Pitch workspaces
Pitch workspaces let you review observations when preparing a customer proposal. Settings → Plan and usage shows two organization-wide quotas:
| Quota | What counts | When capacity becomes available |
|---|---|---|
| Pitch workspace creation allowance | Pitch workspaces created this month | At the next monthly reset. Archiving or converting a workspace to client use does not refund this allowance. |
| Pitch workspaces | Unexpired, unarchived pitch workspaces, including paused workspaces | Expiry, archiving, or conversion to client use removes the workspace from this count. |
For example, creating three pitch workspaces and converting one to client use leaves the monthly creation count at three. If the other two are unexpired and unarchived, the pitch workspace count is two.
Limits follow your contract and additional allowances. Bars show the proportion used. “Unlimited” means no limit; a dash means the value could not be retrieved.
For API and CLI instructions, see Review agency capacity.
Monthly spending limit
The monthly spending limit controls consumption of additional credits. It is separate from auto-recharge, which purchases credits when the balance falls below a threshold.
Organization admins can open Settings → Plan and usage → Usage credits → Monthly spending limit → Manage to save a JPY limit for the selected workspace. This limit applies to additional agent, research, and generation execution. Ordinary AI answer observation remains governed by plan allowances. Zero blocks new paid usage; unlimited removes the monthly cap. Included and promotional allowances are excluded.
Months follow Japan Standard Time. Admission counts settled spending and outstanding holds; holds survive month boundaries until completion. Existing work is not interrupted, and actual costs above an estimate are recorded even if they exceed the limit. New paid work then remains blocked. Purchase-time JPY values determine consumption, rounded up per operation; no estimated FX conversion is used. Unpriced balances or untracked historical paid usage remain unknown and block paid admission until reconciled. Saving a limit does not purchase funds or enable auto-recharge.
Auto top-up
Auto top-up is intended to purchase additional credits when your balance runs low. It is separate from a one-time manual purchase.
Organization admins can save a JPY balance threshold and target balance from Settings. Saving these amounts does not charge a payment method. Auto top-up activation and automatic payments are still in preparation. Changing the switch in Settings does not start automatic purchases. If your balance is low, review your current plan and observation scope.
Auto-recharge
Organization administrators can enable auto-recharge with a threshold and target balance in JPY. When the purchased balance reaches the threshold, the saved payment method is charged for the amount needed to reach the target. If the balance is already below the threshold, charging starts on the next check. The minimum top-up is ¥50.
Purchased usage credits have a face value of ¥1 each. Included plan credits are excluded from this check. Eligible discounts apply before tax; tax is added separately. The monthly usage limit controls consumption, not automatic purchases. Turning auto-recharge off stops new payments; completed payments still receive their credits. Payment failures turn auto-recharge off until an administrator checks the payment method or authentication and enables it again.