docs: document bucket breakdown in usage analytics#207
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
DiabolusGX
approved these changes
Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a reporting section to the time-of-day commitment buckets page covering the new
breakdown_bucketflag on the usage analytics endpoint.Changes
breakdown_bucket: truerequest flag onPOST /events/analytics.bucket_summariesresponse field (per-bucket usage and commitment math) andpoints[].bucketsoverlap hints.BucketSummaryfield with its meaning.Context
The release exposes per-bucket attribution in the usage analytics response so customers can see exact usage, base charge, utilized commitment, overage, and true-up per time-of-day bucket. Without this section, the only signal users had was the OpenAPI spec.