We would like to better understand how billing/API Counts apply to operations triggered from the brainCloud Portal.

Our question is not limited to one specific feature. We are trying to clarify the general rule for Portal actions that execute backend operations, such as:

• Refreshing or re-evaluating segments
• Refreshing promotions/pricing for users
• Running operations from API Explorer or S2S Explorer
• Triggering batch/user-processing jobs
• Other Portal buttons that may cause server-side processing

Could you please clarify:

1. Are backend operations triggered from the Portal counted toward billable API Counts or other usage metrics?

2. If yes, is the billing rule the same as calling the equivalent Client API, S2S API, or Cloud Code operation directly?

3. Are there Portal actions that are considered admin/configuration operations and are not billed as API Counts?

4. For operations that process many users or records, how is usage calculated?

   • Once per Portal action?
   • Once per underlying API operation?
   • Once per user/record processed?
   • Or based on bulk-operation rules?

5. Where can we verify Portal-triggered usage in the brainCloud reports?

   • Is there a specific service/operation naming pattern we should look for?

6. Are scheduled/internal maintenance operations, such as automatic segment refreshes, billed differently from manually triggered Portal operations?

We are asking because we want to avoid unexpectedly increasing API usage or costs when using Portal features in production, especially for actions that may process many users.

Thank you!