Skip to main content

​
crewship paymaster

View LLM spend rolled up by crew, agent, or mission. Reads from the cost_ledger table populated by the Paymaster middleware.

​
Subcommands

​
crewship paymaster by-crew

Sample output:

​
crewship paymaster by-agent <crew>

Takes a crew slug or ID as positional arg. Output columns: Agent, Cost (USD), Calls, Tokens.

​
crewship paymaster by-mission <missionId>

Return the total cost ledger for a single mission (cost, call count, input/output tokens). Mission is workspace-scoped; foreign mission IDs return 404. There is no --range flag here — the server returns the mission’s full cost history.

​
crewship paymaster top

Sample output:
Scope format: <scope_kind>/<scope_id> (one of workspace, crew, mission, agent).

​
crewship paymaster subscriptions

Show flat-rate subscription usage — the API counterpart to the “Subscription plans” panel on the Paymaster dashboard. No $-figures because flat-rate cost is always $0 by construction; the row shape is plan + provider + call_count + token totals + last_used.

​
Global output

--format json|yaml|ndjson works for every subcommand and emits the raw rollup structs from the API.

​
Known limitation

Paymaster metering only captures calls that flow through internal/llm (Keeper, summaries, consolidation, quartermaster). Calls made by the agent’s own CLI adapter (claude, gemini) talking directly to the provider API are not recorded in cost_ledger. See the Paymaster guide for details.Consequence: the numbers here are accurate for server-side LLM activity; agent-driven spend is visible only on the provider’s dashboard. Use workspace-wide budgets as the authoritative cap until the proxy rework lands.