Skip to main content

​
Token Wallets

Every Condense Environment (ENV) is provisioned with token wallets that are used by AI Agents to process requests. These wallets track AI token consumption and ensure that usage is monitored, controlled, and billed accurately. Each environment maintains separate balances for input and output tokens, allowing Condense to accurately account for AI model usage across different providers.

​
Wallet Types

Each environment contains two independent wallets. The balances are managed independently because AI providers typically charge different rates for input and output tokens.

​
How Token Wallets Work

Whenever an AI Agent processes a request, Condense automatically manages the wallet lifecycle.
  1. The AI request is received.
  2. Token usage is estimated before processing.
  3. Available wallet balances are checked.
  4. If sufficient balance is available, the request proceeds.
  5. After completion, the actual number of input and output tokens consumed is deducted.
  6. Usage is recorded for reporting and billing.
This process happens automatically for every AI interaction.

​
Token Consumption

Token usage depends on several factors, including:
  • Prompt size
  • Conversation history
  • AI model used
  • Generated response length
Since every request is different, the actual number of tokens consumed may vary.

​
Balance Management

Wallet balances are updated automatically after every successful AI request. Organizations can replenish balances by purchasing additional tokens when required. Monthly token allocations may also be automatically credited based on the organization’s subscription or contract.

​
Insufficient Token Balance

Before executing an AI request, Condense checks whether sufficient tokens are available. If adequate balance exists:
  • The request is processed normally.
If the available balance is insufficient:
  • The request may be blocked based on platform configuration.
  • Users are prompted to contact an Environment Administrator or purchase additional tokens.
The platform records insufficient balance events for operational visibility.

​
Usage Tracking

Every wallet transaction is logged automatically. Each transaction records information such as:
  • User
  • Environment
  • Workspace
  • AI Agent
  • AI model
  • Timestamp
  • Input tokens consumed
  • Output tokens consumed
This information is available through the Agent Usage page for monitoring and reporting.

​
Wallet Recharge

Environment Administrators can purchase additional input and output tokens whenever required. Purchased tokens are credited immediately to the corresponding wallet and become available to all AI Agents running within the environment.

​
Access Control

Wallet balances are protected through role-based access control (RBAC). Depending on assigned permissions, users can:
  • View wallet balances
  • View transaction history
  • Purchase additional tokens
  • Manage billing settings
Recharge operations are restricted to authorized administrators.
  • Billing
  • Agent Usage
  • Recharge Tokens
  • Pricing & Billing