The table below estimates provider-side free-tier equivalents using known upstream free limits such as weekly or monthly request allowances.
When the filtered usage exceeds a provider's base free allowance, the overflow is counted as additional free-tier-equivalent capacity and translated into token and premium-value equivalents.
</p>
<table>
<tr>
<th>Provider</th>
<th>Used Tokens</th>
<th>Requests</th>
<th>Measured Usage</th>
<th>Free Limit</th>
<th>Extra Free Tiers</th>
<th>Equivalent Saved Tokens</th>
<th>Premium Reference</th>
<th>Equivalent Saved Cost</th>
</tr>
{% for item in optimization_savings.provider_equivalents %}
<pstyle="color: var(--color-muted);">No optimization savings recorded yet. Enable deduplication, condensation, batching, or caching to see savings.</p>
<pstyle="color: var(--color-muted);">No optimization savings recorded yet. Increase usage on providers with known upstream free tiers, or enable deduplication, condensation, batching, or caching to see savings.</p>
Debug view for normalized provider quota/free-tier data persisted from upstream usage endpoints. This page is intentionally not linked from the main navigation.
</p>
{% if provider_rows %}
<table>
<tr>
<th>Provider</th>
<th>Configured Free Tier</th>
<th>Normalized Runtime Quota</th>
<th>User Snapshot</th>
{% if is_admin %}<th>Global Snapshot</th>{% endif %}
</tr>
{% for row in provider_rows %}
<tr>
<td><strong>{{ row.provider_id }}</strong></td>
<td>
{% if row.free_tier_info %}
<div><strong>{{ row.free_tier_info.description or row.provider_id }}</strong></div>