Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Tableau Next
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Billing Considerations for Model Context Protocol (MCP) Server on Tableau Next

          Billing Considerations for Model Context Protocol (MCP) Server on Tableau Next

          MCP Server on Tableau Next consumes Data 360, Flex Credits, and Einstein Requests credits. Understanding which consumption cards are used and how usage is metered helps you manage credit consumption effectively.

          Required Editions

          Available in: Enterprise, Performance, and Unlimited Editions with Tableau Next

          MCP Server on Tableau Next uses Data 360 for data collection and processing, and Flex Credits and Einstein Requests for generative AI. Use of Tableau Next impacts the consumption of credits in these usage types.

          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 or Agentforce 1 Edition. Check your licenses and review license documentation for more information.

          Data 360 Usage

          When you use Data 360 for data collection 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 credits, those credits are consumed first. If you run out of Data Services credits or never had any, your org consumes Flex Credits for Data 360 services. 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.
          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.

          Agentforce and Generative AI Usage

          When your org uses Agentforce or generative AI, it consumes Agentforce Flex Credits or Einstein Requests credits. If you have any active Einstein Requests credits, those credits are consumed first. If you run out of Einstein Requests credits or never had any, your org consumes Agentforce Flex Credits. For more information, see Flex Credits Billable Usage Types and Einstein Requests 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 Consumption Card Usage Type Description Notes
          Einstein Requests
          • 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.

          For Tableau Next processing, LLM gateway calls are counted as {standard/basic/advanced} prompts.

          If consumption is without Tableau Next Unmetered permission, the transaction is metered. This usage type isn't billed when it's associated with a generative AI action that qualifies as unmetered human context usage. For more information, see Metering for Agentforce and Generative AI Usage.

          If consumption is with Tableau Next Unmetered permission, the transaction is unmetered.

          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.

          For Tableau Next processing, LLM gateway calls are counted as {standard/basic/advanced} prompts.

          If consumption is without Tableau Next Unmetered permission, the transaction is metered. When metered, this usage type is billed for agent actions invoked by Agentforce for Analytics: Concierge or by Agentforce for Analytics: Inspector.

          This usage type isn't billed when it's associated with a generative AI action that qualifies as unmetered human context usage. For more information, see Metering for Agentforce and Generative AI Usage.

          If consumption is with Tableau Next Unmetered permission, the transaction is unmetered.

          For more information on how usage is billed, refer to your contract or contact your account executive.

           
          Loading
          Salesforce Help | Article