feat(usage): wait for finalized request receipts - #6
Draft
AmazingAng wants to merge 1 commit into
Draft
Conversation
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
xapi-to usage wait <request-id>for polling until a request-cost receipt is finalized.--intervaland--timeoutdurations.404and transient transport failures while failing permanent authentication and authorization errors immediately.Why
Streaming requests can finish delivery before their actual cost receipt is persisted. Agents need a bounded, scriptable way to wait for the final cost before updating burn-rate and survival decisions.
Review scope
This is a stacked PR based on
agent/request-cost-receipts.Verification
git diff --checkpassed