Agentforce Data Library uses Data 360 for data processing. Use of Agentforce Data Library impacts the consumption of credits in these usage types.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Platform or Einstein or Agentforce for Sales or Service add-on, or Agentforce Foundations |
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.
Some usage types aren't metered for certain licenses or editions, such as a Data 360 Profiles license. Check your licenses and review license documentation for more information.
Data 360 Usage
When you use Agentforce Data Library, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card.
- If your contract included Data Service Credits, those are consumed for all Data 360 usage.
- If you run out of Data Service Credits, your org is billed at your Data Service Credit overage rate for the remainder of your term unless more credits are added.
- If you have Flex Credits for Data 360, those credits are consumed instead.
Data Services and Flex Credits organize data services within different usage type groupings. For more information, see Data Services Billable Usage Types for Data 360 and 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 Consumption Card | 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. |
Data queries are used by the data library to retrieve information from the search index. |
| Data Services | Intelligent Processing | Usage is calculated based on the amount of unstructured data that is processed using AI-assisted features such as LLM-based parsing, LLM-based visual data preprocessing, image processing, Enriched Indexing, and Intelligent Context. | This usage type applies when Intelligent Context is enabled for your data library. Intelligent Context is on by default for all new data libraries and for all file-based data libraries created before July 6, 2026. For data libraries created after July 6, 2026, this usage type applies only if you enable Intelligent Context. Usage depends on the amount and complexity of data in your uploaded files. See Use Uploaded Files. |
| Data Services | Unstructured Data Processed |
Usage is calculated based on the amount of unstructured data that is processed without using AI assisted content processing and extraction. For example, if the search index processes 100 PDF documents that are 1 MB each, usage is calculated as 100 MB. If the search index processes five audio/video files that are on average 100MB each, usage is calculated as 500MB. In Data 360, unstructured data may be chunked and vectorized using an embedding model. Usage is computed only once across both these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB, not as 200MB. If you create a search index that uses a data model object (DMO) as a data source and select Text data type fields from the DMO, all strings from those fields are indexed and the sum total of all bytes processed is reported as Unstructured Data Processed. |
When you set up a Knowledge-based data library, it uses unstructured data processing to build your search index. Prior to Intelligent Context, all files were processed via the unstructured data processing pipeline. |
| 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 |
The Answer Questions with Knowledge action or a custom built action use the Agentforce Data Library to query the index and retrieve relevant information from the database. The extracted information corresponds to processed rows. |
| Flex Credits | Intelligent Processing | Usage is calculated based on the amount of unstructured data that is processed using AI-assisted features such as LLM-based parsing, LLM-based visual data preprocessing, image processing, Enriched Indexing, and Intelligent Context. | This usage type applies when Intelligent Context is enabled for your data library. Intelligent Context is on by default for all new data libraries and for all file-based data libraries created before July 6, 2026. For data libraries created after July 6, 2026, this usage type applies only if you enable Intelligent Context. Usage depends on the amount and complexity of data in your uploaded files. See Use Uploaded Files. |
| Flex Credits | Unstructured Processing |
Usage is calculated based on the amount of unstructured data that is processed without using AI assisted content processing and extraction. For example, if the search index processes 100 PDF documents that are 1 MB each, usage is calculated as 100 MB. If the search index processes five audio/video files that are on average 100MB each, usage is calculated as 500MB. In Data Cloud, unstructured data may be chunked and vectorized using an embedding model. Usage is computed only once across both these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB, not as 200MB.If you create a search index that uses a data model object (DMO) as a data source and select Text data type fields from the DMO, all strings from those fields are indexed and the sum total of all bytes processed is reported as Unstructured Data Processed. |
When you set up a Knowledge-based data library, it uses unstructured data processing to build your search index. Prior to Intelligent Context, all files were processed via the unstructured data processing pipeline. |
For more information on how Data 360 usage is billed, refer to your contract or contact your account executive.
Data 360 Storage Usage
Storage costs are determined by your contract. Use Digital Wallet to check your current usage.
| Digital Wallet Consumption Card | Usage Type | Description | Notes |
|---|---|---|---|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. |
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.  Note Advanced Prompts were launched with a designated multiplier listed in the Agentforce
Flex Credits Rate Card. Salesforce will start metering the use of Advanced
Prompts on July 21, 2026.
|