Credit Discrepancies

Why final cost differs from the estimate.

It's common for the final credit cost to differ from the estimate. Here's why.

Why the Final Cost Is Lower

• Cache hits — responses reused from cache cost 0 credits. The estimate assumes no caching.
• Failed responses — credits for API calls that fail are refunded.

Why the Final Cost Matches the Estimate

If this is your first run or you've changed all your prompts since the last run, there are no cache hits. In this case, the final cost should match the estimate (minus any failures).

Race Conditions

If you see "Insufficient credits. Another run may have consumed them", it means two runs tried to deduct credits simultaneously. Wait for the first run to complete — failed responses from that run will be refunded, potentially freeing up credits.

Checking Usage

Go to Settings > Billing to see your usage history. Each entry shows the event type (Deducted or Refunded), the associated run, and the credit amount.