Add costs and use cases
Record a tool, an agent and a use case on the Costs and Inventory screens, or import them by CSV.
When enabled for your organization
Costs (/scorecard/costs) and Inventory (/scorecard/inventory) are Scorecard screens in release 0.3.0, switched on by Oabo for a deployment and off in production as of release 0.3.0. Writes need Administrator, Governance lead or Team lead; every other member sees the same values read-only.
Each task below has a Console recipe (on the screen) and a Headless one (the CSV import API, with a signed-in session). The switch is remembered across the docs.
Add a tool
On Costs, under Tools and subscriptions, click Add a tool. Three ways to say what it costs:
- From the catalog: pick a Catalog tool (Claude Team, ChatGPT Enterprise, GitHub Copilot Business, Cursor and so on). A plan with a list price fills the cost; a usage plan asks for it.
- An amount I pay: a Name, a Vendor and the Monthly spend ($).
- Usage billed, not in the catalog: the same, for metered spend. Blank means not entered, never $0.
Set Who pays: The business, The person or Not sure. Click Save tool.
Expected result
Total monthly AI spend updates. Until a use case uses the tool it is listed under Unexplained spend: tools and agents that power no use case in use this month.
Use the tools CSV. One row per tool; a blank monthly_cost means not entered, never $0.
name,vendor,catalog_key,who_pays,seats,monthly_cost
Claude Team,Anthropic,claude-team,business,12,
Invoice OCR API,Acme,,business,,480Columns: name, vendor, catalog_key, who_pays, seats, monthly_cost. Then preview and save as under Import by CSV.
Add an agent
Under Agents, click Add an agent. An agent carries three kinds of cost, each its own line: build, usage and upkeep. Leave what you do not know blank.
Agents are not in the CSV import. Add them on the Costs screen, or through the same agents API the screen calls, with a session.
Add a use case
On Inventory, give the use case a Name, a Stage (Planned, Trying it, Regular use, Paused, Retired) and an Area, then click Create use case. Open it to fill the rest, each section saved on its own: About (work type, owner email, audience, data class, affects people), Activity (how often), Powered by, Objective and key results, Benefits, History.
Note
Only Trying it and Regular use are graded. A Planned use case reads Graded once it is Trying it or Regular use.
Use the use-cases CSV. Coded fields take the code or the exact label.
name,owner_email,stage,area,work_type,frequency,involvement,audience,data_class,powered_by
Invoice matching,finance-lead@example.com,regular,finance,review,daily,,my_team,confidential,Claude Team
Lead research,sales-lead@example.com,trying,sales,find,weekly,,just_me,internal,Claude Team; Invoice OCR API| Import | Columns |
|---|---|
| tools | name, vendor, catalog_key, who_pays, seats, monthly_cost |
| use-cases | name, owner_email, stage, area, work_type, frequency, involvement, audience, data_class, powered_by |
Link what powers it
Under Powered by, pick the tools and agents behind the use case. A shared cost divides across the use cases it powers; How shared costs divide on Costs shows the split for any use case you pick. A tool that powers nothing stays unexplained spend.
The powered_by column names tools and agents by exact name, separated by semicolons. Import tools first so the names resolve; an unknown name is an error in the preview.
Import by CSV
There is no upload screen yet. The import is an API; switch to Headless for it.
# headers only, to start from
GET /api/v1/scorecard/import/tools/template
GET /api/v1/scorecard/import/use-cases/template
# dry run: one line per row with its action and any errors; saves nothing
POST /api/v1/scorecard/import/tools/preview (multipart file)
POST /api/v1/scorecard/import/use-cases/preview (multipart file)
# apply every row in one transaction, or none
POST /api/v1/scorecard/import/tools
POST /api/v1/scorecard/import/use-cases- Templates are headers only.
- Preview lists each row's action and errors (unknown codes or names, negative seats, repeated names) and saves nothing. Save applies every row in one transaction or none.
- Re-importing a name updates that row instead of adding another. A tool on a subscription plan keeps its plan.
- Limits: 2 MB and 10,000 rows per file. Extra columns are refused. One audit entry per import, with its row counts.
Expected result
The save response carries the same counts the preview did. The rows appear on Costs and Inventory at once, and the import is in the audit chain.