Bringing CostGraph to the CLI

Internally we keep a long wishlist of what a CostGraph CLI should look like. As with any wishlist, it was long, and knowing where to start was a challenge. After months of selling the dream internally, I am pleased to announce early access to the CostGraph CLI.

We have said many times that CostGraph aims to bring your FinOps data closer to you, whether you are in finance, engineering, or marketing. With this release we shift left: developers and agents get the full CostGraph API from the terminal.

Every command works two ways. Pass flags and get a table, or -o json for a script or an agent. Pass nothing and, if you are at a terminal, the CLI opens an interactive browser you can move through with vim keys, filter with /, and drill into with enter. In a non-interactive shell the CLI never prompts, so the same command works in CI.

Get started

1. 01
   Install the CLI

   $ curl -fsSL costgraph.ai/cli | shcopy
2. 02
   Sign in

   $ costgraph auth logincopy
3. 03
   Paste into your coding agent

   Using the CostGraph CLI, show me [what you want to know about your spend].copy

or

Let your coding agent do all three

Install the CostGraph CLI (curl -fsSL costgraph.ai/cli | sh), run `costgraph auth login` and give me the link to sign in, then show me [what you want to know about your spend].copy

Copy the prompt forClaude CodeCodexGrokOpenCode

Either way, the CLI signs in to the same tenants you see in the dashboard, so what you query in the terminal is what your team sees in the app.

Early access means the surface is still small on purpose. Today the CLI covers cost overviews and breakdowns, compute recommendations, virtual tags, and tenant switching, with shell completion for every flag and an API key path for CI. Reports, anomalies, and billing exports are next. If a command you need is missing, tell us what you would have typed.

If this sounds useful, get started for free or book a demo today.

P.S. You'd need an account first :)