Skip to main content
Run the published Reins CLI in a new local project directory. This guide pins version 0.0.2, a testnet alpha.

​
Prerequisites

  • Node.js 22.12 or later and npm.
  • Network access to XRPL testnet and its faucet.
Use fresh testnet accounts and testnet funds only. Never reuse a production wallet seed.
1

Check the CLI

The command downloads the CLI from npm and prints 0.0.2. No source build or global installation is required.
2

Create testnet accounts

Initialization writes reins.yaml with account addresses and .reins/testnet-wallets.json with plaintext testnet seeds. It also creates a separate agent signing identity for the optional hardened account topology.Keep the wallet file local. Initialization writes .reins/.gitignore to keep wallet files out of Git. Do not upload the file to an agent, documentation service, or chat.Faucet requests can be slow or unavailable. If initialization fails, inspect its output before retrying.
3

Review the generated policy

Keep the generated version, network, and accounts fields. For a small payment-only example, replace the following sections:
This is a policy excerpt. The generated template initially includes Payment, CheckCash, and EscrowFinish; choosing only Payment narrows the delegated transaction types.amount caps each refill Check. period sets that Check’s expiration. It does not create a rolling daily spending limit.
4

Inspect the plan

Review the proposed transactions, signing roles, enforcement descriptions, and limitations. Planning does not submit transactions.
5

Apply, then verify

apply signs and submits transactions; the CLI refuses mainnet for this command. A failed apply can leave some steps completed. Inspect the reported results and live state before retrying.Verification reads the ledger. Read the individual findings rather than treating a successful command invocation as proof of the intended configuration.
6

Revoke as the owner

Revoke submits cleanup transactions and verifies the resulting ledger state. Read its final report. Submission alone does not confirm that revocation succeeded.

​
Connect an agent next

Start with an MCP server that can inspect and prepare transactions without a signing key. Keep the multi-wallet owner file out of the agent process.

Connect an MCP client

Configure inspection, policy status, transaction preparation, and explanations.
For command options, see the CLI reference. Before changing funding or permissions, read the enforcement boundary.