> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage analytics

> Separate saved subscription balances, operational dashboard metrics, and planned public usage reports.

Choose the data source that answers your question. A subscription balance, a conversation-cost chart, and a list of API requests describe different parts of workspace activity.

| Source | Current availability |
| - | - |
| [Subscription information](/api-reference/get-user-subscription-info) | Reads saved plan, credit, period, and invoice information |
| [Agents dashboard analytics](/agents-platform/monitor/analytics) | Reads operational analytics when the deployment has the required data connection |
| [Workspace usage](/api-reference/workspace/get-workspace-usage) | Returns an empty placeholder report |
| [API requests](/api-reference/workspace/list-api-requests) | Returns an empty placeholder report |

<Note>
  The public usage and API-request reports are not working activity reports. Their empty rows do not demonstrate zero usage, zero requests, or a complete audit history.
</Note>

## Review an interval

You need read access to the intended workspace and a clearly defined reporting period.

<Steps>
  <Step title="Confirm scope" id="usage-confirm-scope">
    Record the workspace, reporting dates, time zone, and any agent filters. Keep billing periods separate from custom analysis windows.
  </Step>

  <Step title="Read balances and operational metrics" id="usage-read-metrics">
    Inspect `credits_balance`, `credits_limit`, and `credits_used` in the subscription response. Compare dashboard metrics with known conversation records before interpreting an empty chart.
  </Step>

  <Step title="Label the report's limits" id="usage-label-limits">
    Record missing data and the source of each figure. Do not derive invoices, pooled balances, or request-level accountability from placeholder reports.
  </Step>
</Steps>

For cost decisions, use [cost optimization](/agents-platform/monitor/cost-optimization). For charges and payment terms, review the actual subscription and invoice workflow.

<AccordionGroup>
  <Accordion title="Can I group public usage by billing group?" id="usage-faq-groups">The contract includes grouping fields, but the current implementation does not calculate report rows.</Accordion>
  <Accordion title="Are operational costs the final invoice amount?" id="usage-faq-invoice">Do not assume equivalence. Keep operational measurements and billing records identified separately.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.