Personal connection plans change how many OAuth-connected clients can remain
active. They do not limit simultaneous sessions, and they do not unlock the
enterprise Activity, Analytics, ledger, margin, or end-user billing
surfaces.
Personal Usage
Open Usage to answer three questions:- How much did my agents spend?
- How many tool calls completed?
- Which tools accounted for that spend?
Enterprise Activity
Open Activity to investigate what the workspace spent, who spent it, and which agent tools they used. Spender, provider, endpoint, and period form one shared query that updates the totals, chart, breakdowns, and transaction evidence together. Transaction type narrows only the transaction list. Attribution narrows the list and ledger summary, not the analytics totals above them.
Activity shows:
- Gross spend, completed tool charges before refunds, with the matching prior-period comparison.
- Tool calls and average charge per call.
- Active spenders, covering end users, agents, credentials, and workspace members.
- Pool balance, which is the current balance rather than a total for the selected period.
- Spend over time, spender and provider breakdowns, and newest-first transactions.
Enterprise Analytics
Open Analytics for a higher-level business view. Choose 7, 30, or 90 days; each selection is compared with the equal preceding span. The dashboard reports gross usage, average charge per call, gross margin, tool calls, active end users, usage over time, unit economics, top end users, initiating identities, and services. This view is useful for trend and margin questions; use Activity when you need a specific transaction or spender.Query the API
Enterprise dashboard sessions and tenant secret keys withtenant:read can read the same data.
The analytics endpoint accepts either
days=7|30|90 or an explicit from and exclusive to timestamp. Explicit windows can set bucket=hour|day|week|month and filter by initiator, provider, and endpoint; endpoint requires provider. Use limit to cap each ranked list. An initiator has one of these forms:
createdAfter and exclusive createdBefore timestamps. They also accept initiator, provider, endpoint, externalUserId, category, sourceKey, account=platform, and exact attribution filters such as attribution.customerId=cus_42; the paginated ledger additionally accepts cursor and limit. Attribution narrows the transaction list and summary, not analytics rollups. Analytics can select unattributed, but the ledger cannot filter individual rows by that value.
Analytics counts completed tool charges. Top-ups, allocations, refunds, and other balance movements belong to the ledger. Gross spend is therefore before refunds; use the matching ledger summary when you need category counts or refund amounts for an exact filter.
Authentication and scopes
Choose the right dashboard or API credential.
Funding and billing
Understand balances, top-ups, margin, and payouts.
API reference
Read the exact filters and response schemas.