Parallel from your terminal.
Live protocol data, mint and redeem, savings, bridge, staking and x402 payments. Readable tables for you, clean JSON for your scripts, and nothing signs until you hand it a wallet.
Read the protocol.
No wallet, no config.
Everything, immediately
TVL, supply, savings rate, backing, solvency, bridge quotes, staking positions, governance proposals. No key, nothing to configure: install and query.
Defaults, if you want them
Tired of passing --chain? config init walks you through your defaults once and writes ~/.parallel/config.toml. It is optional: every command works without it.
Forty-four commands.
Only 10 of them move funds. The other 34 need nothing but a shell.
All four are x402: capabilities and quota, verification, and prepare, which builds and signs the payload agent payments run on. What x402 is
Then sign, when you choose.
Preview it
Add --dry-run to any transaction command and it builds and prints the unsigned transaction, with no key involved. Add --address to simulate for a real account.
Then broadcast it
Point --wallet at an encrypted V3 keystore or an environment key and the same command signs and sends. This is the one thing the MCP server cannot do: there, writes always come back for you to sign yourself.
With --wallet, transactions broadcast immediately after signing. There is no extra confirmation step.
Use a dedicated wallet with limited funds, and preview with --dry-run first.
Built to be scripted.
JSON without asking
Output switches to JSON the moment stdout is not a terminal, so commands pipe straight into jq. Force it anywhere with --json.
Dry-run anything
Add --dry-run to build and print any transaction with no key involved. Add --address to simulate for a real account rather than the zero address.
Historical series
Add --history to backing, tvl, savings-rate or supply for a daily series, bounded with --from and --to. Enough to back a dashboard without an indexer; on supply it covers usdp only.
Safe in cron
One response envelope everywhere, and failures exit 1 with a typed code such as WALLET_REQUIRED or UNKNOWN_CHAIN. Protocol refusals come back as UNKNOWN with the reason prefixed in the message.
What people ask
A command-line interface to the Parallel protocol: live data, mint and redeem, savings, bridge, staking, governance and x402 payments. It prints readable tables in a terminal and JSON everywhere else.
npm install -g @parallel-protocol/cli, or run it without installing: npx @parallel-protocol/cli protocol overview. Requires Node.js 22 or newer. The binary is parallel, and the package is MIT-licensed.
Not for reads. Every data command runs with no key, no account and no configuration. Transaction commands need either --dry-run, which prints the unsigned transaction, or --wallet, which signs and broadcasts.
It never looks for a key unless you pass --wallet. That resolves to a standard encrypted V3 keystore or the PARALLEL_PRIVATE_KEY environment variable. With --wallet, transactions broadcast immediately after signing, so use a dedicated wallet with limited funds.
USDp itself is live on 24 chains. The Parallelizer, for mint and redeem, and the Savings module, for sUSDp, run on 4 of them: Ethereum, Base, Avalanche and HyperEVM. Reads like protocol chains report live status for every deployment.
Yes. Output switches to JSON automatically whenever stdout is not a terminal, every response uses the same envelope, and failures exit 1 with a typed error code such as WALLET_REQUIRED or UNKNOWN_CHAIN.
Read the full command reference.
Questions? Join us on Telegram.