Token usage for my team

Q&A
, ,
1

How do I access token usage data for my team?

2

Hey! Quick doesn’t measure usage in “tokens” the way you might with raw LLM APIs. Instead, we use agent hours — basically wall-clock time that an agent spends actively working on a task. Usage is metered per second and resets monthly on your billing cycle.

What counts toward agent hours:

  • Quick Research (in-depth analysis and reports)

  • Quick Flows (automated workflows)

  • Quick Automate (deployed automations)

  • Desktop app activity

  • Artifact generation

  • Custom AI-powered apps

Option 1: The Admin Analytics Dashboard (no code)

If you’re an admin, this is the easiest path:

  1. Open the Quick console → left nav → Analytics

  2. Navigate to the Automations, Flows, and Research Agent Hours tabs

  3. You’ll see total hours consumed, overage hours, and user consumption breakdown

You need the quicksight:QuickSuiteUsageMetrics IAM permission. If you don’t see Analytics in your left nav, check with your instance admin.

Option 2: Programmatic — CloudWatch Logs

Quick can deliver agent hours usage logs to CloudWatch, S3, or Firehose. Great for custom dashboards, alerting, or cross-account rollups.

Set up IAM permissions:



{

“Version”: “2012-10-17”,

“Statement”: [{

“Sid”: “QuicksightLogDeliveryPermissions”,

“Effect”: “Allow”,

“Action”: “quicksight:AllowVendedLogDeliveryForResource”,

“Resource”: “arn:aws:quicksight:::account/”

}]

}

Create the delivery source for agent hours:



aws logs put-delivery-source \

–name “quick-agent-hours-source” \

–resource-arn “arn:aws:quicksight:::account/” \

–log-type “AGENT_HOURS_LOGS”

Create a delivery destination (e.g., CloudWatch log group):



aws logs put-delivery-destination \

–name “quick-agent-hours-dest” \

–delivery-destination-configuration \

'{"destinationResourceArn":"arn:aws:logs:<region>:<account-id>:log-group:/aws/quick/agent-hours"}'

Link source to destination:



aws logs create-delivery \

–delivery-source-name “quick-agent-hours-source” \

–delivery-destination-arn “arn:aws:logs:::delivery-destination:quick-agent-hours-dest”

Query with CloudWatch Logs Insights:



fields @timestamp, user_arn, subscription_type, reporting_service, usage_group, usage_hours

| filter reporting_service IN [“RESEARCH”, “FLOWS”, “AUTOMATIONS”]

| stats sum(usage_hours) as total_hours by user_arn, usage_group

| sort total_hours desc

Each log event includes subscription_type, reporting_service (Research/Flows/Automations), usage_group (Included vs. Extra), and usage_hours.

TL;DR: For a quick team-level view, use the built-in Analytics dashboard. For custom alerting or cross-account aggregation, set up CloudWatch Logs with AGENT_HOURS_LOGS and query with Logs Insights or pipe to Athena.

Hope that helps! :raising_hands:

3

Thanks Ramon — super helpful breakdown! :folded_hands:

Quick follow-up: I don’t currently see “Analytics” in my left nav on the amazonbi instance. I assume I need the quicksight:QuickSuiteUsageMetrics IAM permission added.

Is there a standard process for requesting this, or can you point me to the right admin/team for the amazonbi account?

Appreciate the help!

4

Hi @bitikap,

As this is a public user forum, we are not able to assist in this matter. I would recommend reaching out to any internal channels or a respective IT admin that you have access to, as they should be able to help you in this process. If that is not the case, I would reach out to AWS Support by creating a support ticket, and they can help you from there.

5

Hi @bitikap,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime. Moreover, if you submitted a support ticket and it uncovered any findings, please feel free to share them!

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.

6

Hi @bitikap,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.

Thank you.