Query your MRR from the terminal

Updated 2026-08-04

Checking revenue shouldn't require opening a browser. The frgmnt CLI runs the same revenue engine as the app, from your shell.

Commands

npm run cli -- mrr                    # True MRR + ARR + per-platform
npm run cli -- today                  # today's cash, net of fees
npm run cli -- transactions --limit 10
npm run cli -- validate stripe rk_live_xxx
npm run cli -- sources                # what's configured
npm run cli -- mrr --demo             # no keys needed

Output:

$ npm run cli -- mrr --demo

  TRUE MRR  $6,622.73    ARR $79,473    313 subs
    STRP      $4,475.61
    APPL      $1,005.54
    LEMN        $767.32
    GUMR        $374.26

JSON for scripting

Every data command takes --json:

npm run cli -- mrr --json | jq '.mrr'
npm run cli -- today --json | jq '.net'
npm run cli -- transactions --json | jq '.[] | select(.amount > 100)'

Which makes some genuinely useful one-liners possible:

# Post MRR to Slack every morning
curl -X POST "$SLACK_WEBHOOK" -d "{\"text\":\"MRR: \
$(npm run cli --silent -- mrr --json | jq -r '.mrr')\"}"

# Append a daily row to a CSV
echo "$(date +%F),$(npm run cli --silent -- mrr --json | jq -r '.mrr')" \
  >> mrr-history.csv

That second one is worth doing. Nothing in this category gives you a clean historical export, and a cron job plus a CSV solves it in one line.

Configuration

Keys come from environment variables or ~/.frgmnt/config.json:

{
  "stripe": "rk_live_...",
  "lemonsqueezy": "...",
  "gumroad": "...",
  "appstore": "issuerId:keyId:base64(.p8)"
}

Use restricted, read-only keys. The CLI only ever reads.

Why it exists

The revenue adapters are framework-free TypeScript — no React Native imports — so the identical code runs in the iOS app, this CLI, the MCP server and the push worker. One implementation of interval normalisation, four surfaces.

Full command reference: the developer page. To expose the same data to an AI assistant, see the MCP server.