Usage views
| View | Where to find it | Who can see it | Plan availability |
|---|---|---|---|
| Usage graph | Enterprise: Settings > Usage > Usage graph Self-serve: Settings > Billing > Usage graph | All org members | All plans |
| Granular usage | Enterprise: Settings > Usage > Granular usage Self-serve: Settings > Billing > Granular usage | All org members | All plans |
| Contract burndown | Enterprise: Settings > Usage > Contract usage Self-serve: Settings > Billing > Contract usage | Org admins only (organization:manage) | Enterprise only |
| Invoices | Settings > Billing > Invoices | All org members | Self-serve cloud only |
Usage graph
The usage graph shows aggregate trace consumption for your organization, broken down by workspace. It covers the current billing period and does not show spend—for spend, refer to the invoice. Navigate to Settings → Billing and Usage → Usage Graph.Billable metrics
| Metric | What it counts |
|---|---|
| LangSmith Traces (Base Charge) | Every trace sent to LangSmith during the billing period, regardless of data retention tier. |
| LangSmith Traces (Extended Data Retention Upgrades) | Traces upgraded to extended retention (400 days by default, customizable for Enterprise customers). These are charged in addition to the base charge. |
| LangSmith Deployment Runs | End-to-end invocations of deployed LangGraph agents. See LangSmith Deployment billing for pricing details. |
| LangSmith Fleet Runs | End-to-end invocations of Fleet agents. Tracked separately for cloud-hosted and self-hosted deployments. |
| LangSmith Deployment Nodes Executed | Individual LangGraph node executions across deployed agents. Each step in a deployed agent’s graph counts as one node execution. Tracked separately for cloud-hosted and self-hosted deployments. |
The usage graph uses the term
tenant_id interchangeably with workspace ID.Contract burndown
Enterprise customers with prepaid commitments can view how much of their contract has been consumed. Navigate to Settings → Usage Configuration → Contract Usage. This view shows:- Usage summary: Total usage, total credits, and any overages. Overages occur when usage exceeds your total prepaid commitment.
- Commitment progress bars: Visual indicators for each commitment showing percentage consumed and dollar amounts for used vs. remaining. Contracts can have multiple commitments that apply to different time periods (e.g., year 1 and year 2 of a multi-year contract) or different products.
- Monthly usage chart: Bar chart showing usage amounts for each month within your contract period.
- Product rates: Table of your entitled products and their pricing.
Contract burndown requires the
organization:manage permission and is only available to Enterprise customers with prepaid commitments.Invoices
Invoices are available on self-serve cloud plans only. Enterprise cloud organizations have a separate usage view for tracking spend. Navigate to Settings → Billing and Usage → Invoices to see how your usage translates to spend. The first invoice shown is a draft of your current month’s invoice, reflecting your running spend to date.Granular usage
Granular usage gives you trace counts broken down by a dimension you choose (workspace, project, user, or API key) over a time range you select. This is useful for internal chargebacks, identifying high-usage teams, or auditing trace activity. Navigate to Settings → Billing and Usage → Granular Usage, or use the granular usage API.What “traces” means here
The granular usage view counts traces: root-level runs and all their child spans counted as a single unit. This is the same unit used for billing. It does not count individual spans, tokens, or model calls separately.When usage is recorded
Granular usage records traces by insertion time—when the trace was received and stored by LangSmith—not by when it ran in your application. In practice this difference is usually negligible, but traces sent with significant delay (e.g., buffered SDK uploads) may appear in a later time bucket than expected. For grouping options, time bucket sizes, and API reference, refer to Granular billable usage.Self-hosted limitations
Self-hosted LangSmith deployments have a different set of usage views available compared to Cloud, due to differences in billing infrastructure.| Feature | Self-hosted availability |
|---|---|
| Granular usage (trace attribution) | Available with feature flags or version ≥ 0.13.12 |
| Usage graph (aggregate traces) | Available on Helm chart 0.9.5 and later |
| Contract burndown | Available when Beacon phone-home is enabled |
| Invoices and payment management | Not available (billing is handled outside LangSmith) |
Granular usage on self-hosted
Granular usage is available on self-hosted deployments but requires explicit opt-in:- On LangSmith 0.13.12 and later, granular usage collection is enabled by default.
-
On earlier versions, enable it by setting both of the following environment variables:
Aggregate usage on self-hosted
The usage graph is available on self-hosted deployments running Helm chart 0.9.5 or later. LangSmith automatically generates and syncs organization usage charts, available under Settings → Usage and billing → Usage graph:- Usage by Workspace: trace counts (root runs) per workspace
- Organization Usage: total trace counts across the organization
Related resources
- Granular billable usage API reference
- Manage billing
- Data retention and usage limits
- Organization and workspace operations
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.