scx

Simple Currency eXchanger for stdin streams.

scx reads text from standard input, detects USD amounts such as $12.34 or $1,234.56, converts them to a target currency at a given exchange rate, and writes the rewritten text to standard output.

It is designed to wrap tools like ccusage so their dollar figures can be read directly in your local currency.

Installation

npm install -g @yamamuteki/scx

Or run it on demand with npx:

echo 'Total: $1.00' | npx @yamamuteki/scx -c JPY -r 155

Usage

scx reads USD amounts from a pipe and converts them to your local currency.

First-time setup (one command):

scx config update         # fetch USD->JPY (default)
scx config update -c EUR  # or any other currency

This fetches the rate from Frankfurter; subsequent invocations need no flags.

Then pipe input:

echo 'Total: $1.00' | scx
ccusage | scx
ccusage | scx -c JPY -r 155        # one-shot (no setup needed)

Run scx --help for all commands.

Options

Environment variables

The three core options can also be supplied through environment variables. CLI flags take precedence.

export SCX_CURRENCY=JPY SCX_RATE=155
ccusage | scx

Config file

scx can read persistent settings from a JSON config file, so you don't have to repeat -r, -c, etc. on every invocation. Resolution order from highest to lowest precedence is: CLI flags > environment variables > config file > built-in defaults.

Location

The first file that exists in this order is used:

1. $SCX_CONFIG (when set)
2. $XDG_CONFIG_HOME/scx/config.json
3. ~/.config/scx/config.json

If $SCX_CONFIG points at a missing or unreadable file, scx exits with status 1 instead of silently falling back — explicit paths are treated as load-bearing.

If no config file exists at any of the default locations, scx simply runs with built-in defaults and any CLI/env values supplied.

Schema

{
  "currency": "JPY",
  "locale": "en-US",
  "rate": {
    "value": 155.23,
    "currency": "JPY",
    "updatedAt": "2026-05-26T08:00:00Z"
  }
}

All fields are optional. rate.currency records the target currency the rate corresponds to. If you override the effective currency (via -c or SCX_CURRENCY) to something other than rate.currency, the stored rate is treated as not applicable and you must supply a fresh -r / SCX_RATE for that currency. The rate-missing error names both currencies so the mismatch is easy to spot.

Managing the config file

scx config update                   # fetch the latest rate (see "Automatic rate update")
scx config update -c EUR            # fetch for a different currency (and switch to it)
scx config update list              # list the currencies config update can fetch
scx config show                     # show resolved settings with their source
scx config path                     # print the config file path
scx config set currency JPY         # write a key
scx config set rate 155             # write rate manually (no network)
scx config set locale en-US         # write a key
scx config unset rate               # remove a key
scx config delete                   # delete the config file entirely

scx config set rate <number> stores rate as the structured { value, currency, updatedAt } object using the already-configured currency (or the built-in default JPY when none is set). Values are validated before writing — currency must be a known ISO 4217 code, rate must be a positive number, and locale must be a recognized BCP 47 tag.

Automatic rate update

Refresh the exchange rate with a single command — no manual lookup.

scx config update                   # fetch USD->JPY (or your config currency) from frankfurter.dev
scx config update -c EUR            # fetch USD->EUR (also makes EUR the default currency)

The rate comes from Frankfurter, a free public API that aggregates daily reference rates from central banks worldwide. No API key needed. The fetched value is written to the config in exactly the same shape as scx config set rate <number>, with updatedAt reflecting when the fetch happened. Network failures, HTTP errors, and timeouts (5 s) exit with status 1; the stale config is left untouched. Override the target currency with -c <code> or SCX_CURRENCY.

Auto-updatable currencies

scx config update works for any currency Frankfurter serves — most ISO 4217 codes (JPY, EUR, GBP, VND, KWD, … ~170 in total). Run scx config update list to print them all as CODE Name, or browse the raw list at api.frankfurter.dev/v2/currencies (JSON).

If a currency isn't served, config update exits with an error — supply the rate yourself with -c <code> -r <number> per run, or scx config set currency <code> then scx config set rate <number>.

USD is a special case: it's the base currency, so scx config update -c USD (or with USD configured) sets rate 1 without any network call — letting you keep scx in a USD pipeline (e.g. the statusline) unchanged.

How it works

scx matches the pattern $<digits> in the input — supporting forms like $12, $12.34, $1,234.56, and $0.0012 — multiplies each detected amount by the rate, and formats the result with Intl.NumberFormat(locale, { style: "currency", currency }). Surrounding text is preserved as-is.

Because matching requires a literal $ prefix, inputs without one — for example ccusage --json, whose costs appear as bare numbers like "totalCost": 19.18 — pass through unchanged in the default text mode. Use --json (described below) to convert them.

Examples

Convert a piped string:

echo 'Today: $1.23 Total: $45.67' | npx @yamamuteki/scx -c JPY -r 155
# => Today: ¥191 Total: ¥7,079

Typing -c JPY -r 155 on every invocation gets old. Run npx @yamamuteki/scx config update -c JPY once, and the same conversion becomes:

echo 'Today: $1.23 Total: $45.67' | npx @yamamuteki/scx
# => Today: ¥191 Total: ¥7,079

The following examples run with scx config update.

Show ccusage output:

npx ccusage | npx @yamamuteki/scx

Override the currency or locale for a single run:

npx ccusage | npx @yamamuteki/scx -c EUR -r 0.92 -l de-DE   # euros with German formatting
npx ccusage | npx @yamamuteki/scx -c VND -r 25400 -l vi-VN  # Vietnamese dong

Convert ccusage --json output (JSON is auto-detected; cost values stay as numbers):

npx ccusage daily --json | npx @yamamuteki/scx

Claude Code statusline

scx can be wired into the Claude Code statusline so the live cost figures from ccusage statusline are shown in your local currency.

The most direct approach is to hard-code the rate in .claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "npx -y ccusage statusline | npx -y @yamamuteki/scx -c JPY -r 155"
  }
}

But the rate moves daily, and editing .claude/settings.json every time you want a fresh rate is annoying. Use scx config update instead — it keeps the rate in scx's own config:

{
  "statusLine": {
    "type": "command",
    "command": "npx -y ccusage statusline | npx -y @yamamuteki/scx"
  }
}

Now refreshing is one command (scx config update), and settings.json stays untouched.

The -y on each npx is important: the statusline is non-interactive, so any first-run install prompt would hang it.

The resulting status line will look like:

🤖 Opus | 💰 ¥775 session / ¥1,262 today / ¥1,262 block (3h 21m left) | 🔥 ¥1,525/hr | 🧠 N/A

For best startup performance, install both tools globally and use the bare names:

npm install -g ccusage @yamamuteki/scx

{
  "statusLine": {
    "type": "command",
    "command": "ccusage statusline | scx"
  }
}

JSON mode

In JSON mode scx reads stdin as a single JSON document, walks it recursively, and rewrites the values of known USD cost keys. Other numeric fields (token counts, timestamps, ratios, etc.) are left untouched.

JSON mode is enabled in two ways:

• Auto-detection (default): if the input's first non-whitespace character (after skipping a UTF-8 BOM) is { or [, scx tries to parse it as JSON. If parsing succeeds, JSON mode runs; if it fails, scx silently falls back to text mode so well-formed text starting with { is never broken. Disable with --no-auto-json.
• Explicit --json: forces JSON mode. Parse errors exit with status 1 instead of falling back. Use this when you want a parse failure to be loud (e.g. in CI).

ccusage daily --json | scx -c JPY -r 155          # auto-detected
ccusage daily --json | scx -c JPY -r 155 --json   # forced; fails loudly on bad JSON

Default cost keys

The following keys are treated as USD by default — chosen to cover ccusage's primary outputs out of the box:

Add more keys with --json-key:

ccusage daily --json | scx -c JPY -r 155 --json --json-key myFee,extraCharge

Output: number vs. string

By default the converted value stays a JSON number, rounded to the target currency's natural decimal places (JPY → integer, USD → 2 digits, KWD → 3 digits, etc.). This keeps downstream tooling — dashboards, bots, jq — happy:

{ "totalCost": 19.18 }     // input  (USD)
{ "totalCost": 2973 }      // output (JPY, --json)

Pass --json-cost-string to get a human-readable currency-formatted string instead:

{ "totalCost": "¥2,973" }  // output (--json --json-cost-string)

This is useful when piping into a viewer that displays the JSON as-is, but note that the value is no longer a number — code that expects typeof x === "number" will need to be updated.

Requirements

• Node.js >= 18

License

MIT