Tokens are the primary usage resource for AI-powered operations inside AIUNIFY PROS SUITE.
Your Plan provides a Token allocation, and different tools or actions can consume different amounts as you use the Suite.
The basic usage model is:
Current Token Balance
↓
Choose Tool
↓
Review Token Cost
↓
Generate / Create / Edit / Run
↓
Tokens Consumed According to the Applicable Operation
↓
Account Balance Refreshes
↓
Remaining Tokens Available for Additional Work
This chapter explains:
Throughout PROS SUITE, the user-facing term Tokens refers to the account usage balance shown by the platform.
For example:
Monthly Tokens
[number] left
and:
Your balance: [number] tokens
These are PROS SUITE account usage Tokens.
They should not be confused with technical language-model input/output token measurements that AI providers may use internally.
For ordinary subscribers:
PROS SUITE Tokens = the usage balance you monitor inside your account.
Token information can appear in several places.
Monthly Tokens
[number] left
Token Balance
Available credits
Your balance: [number] tokens
The standard ToolPage places the current balance immediately beside the operation's displayed Token cost.
Many standard AI tools display:
[number] tokens per use
near the top of the workspace.
For example, you may see:
15 tokens per use
alongside:
Your balance: 2,500 tokens
This allows you to understand the expected cost before starting the generation.
Before selecting Generate:
This simple habit is one of the best ways to manage PROS SUITE usage efficiently.
PROS SUITE does not assign one universal Token cost to every AI tool.
The current feature definitions include different base costs for different capabilities.
For example, the source-defined fallback costs include examples such as:
These values illustrate the range of Tool costs in the Suite.
Those feature-level values can be superseded by the current live Tool cost configuration, so the cost actually displayed in your current workspace should be your operational reference.
The current feature definitions also demonstrate that more resource-intensive creative capabilities can carry higher base costs.
Examples include:
This reinforces an important operating principle:
Do not assume a text-generation cost applies to image, video, avatar, agent, or project-building workflows.
The current feature definitions also assign different cost levels to advanced AI Agents.
Examples include:
These are source-defined fallback costs and can be overridden by current system configuration.
Always review the current user-facing cost where one is shown.
For tools using the shared standard ToolPage, PROS SUITE determines a base displayed cost in this order:
Current configured Tool cost
↓
If none:
Tool's defined Token cost
↓
If none:
ToolPage fallback cost
The standard ToolPage's own fallback is currently 10 Tokens.
For subscribers, the important point is not the internal hierarchy itself but the result:
The cost displayed today can differ from an older screenshot, document, or default tool definition because PROS SUITE can use the current configured cost.
Because the standard ToolPage reads the current cost configuration when available, you should not memorize historical Token prices.
Instead:
Open Tool → Read Current “tokens per use” → Generate
This is safer than relying on a previously recorded Token amount.
For the shared standard ToolPage, the selected AI provider can also change the displayed cost.
The current source specifically applies a different displayed cost when the selected Model belongs to:
OpenAI.
For standard ToolPage generators, when the selected model uses the OpenAI provider, PROS SUITE currently calculates the displayed amount as:
Base Cost × 1.5
and rounds upward when necessary.
This rule is source-verified for the shared standard generator interface.
It should not be assumed to apply identically to every specialized workspace in the Suite.
Suppose you open a standard generator and then select another AI Model.
If the provider changes, the Tool's displayed Token cost may also change.
Therefore, the recommended sequence is:
Choose Tool
↓
Choose AI Model
↓
Recheck tokens per use
↓
Enter Prompt
↓
Generate
Do not assume the amount you saw before changing the Model is still the current displayed cost.
The 1.5× displayed-cost behavior is verified specifically inside the shared ToolPage component.
PROS SUITE also contains:
These can implement their own usage logic.
Therefore:
Do not apply the standard ToolPage calculation manually to every PROS SUITE feature.
Follow the specific workspace's current behavior.
There are two important Token patterns.
Typically presents:
X tokens per use
and:
Your balance: X tokens
before generation.
Can contain several different actions with different Token costs.
For example:
Create entire project
may cost more than:
Edit one existing portion
This distinction is particularly important in Website Builder and Pitch Deck.
The Dashboard can display a Tool Card Token cost using the configured cost or a feature-level fallback.
However, a complex workspace may contain multiple operations internally.
For example:
Open Website Builder
is not the same operation as:
Generate an entirely new website
which is not necessarily the same as:
Make one targeted website edit
Therefore:
Do not interpret a Dashboard Tool Card cost as a guarantee that every operation inside a complex workspace costs that exact amount.
The current Website Builder source establishes different deductions for:
This makes Website Builder a good example of why specialized workspaces need separate Token treatment.
The current Website Builder workflow requests a deduction of:
500 Tokens
before beginning a new full website-generation process.
If that deduction cannot be completed, Website Builder stops the generation before proceeding.
After a website exists, the AI editing workflow currently requests:
10 Tokens
for an edit operation.
This creates an important distinction:
Generate New Website
→ Higher-cost project creation
versus:
Modify Existing Website
→ Lower-cost incremental editing operation
under the current source-defined workflow.
Once a website has been generated, it can be more efficient to make targeted modifications rather than regenerate the entire project from scratch.
For example:
Instead of:
Create the whole website again but make the headline blue.
use the existing project and request the specific change.
Website Builder's current workflow distinguishes the full creation operation from subsequent edits.
Pitch Deck follows a similar concept.
The current source differentiates between:
The current live AI slide-generation workflow requests:
500 Tokens
before generating a new eight-slide presentation.
If the Token deduction cannot be completed, the generation does not proceed.
The current Pitch Deck editing workflow requests:
10 Tokens
for a subsequent AI editing request.
This means the initial creation and later refinement are not treated as identical operations.
The source-defined feature list contains fallback values such as:
But the actual current specialized project workflows independently request:
This is precisely why the manual will distinguish:
Tool discovery cost indicators
from:
specific action costs inside complex workspaces.
For specialized tools, follow the instructions in that tool's dedicated chapter.
For a simple standard generator, the Dashboard and ToolPage costs may closely correspond.
For a project-building application, do not assume:
Dashboard says 25 → every action is 25
or:
Dashboard says 100 → full project generation is 100
The specialized workflow can have its own operation-specific usage.
Website Builder and Pitch Deck illustrate a broader best practice:
Full Generation
often performs significantly more AI work.
Targeted Edit
can perform a smaller focused operation.
When a tool supports incremental editing, use it rather than rebuilding an entire project merely to change one small element.
In specialized workflows such as Website Builder and Pitch Deck, the current source checks/deducts Tokens before proceeding with the full generation.
If Token availability is insufficient, the workflow stops.
This prevents the full AI creation sequence from proceeding without the required usage balance.
For Website Builder and Pitch Deck, a failed Token deduction causes the generation/edit process to stop rather than continue into AI creation.
If this happens:
The shared AI streaming workflow refreshes the user's account information after generation completes.
This allows the updated Token Balance to appear in the interface following supported AI usage.
The authenticated application monitors successful non-authentication API actions.
After many successful operations, PROS SUITE silently refreshes the user's account information so the current Token Balance can update.
For the subscriber, this means:
The Token display can update automatically after a successful AI operation without requiring you to sign out and back in.
Certain specialized workflows explicitly request an account refresh when they finish or deduct Tokens.
Examples include:
The Image Generator, for example, refreshes the user account after successful image creation so the Token Balance can be updated.
Because account state can refresh after a request completes, the number displayed in one part of the interface may not always visibly change at the exact instant you click Generate.
If you want to verify the new balance:
Do not immediately repeat an operation simply because the displayed balance has not yet visibly changed.
Several PROS SUITE workflows explicitly recognize the condition:
Insufficient token balance.
This means the current available Token Balance does not meet the requirement for that operation.
Conceptually:
Current Balance < Required Cost
↓
Operation Cannot Proceed Normally
It does not necessarily mean:
It is specifically a usage-balance condition.
Remember the distinction from Chapter 8.
Can my account open this Tool?
Can my account currently afford this Token-consuming operation?
Possible combinations include:
| Tool AccessToken BalanceResult | ||
| Available | Sufficient | Work can proceed |
| Available | Insufficient | Token-related failure |
| Restricted | Sufficient | Tool still cannot be used |
| Coming Soon | Sufficient | Tool still unavailable |
Having Tokens does not automatically unlock a Tool outside your Plan.
Follow this sequence:
Step 1 — Stop repeated attempts
Do not continue clicking Generate.
Step 2 — Check Monthly Tokens
Review the Sidebar.
Step 3 — Check operation cost
Look at the Tool or relevant workspace.
Step 4 — Determine whether a lower-cost action is appropriate
For example, use a targeted edit instead of full regeneration where supported.
Step 5 — Review Plan options if necessary
Open Upgrade Plan.
Step 6 — Retry after sufficient Tokens are available
Certain integrated services can use provider terminology such as credits, while PROS SUITE uses Tokens as the user account balance.
For example, a specialized external generation service can return an insufficient-credit error during its own process. Music generation has source handling for such a provider-side condition.
The practical point for subscribers is:
An error mentioning an external provider's credits is not necessarily identical to the Monthly Tokens balance displayed by PROS SUITE.
Follow the exact error shown in the specialized tool.
A generation can fail for other reasons, including:
Read the actual error before assuming the Token Balance caused it.
If a standard ToolPage generation fails, it can display:
Error
and either the returned message or:
“Failed to generate content. Please try again.”
If the error specifically refers to Tokens or balance, investigate Tokens.
Otherwise, troubleshoot the reported issue.
A higher Token cost does not necessarily mean:
“This Tool is better than another Tool.”
Cost can reflect:
Choose tools according to the required outcome rather than assuming highest cost equals highest quality.
Token efficiency often improves when you start with the correct specialized Tool.
For example:
Need a Sales Pitch
→ Use Sales Pitch.
Need an Article
→ Use Article Writer.
Need a Business Plan
→ Use Business Plan.
Need a Website
→ Use Website Builder.
A general-purpose AI conversation may require more rounds of prompting to reach the same structured result.
Before spending Tokens, include:
What should be created?
What should the AI know?
Who is the result for?
How should it sound?
What must be included?
How should the result be organized?
This reduces the need for avoidable retries.
Write a marketing plan.
This may require several follow-up generations because the AI lacks important context.
A better request would include information such as:
Create a 90-day B2B marketing plan for a software company targeting real estate teams with 10–100 sales professionals. Organize the plan by lead generation, conversion, customer onboarding, social media, email marketing, and weekly KPIs. Use an executive business tone.
A complete first request gives the AI more information to work with and can reduce unnecessary regeneration.
After a result appears, first ask:
Can I use or edit this result?
before immediately selecting Generate again.
You may only need:
rather than a completely new generation.
When a generated result is nearly correct, manually fixing:
can be more efficient than requesting an entirely new AI generation.
Use AI when it provides meaningful value, not for changes that are faster to perform manually.
Where a specialized workspace supports focused edits, use them.
Website Builder and Pitch Deck both currently distinguish full-generation operations from lower-cost editing operations.
This makes targeted refinement particularly useful after the initial project exists.
Suppose your generated website is correct except for:
Do not automatically rebuild the entire website.
Use its editing capability when appropriate.
The same principle applies to Pitch Deck refinements.
For expensive or multi-step work:
This is especially useful for:
For example, before generating a brochure, decide:
Entering those decisions upfront can produce a more useful first result.
Standard ToolPage generators can provide:
Try these examples:
Use an example to understand what the Tool expects.
Then customize it before selecting Generate.
This is often more Token-efficient than submitting a vague request and discovering afterward that the Tool needed additional information.
Because the current standard ToolPage can display a different cost for OpenAI-provider models, Model choice can be part of Token management.
Before changing the Model:
If your current Model is successfully handling the task, switching providers merely to experiment may alter:
Use Model selection intentionally.
Chapter 10 will explain AI Model selection in detail.
If an operation consumes Tokens per use, repeatedly pressing Generate creates repeated usage.
A practical discipline is:
Generate Once
↓
Review Carefully
↓
Identify Specific Problem
↓
Revise Prompt or Use Edit
↓
Generate Again Only When Necessary
This is much more efficient than repeatedly generating without changing the instructions.
After selecting Generate, allow the current operation to begin.
Standard ToolPage disables the Generate action while streaming is active.
Specialized tools can use their own loading states.
Do not repeatedly click controls because generation appears to take a few moments.
Once content has been generated, merely:
does not cause the standard ToolPage to initiate another generation request.
The AI request occurs through the generation workflow, while Copy and Download are separate local actions.
Selecting Copy simply copies the existing generated result to the clipboard.
Therefore, once you have a useful result, Copy it rather than asking the AI to recreate the same output just so you can move it elsewhere.
Selecting Download creates a text file from the existing output.
Use Download to preserve good results.
There is no need to regenerate merely to create another copy of the same content.
The standard ToolPage Reset action clears:
and returns focus to the Prompt area.
Reset itself is not the same as an AI generation.
Use it when you are ready to start unrelated work.
Before Reset or beginning a completely different task:
This avoids spending Tokens later to recreate a result you already had.
The source-verified ordinary-user interface provides:
However, the current user-facing source does not establish a universal subscriber page that lists every Token transaction line-by-line, such as:
10:04 AM — Content Writer — 20 Tokens
10:15 AM — Research Agent — 100 Tokens
10:21 AM — Image Generator — 50 Tokens
Therefore, this manual does not instruct users to navigate to a nonexistent global Token Transaction History screen.
As established in Chapter 5, the current Dashboard Usage Overview and Category Usage charts use demonstration/static data.
Do not use those charts to reconcile Token consumption.
For current Token awareness, rely on:
The Sidebar progress bar gives a visual relationship between current Tokens and Token Limit.
For specific usage decisions, use:
[number] left
because that is the numerical balance.
For example:
Monthly Tokens — 340 left
is more useful when considering a 500-Token full project generation than simply looking at the progress bar.
Suppose a standard Tool displays:
20 tokens per use
and:
Your balance: 1,000 tokens
Recommended workflow:
Suppose you want a new website.
Before beginning:
The current workflow distinguishes the 500-Token initial generation from 10-Token AI edits.
Before creating a Pitch Deck:
The current workflow distinguishes a 500-Token initial generation from 10-Token subsequent AI editing.
If a standard ToolPage currently displays a base cost and you switch to an OpenAI-provider model, PROS SUITE recalculates the displayed per-use amount using the current OpenAI multiplier.
Before generating:
Switch Model → Recheck Cost → Generate
Do not rely on the cost you saw under the previous provider.
Possible reasons include:
Check the current workspace rather than relying on an older value.
This can occur with complex applications.
The Dashboard resolves a Tool Card cost from configured or feature-level information.
Website Builder and Pitch Deck independently implement operation-specific costs for full project generation and editing.
Use the specialized Tool's dedicated operating instructions for its exact workflows.
If an operation completed but your displayed balance appears unchanged:
PROS SUITE contains automatic account-refresh behavior after successful API operations.
Check:
Do not assume the Tool's Dashboard-card cost represents every action inside a specialized workspace.
Token Balance may not be the cause.
Check the actual error for:
Resolve the actual message shown.
This is an access issue, not a Token issue.
Check:
Having 10,000 Tokens does not override a Plan restriction.
After verified successful checkout, PROS SUITE refreshes the user account and can display:
Upgrade Successful!
“Tokens have been added to your account.”
If the old balance remains visible:
Not every specialized workspace uses the shared:
X tokens per use
display.
If no cost appears:
Do not assume an absent standard cost badge means the operation is free.
Token settings and Tool capabilities can evolve.
Therefore:
Current displayed cost > old screenshot
Current workspace behavior > remembered cost
Current Plan/Pricing > old documentation
This manual explains the operating model, but live displayed values should be used for current usage decisions.
Rather than thinking only:
How many generations can I run?
think:
What business outcome do I need to complete with my available Tokens?
For example:
Website Project
Marketing Campaign
Investor Presentation
This helps allocate Tokens according to completed outcomes.
For complex builders:
Plan → Generate Strong First Version → Refine
is generally preferable to:
Generate → Discard → Generate → Discard → Generate Again
when the existing project can be edited.
When a tool provides:
use those functions.
Preserving completed work prevents unnecessary repeat generation.
Connected agents can operate differently from one-time text generators.
Because their activity can involve repeated message-handling operations, review:
before relying on an Agent for ongoing activity.
The dedicated Social Agent chapters will explain their specific workflows.
Media creation can have higher source-defined base costs than many text-generation tools.
Current feature definitions demonstrate higher levels for capabilities such as Image, Video, and Avatar generation.
Before producing several versions:
A practical PROS SUITE Token workflow is:
CHECK BALANCE
↓
CHOOSE CORRECT TOOL
↓
SELECT MODEL
↓
CHECK CURRENT COST
↓
PREPARE COMPLETE INPUT
↓
GENERATE ONCE
↓
REVIEW RESULT
↓
Choose:
Use Result
or:
Targeted Edit
or:
Regenerate Only if Necessary
↓
COPY / DOWNLOAD / SAVE
↓
CHECK REMAINING BALANCE
Before a generation:
After a generation:
You do not need to know how PROS SUITE administrators configure Token pricing.
As a subscriber, you need to know:
How many Tokens do I have?
What does this Tool/action currently cost?
Does changing the Model alter the displayed cost?
Is this a full project generation or a smaller edit?
Do I have enough Tokens?
Can I refine existing work rather than regenerate it?
That is the user-level Token management model.
AIUNIFY PROS SUITE uses Tokens as its subscriber-facing AI usage resource.
Standard generators display:
[number] tokens per use
alongside:
Your balance: [number] tokens.
For the shared standard ToolPage, the displayed base cost is taken from the current Tool configuration when available, then the Tool's defined cost, then the ToolPage fallback. The current standard ToolPage also increases the displayed cost by 1.5×, rounded upward, when an OpenAI-provider model is selected.
This model is not universal to every specialized workspace.
Complex applications can contain their own operation-specific usage. Current examples include:
Website Builder
Pitch Deck
This means users should not assume a Dashboard Tool Card cost represents every operation available inside a complex project workspace.
PROS SUITE refreshes authenticated user information after many successful AI/API operations so Token Balance changes can be reflected in the interface.
The most effective Token-management principle is:
Check Balance → Choose the Right Tool → Choose the Right Model → Check Cost → Give Complete Instructions → Generate → Review → Edit Instead of Rebuilding Where Possible → Save the Result → Monitor Remaining Balance
Tokens are most valuable when managed around completed business outcomes, rather than simply around the number of AI generations performed.