This guide will help you understand how the token usage system works within the application. Understanding this system will help you make the most of the application’s features while efficiently managing your tokens.
Overview of Token System
Tokens in Await Cortex are a form of digital currency used to access various features.
Each action within the application - whether sending a message via the chatbot, crawling web pages or uploading files - consumes a certain number of tokens.
Query Tokens:
Used to generate AI responses.
Replenish monthly according to your subscription plan and can be purchased additionally.
Computation Tokens:
Used for creating knowledge bases.
Replenish monthly according to your subscription plan and can be purchased additionally.
Storage Tokens:
Utilized to store the created knowledge bases.
Storage capacity is limited and determined by your subscription plan.
Query Token Usage
Each message sent to the AI chatbot consumes 1 token.
This also relevant for any query or command input into the chatbot interface, including the “Regenerate“, “Continue“ or “Suggestions“ features.
The same system applies to the chatbot agents, located on the external websites.
...
Computation Token Usage
Computation tokens are primarily used to extract and convert raw data into structured knowledge bases AI can read.
The consumption of computation tokens is directly related to the size of the data being processed as it requires more computational resources. Token consumption doesn’t depend on the data format.
The final amount of spent tokens will depend on amount of successfully converted data after the end of the process. For example: if you set the “Links limit“ value as 50, but only 20 links were scraped successfully, system will consume tokens only for 20 successful links.
The same logic will be applied if you started the process and then canceled it (deleted the knowledge base while it’s in progress status). Tokens will be consumed for the amount of already processed data before canceling.
...
Storage Token Usage
Used for storing the created knowledge bases.
The amount of consumed storage tokens depends on the size of the data inside the knowledge base stored.
The initial size of the data which was converted into the knowledge base doesn’t affect the final size of the storage that will be consumed. For example: 1 MB PDF file might consume the same (or less) storage as 10 KB TXT file.
Unlike the Computational Tokens, Storage capacity is limited and determined by your subscription plan. If you ran out of the storage, you will not be able to create new knowledge bases and use them. You can upgrade your subscription plan or delete some of the previously created knowledge bases.
...
Managing Your Tokens
Your current token balance is displayed in the “Settings“ page.
If you need more tokens, you can purchase them through the “Get extra credits“ option in your account settings.
Best Practices for Token Usage
Plan Your Actions:
Estimate and plan your usage of the features to optimize token consumption.
Monitor Usage Regularly:
Regularly check your token usage to avoid unexpected depletion of tokens.