Analytics

Usage and billing

Review customer-scoped workspace runtime, managed AI activity, reconciliation status, and billing readiness.

Customer adminsPlatform operators
Console-rendered Analytics page with safe workspace runtime, usage totals, and reconciliation status.
Console-rendered example with safe data: Analytics is customer-scoped for customer admins and hides provider identifiers that are not needed for normal review.

Who can view usage

Customer admins can view Analytics for their own customer account. Customer members are intentionally denied Analytics. Platform operators use Analytics for onboarding review, support, and billing handoff.

What the numbers mean

FieldMeaning
Workspace runtimeObserved workspace activity for the selected period.
Managed AI usageCustomer-attributed provider activity when reconciliation is configured.
Reconciled statusWhether provider-side usage was matched to the customer account.
Billing stateWhether workspace creation is allowed by billing, trial, or prepaid readiness.

Usage data should be treated as account evidence. It should not include prompts, responses, transcripts, raw provider payloads, API keys, cookies, or workspace Secret values.

How to review usage

  1. Open Analytics.
  2. Confirm the customer scope.
  3. Choose the period you need.
  4. Review workspace runtime first.
  5. Review managed AI usage and reconciliation status.
  6. Use billing state to decide whether setup, funding, or support action is needed.

Reconciliation timing

Provider reconciliation can lag provider billing systems. If a current-day number looks low or missing, note the selected period and reconciliation status before escalating.

For formal billing questions, include the customer account, period, visible totals, and reconciliation status. Do not include payment secrets, invoice payloads, provider account secrets, or webhook details.

Why provider IDs are hidden

Customer-scoped Analytics intentionally hides provider project IDs and secret-bearing provider metadata. That is expected. The UI should provide useful usage status without exposing operational identifiers.

Billing readiness and workspace creation

Workspace creation depends on account billing state. Verified paid access or an approved trial can allow create when other readiness gates are clear. Prepaid accounts also need funded workspace-time and managed-AI balances before create proceeds.

Done When

  • Analytics opens only for customer admins or operators.
  • The selected customer scope is correct.
  • Billing state matches approved trial, prepaid, or paid access.
  • Reconciliation status is understood before quoting a final billing number.