Usage and Capacity

Usage reporting helps admins understand whether the workspace is staying within its plan and where support load is growing. The live plan meters are shown in Billing; analytics pages focus on operational performance.

Usage Areas

Metric	What it represents
AI resolutions	Customer-facing AI answers counted against the monthly plan allowance.
Operators	Seats assigned to support users.
AI agents	Configured support agents and widget routing surfaces.
API sources	Knowledge-base sources attached to the workspace.
Indexed endpoints	Endpoint-level context extracted from sources.
Public API calls	Requests made with workspace API keys.
Live API checks	Authenticated checks run through Woes source testing.

Where Usage Appears

Surface	Use it for
Settings → Billing	Current plan, Stripe subscription status, included capacity, add-ons, public API usage by key, and projected monthly total.
Analytics	Support performance, surveys, customer behavior, agent quality, and operational trends.
API Reference → Usage	Server-side usage reads through the authenticated REST API.

How To Use Usage Data

Review usage before large docs or source imports.
Use extra API source bundles when a workspace needs more source capacity without changing its base plan.
Watch public API calls after adding server-side integrations.
Keep agent count aligned with real product or docs segmentation.
Use indexed endpoint counts to understand API context growth.
Review overage and plan limits before launch periods.
Use Manage subscription from Billing when payment details, invoices, or supported subscription edits need to be handled in Stripe.

​Usage and Capacity

​Usage Areas

​Where Usage Appears

​How To Use Usage Data

​Related Pages

Usage and Capacity

Usage Areas

Where Usage Appears

How To Use Usage Data

Related Pages