Billing & usage
Understand where usage goes, drill into individual calls, and run read-only reports and see their final credit charge.
Spend and Intelligence are available to workspace admins and platform admins. Both tabs share the same frame; returning to a loaded tab preserves your results, table position and drafts. Refresh explicitly advances the snapshot. The existing Model evals panel is now its own platform-admin-only Evals sidebar page.
Spend includes credits charged, the estimated list value of bring-your-own-key usage, and free promotional usage at list price. Hover or focus a figure for its components. BYOK estimates and free list value are not debits from your credit balance.
Amounts are kept in integer nano-dollars: 1,000,000,000 equals one US dollar. Report APIs carry amounts as decimal strings and CSV dollar columns retain nine decimal places. Cached input is part of input tokens; reasoning is part of output tokens, not extra volume.
Choose preset or custom dates and your timezone in the date dropdown. Today starts hourly; choose Hourly or Daily beside the date options for windows up to seven days. Views → Workspace shows one summary; Member or another view splits usage into contributors without changing your filters. Filters (n), beside the date and Views controls, reveals existing pills below and immediately opens the filter picker. Select a dimension and its values, starting with All; editing a pill reopens the same picker and removing it restores those values without changing the view. Requests and Provider attempts remain a separate counting choice inside the filter menu. Multiple values within one filter mean OR; separate filters mean AND.
API key ownership is not proof of the human behind every request. End-user labels are supplied by the caller. Missing attribution is kept visible rather than guessed. Click a group to narrow the report, or choose View Activity to inspect the same exact filters and dates.
Export CSV includes every group in the selected snapshot, not just the visible page. Export supports up to 10,000 groups. Very large windows fail explicitly; narrow the range instead of interpreting a partial result as a complete total. Grouped by Workspace, the button reads Export breakdown CSV: the chart and table show one aggregate summary, but the export still returns the full breakdown groups for your currently selected filters, not a single workspace row.
A dimension is a way to split the same usage: model, API key, recorded member/key owner, end-user label, provider, funding, API surface, outcome, error, repeated prompt, or usage source. Search the dimension menu, then search the observed values by name or ID. API keys and members retain their stable IDs underneath their display names.
New filters include calls without the selected label by default. They appear as a No API key, No member, or No tag value option. Remove that option to exclude them, or select it alone. Clicking a specific group is an exact drill and does not add unlabeled calls. The trail above the report shows your drill path and lets you return to an earlier slice.
Only one report menu opens at a time. Click outside or press Escape to dismiss it. The breakdown scrolls under its header and loads more groups as you scroll; Load more also works by keyboard. Table sorting, Activity and CSV retain the same snapshot.
Request tags are key/value labels you supply, such as run=eval-September or team=search, to report on multiple workloads using the same API key. They are not permissions or verified identity. The tag picker searches keys and values already observed in the selected reporting context.
Inside Views or Filters → Tag, workspace admins can choose Create tag to save a key/value pair for future requests. Defined tags are marked separately from observed usage and do not rewrite historical calls. Valid request tags require no pre-registration: the collection contract discovers new keys and values from the supplied header X-Explabs-Tags: {"run":"eval-September"}, not by reading prompt text. SDKs carry it through extra_headers.
The Tag view groups by one key. A tag filter separately selects its values without changing that view. Filters support multiple values: click or press Enter to toggle a selection, then Apply to update the report once. Several tag keys combine with AND. Workspace definitions are not organization entitlement tags and never grant access or credits.
Use at most 16 entries within an 8 KiB header. Keys begin with an ASCII letter and contain at most 64 letters, digits, underscores, dots or hyphens; values are nonempty and at most 256 Unicode characters. The explabs. prefix is reserved. Values match exactly, including case. Never put secrets, prompts or personal information in tags.
The Spend tab leads with usage value, prior-period change, average daily spend and request count. The selected dimension drives the stacked graph, matching colored leaders and breakdown. Model shows top models; Prompt shows repeated groups and cached input; Outcome and Error show failures and pre-dispatch refusals. Funding adds the paid, BYOK and free component view.
Period change compares the observed interval to an equally long interval immediately before it, clipped at the report snapshot. Hover for the actual dates. All time and incomplete or unavailable history have no comparison. Daily average uses 24 elapsed hours and is not a forecast.
Filters and actions share one row: Export CSV, View Activity and Refresh. An amber shield appears only when data has an issue; hover, focus or tap it for details. Repeated-prompt, error and key panels appear only in relevant dimension views, not all at once. Refresh preserves filters while advancing the shared snapshot.
Admin telemetry, Overview and Spend share the same chart and ranked-list components. The selected dimension’s entities retain their colors across narrowing, and chart, legend and leaders agree. Click a chart column to pin its popup; click elsewhere or press Escape to close it. Hover, focus or tap a row to open Paid, Bring your own key and Free in a separate secondary popup, without changing the pinned popup’s size or layout. Legend and table actions still drill further; Other is the exact remainder, not one selectable value. Notes are behind the eye beside a breakdown title. Displayed amounts use two decimals; exact amounts remain in CSV and the API. Table shells, sorting controls and spacing are shared too, while request-inspection rows retain their domain-specific fields. Daily and monthly buckets follow your calendar; hourly UTC buckets have timezone-aware labels that distinguish repeated local hours.
For Prompt, use View requests & prompts to inspect the same filtered calls, then expand a captured prompt. Digests are identifiers, not text. Content is available only where storage was enabled and the retention window permits it. Cache read % means cached input divided by input tokens, not a request hit rate or estimated savings.
Spend reports settlement-time usage. Historical projection can take time; incomplete coverage and unknown provider usage are labeled. Accepted failures before provider dispatch count as requests. Protocol rejections before admission are currently outside this projection.
Application headers are not yet a collected reporting dimension. Tag grouping reads captured tags only; older calls remain untagged. The shared tag header requires the corresponding gateway engine release and is not available merely because the reporting filter exists.
Intelligence is Pro-only and read-only. Ask a question about cache usage, errors, or spend contributors, or select Run a report. Your first visit offers a report invitation; dismissing it is remembered for you in this workspace. It sends your question plus content-free aggregate evidence to an analysis model, never stored prompts or completions.
Reports use credits. There is no maximum to set before starting; the final charge appears in credits once the report settles. Unused reserved availability is released when the run settles.
Intelligence puts one report document on the left and independent chat on the right, inside the same padded frame as Spend. The panes scroll independently while the composer stays at the bottom. Spend filters do not apply here; new chats start from their own 30-day usage window. Generating or opening a report never adds a chat message, attaches a report reference or changes your draft. Follow-ups continue completed questions, not reports. Up to 12 genuine saved question turns are restored, with missing history labeled rather than invented.
Investigated reports check errors, cache reuse, retries and spend, then show up to four supported changes with their evidence. A fix names the affected target and exact request or configuration change; copyable examples are text, never automatically executed. The model cannot substitute “look into this” for a fix. Missing cache directives, token eligibility or client retry settings remain explicit evidence gaps, not invented prescriptions or savings.
While a report runs, live updates show completed checks and verified facts. Reconnecting resumes those updates without starting another paid operation. Final fixes appear after evidence validation; partial checks on failed or cancelled work are not a completed report.
Choose any completed, failed, cancelled or active report from Previous reports. Each option shows its date, status and settled charge, or pending while unsettled. There is no separate failed-attempt section. Chat history remains independent. Report errors stay by Run a report; question errors stay by chat. History, recovery and cancellation remain available when new work cannot start.
Saved analyses stay inside your organization and include evidence links and limitations. Model alternatives are candidates to evaluate, not automatic configuration changes or guarantees of equal quality. Opening the page never starts paid work.
Use your organization’s API key with POST /api/orgs/<org_id>/spend/query, /spend/facets, /spend/series, /spend/activity and /spend/export. Keys can read only their own workspace; Personal usage requires a signed-in member. Reuse the report’s coverage.as_of for the same snapshot across detail and export.
Activity accepts include_features: true to include Intelligence charges separately from API requests. CSV uses one bounded grouped read, preserves exact amounts and includes the query. Captured prompt bodies remain a separate member-authorized API, not available to ordinary API keys. The machine-readable contract and examples live at llms.txt.
Never put secrets, prompt content, email addresses, or personal information in reporting labels or tags. Labels are metadata. Privacy erasure removes caller attribution while preserving anonymous financial amounts.
See the Platform privacy policy and Telemetry for data controls and usage APIs.