Check Queries Used
The Usage page shows your query activity for the last 30 days, your monthly quota progress, and an estimated cost-savings figure. Everything is derived from thequery_events table, filtered to your account.
Last updated: April 2026
Stat cards explained
Four stat cards appear at the top of the page. Each shows a different dimension of your query activity:
Queries this period
Total number of queries in the last 30 days. Counts every event row in the query_events table where created_at ≥ 30 days ago.
Daily average
Total queries divided by the number of days that had at least one query. Excludes zero-query days from the denominator.
Peak day
The single day with the highest query count in the 30-day window. The date is shown as a sub-label (e.g. "Apr 2").
Active keys
Count of API keys where is_active = true. Revoked keys are excluded.
30-day chart
Below the stat cards is a bar chart labelled "Daily queries — last 30 days". Each bar represents one calendar day. Hover a bar to see the exact date and query count.
The chart spans exactly 30 days — days with zero queries show as empty bars, so you can see gaps in your usage pattern.
Quota progress bar
Below the chart, a progress bar shows your usage for the current calendar month against your plan limit. The counter resets on the first of each month.
The limit comes from profiles.queries_limit. Upgrade your plan from Dashboard → Billing to increase it.
Estimated cost savings this month
Based on avg 60% token reduction across your queries.
$X.XX
saved vs. unrouted
Calculated as: total_queries × $0.07. The $0.07 figure represents the average token savings per query at typical LLM pricing, assuming a 60% token reduction.
Refreshing data
Usage data is cached in localStorage to avoid repeated Supabase queries on every page visit. To force a live refresh, click the Refresh button (icon) in the top-right corner of the Usage page. The button shows "Refreshing…" with a spinning icon while it fetches fresh data.
Seeing more queries than expected? Learn how to lower your token footprint. Reduce Token Usage →