A shared view of supported AI spend.

Workspace is invitation-only. Join the waitlist to express interest; selected partners receive an invitation and help setting up supported sources. A waitlist submission does not provide immediate access. Existing invited members can sign in to Workspace.

1. Agree on the accounts and questions you want to review during onboarding.
2. Accept your Workspace invitation and sign in with the invited account.
3. Ask the appropriate provider organization owner or admin to connect supported cost sources.
4. Review the first report together, including missing coverage, before drawing conclusions.

Overview

Start with the selected date range and provider accounts. Read the reported subtotal together with coverage and freshness, then use the chart and project or model groups to investigate.

Projects

Review the cost groups reported by supported sources. Provider project names do not automatically identify a repository, a person or an accepted business outcome.

Briefing

Read the spending summary, available comparisons and questions worth investigating for your selected period. Missing data and insufficient comparison evidence remain visible.

Controls

Review configured budgets and the evaluations available for them. Budget notices depend on observed costs and coverage; a configured budget is not a provider spending limit.

Connections

Connect supported provider sources, inspect their read status and manage available key controls. The onboarding team helps confirm the right account and permissions.

Settings and activity

Manage your profile, members and available machine or app connections. Your activity keeps provider-key context, shared machine activity and briefing history distinct.

Choose the period and accounts before comparing reports. OpenAI and Anthropic cost views can show a provider-reported known subtotal even when some daily records are unavailable. Read the included, pending and missing coverage next to the amount. Missing days do not mean zero spend, and a subtotal is not a final invoice.

Usage records, local machine tokens and cost records can cover different periods. Available history depends on each connected source and the records retained for it. Some Usage views currently require shorter date ranges; if a range is unavailable, narrow the range rather than interpreting it as no usage.

Where enabled, Cursor and Copilot amounts retain their own period and estimate labels. They are shown separately from the OpenAI/Anthropic reported subtotal. Budget evaluations and comparisons also retain their stated scope.

An invited member can pair a supported machine from Settings → Machines and explicitly share eligible local session facts. Follow the enrollment instructions in Workspace and the terminal; connecting the machine and approving a push are separate steps.

npx aibill@latest workspace connect

After completing browser and terminal enrollment, review the sharing scope in Settings. The push command previews the exact outgoing facts and asks for confirmation. A default local CLI readout does not share session facts with Workspace.

npx aibill@latest workspace status
npx aibill@latest workspace push

Shared records contain supported session counts, token counts and repository labels where available. The push excludes raw prompts, transcript contents, full paths, raw session IDs and dollar amounts. Unknown token values and unattributed activity stay visible instead of being filled in.

Use npx aibill@latest workspace disconnect to review revocation from the CLI, or manage the machine in Settings. Revocation stops future uploads; previously accepted records follow the disclosed retention policy. The CLI reference explains recovery when a connection or push outcome is uncertain.

Workspace MCP is available through assisted invited onboarding. An owner or admin reviews the requesting app and Workspace before granting access to spend, projects, briefing and budget settings. It cannot refresh providers, change budgets or manage keys. Follow the Workspace MCP guide; supported client setup is confirmed during onboarding.

• Confirm the selected dates and accounts, source status and last successful read.
• Check whether the view shows provider cost, provider usage or machine activity.
• For a new connection, wait for its first accepted read; a saved key alone is not a completed report.
• Share the visible status and selected period with your onboarding contact. Keep provider keys and private credentials out of support messages.

See Sources for evidence labels and the privacy policy for hosted data handling.