Repository navigation
Track estimated Jev spend in resumable benchmarks - #47
Merged
Merged
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
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.
Local benchmark runs recorded provider tokens without a dollar total. Add resumable non-email benchmark helpers that show estimated USD spend in live status and reports using an explicitly configured, sourced Jev list rate ($0.042 per million input tokens; output free, checked October 17, 2026).
New attempts snapshot pricing and retain per-attempt costs. Earlier unpriced receipts receive identified retrospective estimates without rewriting the original receipts. Unknown usage and pending attempts remain visible as partial coverage. The helpers preserve the existing run and completed cases, record source-label limitations, and keep datasets, receipts and credentials outside Git.
Add offline pricing/resume checks to CI and document the setup, source provenance, request/token limits and invoice limitations in docs/COSTS.md.
Validation:
No dataset downloads or paid API calls run in CI. Hosted checks must pass before merge.