Usage, quotas and metering
Usage & Quotas shows what your workspace has used this month against what your plan includes. This page explains the tabs, how each meter counts, and what happens when you reach a limit. It states no quota values and no prices. Backoffice shows the values in force for your workspace. See pricing and your agreement for commercial terms.
What it is
Availability: Availability depends on your plan, role and the modules enabled for your organisation.
Usage & Quotas is under Backoffice → Billing & Plan → Usage & Quotas (/usage). Viewers, analysts, admins and billing users can open it. Some sections need more than view access.
| Tab | Content | Needs |
|---|---|---|
| Overview | Usage against quota for events, collector requests, ingestion requests, Score API calls, AI credits, MCP queries and domains. Burn-down chart. Usage by domain. Plan limits. | View access |
| Meters & quotas | One row for each meter, with usage, quota, projection and status. Usage by store. Usage by functionality and endpoint. | The capability to view billing: admin or billing role |
| AI & agents | AI Assistant usage. Agent and MCP usage. LLM sourcing usage. | View access. Agent and MCP usage needs the admin role. LLM sourcing usage needs the admin role. |
| KYC & identity | Verifications this period and an estimated spend. | The capability to view KYC usage: any role |
| PAYG & wallet | Module add-ons, pay-as-you-go accrual and wallet balances. | View access |
| History | Recent wallet activity and pay-as-you-go close-outs. | View access |
Old links still work. /billing/usage opens the Meters & quotas tab and /ai-usage opens AI & agents.
Quota rules in plain words
All counters run on the UTC calendar month. They reset at the start of each month.
| Meter | What counts | At the limit |
|---|---|---|
| Collector requests | Each token issuance request to the collector. | When quota enforcement is enabled for your organisation, a further token request is refused with 429, code COLLECTOR_REQUESTS_QUOTA_EXCEEDED, and a Retry-After header with the seconds until next month. Without enforcement the counter fills and nothing is refused. |
| Events | Each event submission. | The same enforcement setting applies. |
| Ingestion requests | Each authenticated request served by the ingestion service in native mode. Proxied and unauthenticated requests are excluded. The quota is 10 times your collector request quota. | Counted and shown. Never blocked. |
| Score API calls | Each authenticated, valid POST /v1/score call. | Calls above the included amount are billed as metered usage and are never rejected. |
| AI credits | AI Assistant use. The plan gives a monthly allotment. Purchased extra credits stay until used. | Backoffice shows Remaining. |
| MCP queries | MCP tool use against a monthly cap for the token scope tier. | Backoffice labels it Enforced — counts toward your monthly cap or Shadow only — not yet enforced. |
| Domains | Active domains against the plan maximum. | Creating another domain is refused with Maximum domains limit reached for this tenant. |
Two further points:
- A meter with no enforced quota shows Count only — no enforced quota.
- Each plan includes a share of the listed monthly allowances for module meters, rounded down to a whole unit. Whether an overage price applies depends on your plan. Where a plan sells no overage the table shows Hard cap.
Some figures are estimates. The page labels them. Billable units and pay-as-you-go accrual are estimated and display-only. What you are charged appears on your invoices.
Prerequisites
- A Backoffice user with at least view access for the Overview. The admin role or the billing role for Meters & quotas.
- A workspace with traffic. A new workspace shows No usage recorded yet.
- For KYC usage: the identity verification module activated for your workspace. Otherwise the tab says Not activated.
- For quota alerts: the admin role, and alert delivery set up. See Uptime checks, alerts, status reports and the status page.
Steps
1. Open Usage & Quotas
Go to Backoffice → Billing & Plan → Usage & Quotas. The subtitle shows the period. The tab you open is kept in the ?tab= part of the address, so you can bookmark it.
2. Read the Overview
Each quota card shows the used amount, the limit and N% used. The footer reads:
- Healthy below 75 percent.
- Approaching limit from 75 percent.
- Over 90% — upgrade recommended from 90 percent.
The Quota burn-down chart draws cumulative usage and a straight-line projection to month end. It says Within quota, Projected to exhaust on ~ or Quota exhausted on . A plan without a monthly event quota shows no limit line.
Usage by domain lists Domain, Status, Submissions and Visits for the period. Plan limits lists the static limits of your plan.
Backoffice labels figures by what they are:
- Usage vs quota: the metered counters your plan is measured against.
- Analytics & trend: raw event volume. These are trend metrics, not billing counters, and can exceed the quota count.
- Observed (not billed): read-only meters shown for visibility.
- Billable units (post free-tier): an estimate, display only.
3. Read the meters
Open Meters & quotas. Use Filter by group for All groups, Plan-included, Pay-as-you-go or Observability. Each row shows:
| Column | Meaning |
|---|---|
| Meter | The feature axis, with a link to its page. |
| Used / quota | Usage and the ceiling, with a percent bar. |
| Projected month-end | A straight-line projection. Monthly meters only. |
| Last 14 days | A trend line for meters with daily data. |
| Rate | The pay-as-you-go rate code and unit price, when the meter is billed. |
| Status | Within quota, Over quota, Tier-included or No ceiling. |
Below the table:
- Usage by store lists rows and estimated size this calendar month for each data class: Event data, Event payloads, Metrics, Warehouse analytics and KYC evidence, by storage location.
- Usage by functionality and endpoint shows what the Collect and Ingest endpoints served in a UTC month, per meter, against the included quantity, with % used and any overage. Choose the period with the selector.
- For KYC usage the section can show a Shadow invoice — not billed: what the period would cost under the rate card. The page states the rate card version and status. When a rate card is a proposal, the figures are informational and nothing is enforced or billed against them.
4. Compare plans
Open Backoffice → Billing & Plan → Packages & Add-ons → Included usage. The table has one row for each meter and one column for each plan. A cell shows the monthly included quantity and the overage price per unit, or Hard cap. Your plan column is marked Your plan. A badge says whether the rate card is active or Proposed — not billed.
5. Read KYC usage
Open KYC & identity. It shows Verifications this period and Estimated KYC spend (this period). The spend is a display-only estimate. Use the pricing page for the rate card.
6. Check pay-as-you-go and wallet
Open PAYG & wallet for module add-on state, estimated pay-as-you-go accrual and wallet balances. Open History for the latest wallet entries and pay-as-you-go close-outs. Full wallet detail is under Billing & Plan → Wallet.
7. Set a quota alert
Go to Backoffice → Integrations & API → Alerts → rules.
- Add a rule from the Quota usage template. It alerts when this workspace’s monthly quota usage reaches the threshold percentage.
- Set the threshold between 50 and 100 percent. The default is 90. The rule evaluates over one day.
- Choose one or more alert channels and save. The save needs a step-up check.
Rules can be written even when the evaluator is paused for your organisation. Backoffice shows a banner when it is. Status-report e-mails also summarise usage and quota. See Wallet, invoices and reports.
Verify it works
- The Overview shows a period in the subtitle and your quota cards with percentages.
- The burn-down chart shows a cumulative line that grows through the month.
- Meters & quotas lists meters with a Status for each.
- A quota alert rule shows in the Alerts list with its condition and state.
- After the month changes, the counters start again from zero.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Failed to load usage data | The overview read failed. | Click Retry. Other tabs load their own data. |
| This report is temporarily unavailable. | A section read failed. | Click Retry. |
| Unavailable on a card | That metric could not be read. | Retry later. |
| No usage recorded yet | No billable events in the current period. | Send traffic, or check the domain install. |
| Analytics events are higher than the Events quota count | Analytics volume includes rejected and removed events. It is a trend metric. | Use Usage vs quota for the billing counter. |
| This plan has no monthly event quota, so no limit line is shown. | Your plan has no event quota. | None needed. |
| No ingestion quota line | No collector request quota is set, and the ingestion quota is 10 times it. | None needed. |
| No quota or No allowance on a meter | The plan has no rate-card row for that meter. | Ask your account team. |
| Meters & quotas tab is missing | Your role has no view-billing capability. | Ask an admin or use the billing role. |
Token requests return 429 with COLLECTOR_REQUESTS_QUOTA_EXCEEDED | Quota enforcement is enabled and the collector request quota is used up. | Wait for the next UTC month or request more capacity. See Plans, packages and add-ons. |
| Maximum domains limit reached for this tenant | You reached the plan domain limit. | Remove a domain, or request a plan change. |
| Not activated on KYC & identity | The identity verification module is not activated. | Ask your account team. |
| Per-store usage appears here once the daily store-usage rollup has run | The daily rollup has not run for this workspace. | Check again later. |
| A rate card badge says Proposed — not billed | The rate card is not active. The figures are informational. | Use invoices for amounts charged. |
Related
- Plans, packages and add-ons: request more capacity.
- Wallet, invoices and reports: wallet, invoices and status reports.
- Billing status, grace period and reminders: banners and reminders.
- Uptime checks, alerts, status reports and the status page: alert channels and rules.
- Pricing reference: the definitions of collector request, event, ingestion request and Score API call.