You are here:
Billing Considerations for Testing Retrievers
When you test retrievers by querying search indexes, your data is processed in Data 360. The primary usage type for retriever testing is Data Queries. Use of retriever playground impacts the consumption of credits used for billing in these usage types.
Where your feature consumes credits for Data 360 depends on which consumption cards are active in your org. Use Digital Wallet to check which consumption cards are active in your org, find out how many credits are available on each card, and determine how many credits have been consumed in each usage type.
If you have certain licenses or editions, such as a Data 360 Profiles license or Agentforce 1 Edition, some types of usage aren’t metered. Check your licenses and review license documentation for more information.
For more information on how usage is calculated for Data Queries see, Billing Consideration for Unstructured Data and Search Index. This feature has access to Digital Wallet, a free account management tool that offers near real-time consumption data for enabled products across your active contracts. Access Digital Wallet and start tracking your org's usage. To learn more, see About Digital Wallet.
Data 360 Usage
When you use Data 360 for data collections and processing, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card. If you have any active Data Services consumption cards, those credits are consumed first. If you run out of Data Services credits or never had any, your org consumes Data 360 Flex Credits for Data 360 services.
To learn more about Data Services usage types, see Data 360 Billable Usage Types or Flex Credits Usage Types for Data 360. To check multipliers for each usage type, see the Multipliers for Data Services Rate Card or the Agentforce & Data 360 Flex Credits Rate Card. The cost of each credit is determined by your contract.
| Digital Wallet Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | Data Queries | Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. |
For vector search queries against unstructured data, the number of vectors in the search index are counted. For hybrid search queries against unstructured data, the number of vectors and keyword records in the search index are counted. In a typical search index, the number of keyword records is the same as the number of vectors. |
| Flex Credits | Data 360 Queries | Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. When an object is queried in the context of a data space, the number of rows processed is based on the total number of processed rows in the source object, not the number of rows pertaining to the particular data space |
This usage type is consumed only if you don’t have any Data Services credits. For vector search queries against unstructured data, the number of vectors in the search index are counted. For hybrid search queries against unstructured data, the number of vectors and keyword records in the search index are counted. In a typical search index, the number of keyword records is the same as the number of vectors |
Agentforce and Generative AI Usage
When your org uses an Agentforce or generative AI, it consumes Agentforce Flex Credits or Einstein Requests credits.
To learn more about Flex Credits usage types, see Generative AI Billable Usage Types. To check multipliers for each usage type, see the Agentforce & Data 360 Flex Credits Rate Card. The cost of each credit is determined by your contract.
| Digital Wallet Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Flex Credits | Standard Prompts Basic Prompts Advanced Prompts |
Usage is calculated based on two factors: the number of direct requests to the LLM via the LLM gateway, and whether the gateway uses a Salesforce managed large language model. The specific category depends on the model that is used. See Large Language Model Support to find out which usage types apply. All Standard, Basic, and Advanced prompts process up to 2,000 tokens per prompt. Token usage is rounded up in 2,000-token increments. All Standard, Basic, and Advanced prompts that exceed this limit will be metered as multiple prompts, with each additional 2,000-token chunk counting as a new prompt. For example, a prompt with a total of 6,500 input and output tokens will be metered as 4 prompts. Tokens are units of data processed by the AI models. |
To generate a context recall score in the advanced testing mode, retriever playground makes LLM gateway calls that are counted as Standard Prompts. Testing retrievers in the basic mode does not consume flex credits. |
