nirium-cli 3.0.0

Breaking changes

• nirium pay's --amount flag was removed; it never did anything (options.amount was never read). Use --max-amount <usd> instead, a per-payment cap enforced before anything is signed.
• engines.node is now >=22.12.0 (was >=18). @stellar/stellar-sdk 16 pulls in the ESM-only @noble/hashes 2.x, and require() of an ES module only works unflagged from Node 22.12.0.

Fixed

• nirium pay no longer fails with NiriumAgent is not a constructor on a clean install (#147). nirium ships as CommonJS, so the default import was the whole exports object, not the Agent class. Fixed to import the named Agent export.
• nirium serve no longer fails every real payment with x402 payments unavailable / the facilitator could not be reached. x402Serve() loads @x402/express with a dynamic import(), deliberately optional in the SDK so consumers who only buy via x402Fetch() don't need Express, and it fails with a clear, actionable error rather than crashing — not an SDK bug. But serve always calls x402Serve(), with no path that doesn't need it, so it should have declared @x402/express itself, the same way it already declares express. Found while doing the manual testnet smoke test for #137; the existing serve tests never caught it because they only check CLI validation and kill the process as soon as it starts listening, before any payment is attempted. Added @x402/express as a direct dependency.
• packages/cli had drifted from the SDK (#137): nirium was pinned at ^0.16.0 (SDK: 0.16.1), @stellar/stellar-sdk at ^14.5.0 (SDK: ^16.3.0, not 17: @x402/stellar requires ^16.3.0), and the version was hardcoded twice (.version('2.0.1') in bin/nirium.js and "version" in package.json). Bumped both dependencies to match the SDK and engines.node to >=22.12.0 (stellar-sdk 16 pulls in the ESM-only @noble/hashes 2.x; require() of an ES module only works unflagged from Node 22.12.0). .version() now reads package.json at runtime, the same file nirium-doctor's user agent already read, so there is one source instead of two. The @stellar/mpp@0.7.1 peer warning for @stellar/stellar-sdk@^15.1.0 (upstream, unrelated to this package) persists, but stellar-sdk is now a single shared copy (nirium, @x402/stellar and the root project all resolve to the same install) instead of two separate ones.
• nirium status no longer exits 0 when the agent is down (#138). It printed Agent unreachable or Agent returned error but always exited 0, so it could not be used in a script or a CI health check. Now exits 1 if the agent is unreachable, times out, or /health is not 2xx. Added --json (the raw /health fields plus ok) and --timeout <ms> (default 5000) so an unreachable host does not hang.
• nirium verify no longer reports VERIFICATION PASSED when nothing was actually checked (#149). A pass was computed as "no check failed", which is also true when both the hash and the signature check were skipped (an unsigned hash-only anchor with no --hash or --evidence). A pass now requires at least one check to have run and succeeded. When both are skipped, verify prints NOTHING VERIFIED, exits non-zero, and sets verified: false in --json. A hash-only anchor with a valid signature and no --hash, or an unsigned one with a matching --hash, is still a pass.
• nirium pay no longer reports a failed request as a success (#148). It always printed Payment Negotiated & Request Completed and exited 0 after a successful payment, even when the request that followed answered 4xx or 5xx. Success (text and --json, exit 0) now requires response.ok; otherwise it prints the failure and the response body and exits 1.
• nirium pay's --amount was removed: it was declared on the command and documented, but options.amount was never read, so it did nothing. Replaced with --max-amount <usd>, a per-payment cap. nirium does not publish initX402({ maxAmountPerPayment }) yet, so the cap is enforced with the SDK's pre-sign policy hook (initX402({ policy }), published since 0.16.0), which runs before anything is signed. --max-amount rejects zero, negative and non-numeric values before any network call.
• nirium verify no longer fails every hash-only anchor (#139). Without a record it compared content_sha256 against sha256("") and built the signed statement from that same empty hash, so both checks always failed. Hash-only documents now verify the agent signature over nirium-audit-v1:<content_sha256>, and the hash is reported as not checked unless you pass --hash <hex> or --evidence <file>. Record documents behave as before.
• nirium verify accepts hex as well as base64 signatures, and SEP-53 signed messages (Freighter signMessage) after raw ed25519, matching the anchoring node.

Added

• nirium verify --hash <hex> and --evidence <file> to compare a hash-only anchor with your original evidence.

nirium 0.16.1

Documentation and package metadata only. dist/ is identical to 0.16.0.

Changed

• package.json repository now points to nirium-protocol/nirium with directory: packages/sdk, and bugs.url to nirium-protocol/nirium/issues (both pointed to the old nirium-sdk repo). nirium-mcp gets the same change in its own next release.
• README: documents the x402Serve() replay and rate-limit guard (guard, X402GuardStore, createUpstashX402GuardStore) with a tested example, credit to Edgadafi, and rewrites the "known limitation" text: without guard there is still no replay protection or rate limit. Documents ResilientSignalClient.
• README: /premium/signals exists only on testnet (mainnet answers 501). Removed two dead links (/docs/api, /docs/mcp), fixed the GitHub link, removed long dashes.

nirium-mcp 0.6.3

Added

• README: documents the 11 Treasury tools (get_treasury_info, get_treasury_vault, get_treasury_vaults, get_treasury_strategy_asset, deploy_treasury_vault, deposit_to_treasury_vault, withdraw_from_treasury_vault, set_treasury_rebalance_manager, build_treasury_rebalance, submit_treasury_tx, execute_treasury_rebalance), missing since they shipped. Text taken from each tool's own description in the code. Says which build an unsigned XDR, which signs with Nirium's own key (execute_treasury_rebalance, invite-only), and under what condition.

Fixed

• prepublishOnly: npm run build added, so a future publish can't skip the build the way 0.6.1 did.
• README: "Run from source" and the LICENSE link pointed to the old nirium-sdk repo.
• Removed long dashes from README.

nirium-mcp 0.6.1

No new tools and no change to any tool. Package metadata and the reported version only.

Changed

• The server version, the startup log line and the code header no longer have 0.6.0 written by hand. The version is read from package.json, so the server reports the version that was installed (0.6.0 reported itself correctly only until the next bump).
• package.json repository now points to nirium-protocol/nirium with directory: packages/mcp, and bugs.url to nirium-protocol/nirium/issues (both pointed to the old nirium-sdk repo).

nirium-cli 2.0.1

Documentation only. No behavior changes.

Changed

• README: the secret key section no longer suggests nirium config set secretKey S..., which is refused since 2.0.0. It lists the three safe ways instead.
• README: nirium status is now documented, including that its default URL is http://localhost:3001 and not the Nirium agent.
• README and nirium doctor help text: the MPP check only validates configuration, and Nirium does not charge MPP payments on mainnet today.
• README: the x402Serve() usage telemetry is off by default and only sent when NIRIUM_X402SERVE_TELEMETRY=true (as in nirium 0.16.0). The text said it was on by default.
• README: fixed the nirium verify options table and removed long dashes.

nirium-cli 2.0.0

Breaking: three ways of passing a secret on the command line are gone. A key typed as an argument stays in your shell history and shows up in ps for anyone on the machine. The safe ways to supply a key are the environment variable (NIRIUM_SECRET_KEY, FACILITATOR_API_KEY) or the hidden prompt.

Removed (breaking)

• nirium pay --secret <key> (#108). Use NIRIUM_SECRET_KEY, or run nirium config set secretKey and type the key at the hidden prompt.
• nirium config set secretKey <key> and nirium config set facilitatorApiKey <key> (#111). Run the same command with no value: in a terminal it asks for the key without echoing it, and without a terminal it reads the key from stdin. A key passed as an argument is refused and not saved.
• nirium serve --api-key <key> and -k (#111). Use FACILITATOR_API_KEY, nirium config set facilitatorApiKey, or the hidden prompt. Without a terminal and without the variable, serve waits up to 10 seconds for the key on stdin and then exits with the missing-key error.

Changed

• Depends on nirium ^0.16.0 (#109). The scaffolds written by nirium create pin the same range.

Added

• nirium doctor --seller <url> validates a remote x402 seller without paying (#105) (#110). Thanks to @Edgadafi. It checks for HTTP 402 with a decodable PAYMENT-REQUIRED header, that network, asset, amount and payTo are present and well formed, that resource.url is https://, and that a CORS preflight from a random origin does not return 5xx, that the 402 response exposes PAYMENT-REQUIRED and PAYMENT-RESPONSE (a preflight that lists them does not count), and that PAYMENT-SIGNATURE is allowed. --json still prints the report for CI. The probe never sends a payment. The User-Agent is nirium-doctor/<version> from this package's package.json.

Install: npm install -g nirium-cli@2.0.0. Upgrading from 1.x: replace --secret S... with NIRIUM_SECRET_KEY, and --api-key <key> with FACILITATOR_API_KEY.