Page Comparison

...

• 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

• Standard “Comply” Mode:

  1 token is consumed for each URL link crawled

  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

  crawled URL links

  converted data after the end of the

  crawling

  process.

  If

  For example: if you set the “Links limit“ value as 50, but only 20 links were scraped successfully, system will consume tokens only

  20 tokens will be consumed

  for 20 successful links.

• The same logic will be applied if you started the process

  of crawling

  and then canceled it (deleted the knowledge base while it’s in progress status). Tokens will be consumed for the amount of already

  crawled links

  processed data before canceling.

• Advanced “Bypass“ Mode:

  • 50 tokens are consumed for each URL link crawled.

  • This mode bypasses certain web restrictions, requiring more resources and thus more tokens.

...

Files Token Usage

• 1 token is used for every 1 MB of file data uploaded and successfully converted into the knowledge base.

• If a file is less than 1 MB, the token cost is proportional to the file size. For example, a 0.5 MB file will cost 0.5 tokens.

• The storage is limited by your subscription plan.

...

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.

...

• 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.

  Optimize File Sizes:

  • When using the “Files” feature, consider compressing files to lower sizes to save tokens and storage.