Local request reconciliation / no account access

Trace every credit to a request.

Paste a Grok Build usage export, enter the rules shown on your account, and separate explained burn from the rows worth investigating.

No live price claim. Every rate is editable, visible, and saved with the evidence.

Computed evidence

Waiting for valid rows

0 rows
Expected0.00credits
Observed0.00credits
Unexplained0.00credits
Anomalies0requests
Expected burn0.00× observed / expected
RequestTokensCacheExpectedObservedRatioFinding
SELECT A ROW

Request arithmetic appears here

Run the sample to inspect standard input, cached input, output, overhead, and residual evidence.

An anomaly identifies a mismatch. It does not, by itself, prove a billing error.

Read the evidence

Three questions before you blame the model.

The verified sample has five rows that reconcile exactly. That makes req-004's 31.20-credit residual specific rather than a global rate-model failure.

Transfer check

The sample has one 3.00× row while five rows reconcile. What should you investigate next?

Choose the next investigation supported by the row-level evidence.
Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.