Responsible team: Reclaim / MarketWhale · Reviewed: 2026-09-20

Advanced local workflow

Reclaim SOL Without Manually Signing Every Transaction

Use reclaim-cli when a wallet has many empty token accounts and you want a repeatable local workflow. The key boundary is simple: previewing reads a public address; executing signs and submits transactions.

Most users should start with the browser flow. Choose local execution only after reviewing the estimate and deciding that automatic batch signing is worth the extra setup.

At a glance

Preview first. Sign only when you mean to.

Use a public address to see what may be reclaimable. This lane never loads a private key or signs a transaction.

Public address

The address you want to inspect

No secret

Read-only scan

Reclaim checks token accounts and eligibility

No signing

Estimate + warnings

Review candidates, deductions, and limits

Provisional

A preview is information, not permission to execute. Recheck before any signing decision.

1. Preview a public address — no private key

Start here even if you expect to execute locally. An explicit public address is enough to request a read-only preview; the command does not need a wallet connection, private key, or signing permission.

Install Node.js 20 or later and npm. From the official repository, run:

git clone https://github.com/MarketWhaleApp/reclaim-cli.git
cd reclaim-cli
npm install
npm run wallet:check -- YOUR_PUBLIC_WALLET_ADDRESS

Replace YOUR_PUBLIC_WALLET_ADDRESS with a Solana public address. This command builds the CLI and requests a preview from Reclaim. It needs no private key, wallet connection, or signing. The public address is sent to the service.

Illustrative text output for a hypothetical funded wallet, with build messages omitted:

Wallet Check — YOUR_PUBLIC_WALLET_ADDRESS
2 candidate accounts (0 protected).
Gross rent: 0.004078560 SOL
Service: 0.000244713 SOL; referral portion (service): 0.000163142 SOL
Subsidy: 0.000000000 SOL; service account rent: 0.000000000 SOL
Network fee: unknown (excluded from estimate).
Estimated net before network fees: 0.003670705 SOL
Current balance: 1.000000000 SOL
Eligibility: eligible; reasons: none

The command also prints observation time/slots, expiry, validation warnings, and a browser continuation link. Candidate counts are not proof every account will close. Network fees, changed state, and batch rounding can affect the result. The preview never starts signing. See the developer reference for JSON output, exit codes, and complete example responses.

The result is a decision aid, not a guaranteed payout or a transaction simulation. Candidate accounts, eligibility, deductions, and amounts can change before execution; network fees are unknown and excluded from the estimate.

2. Choose how you want to sign

Reclaim deducts 10% of recovered account lamports: 6% service and 4% referral. Without a valid external referral, both portions go to the service.

At a wallet balance of 0.0001 SOL or less, the subsidized flow adds 0.0001 SOL per closed account. An additional account-rent charge can apply when no native SOL token account exists. Network fees and rounding can also change the final balance.

See the full fees and eligibility reference. Preview amounts are estimates.

The browser flow keeps signing in your connected wallet and may ask for several approvals. Rejecting a prompt is always valid. Checking a public address does not select or authorize the execution wallet.

Local execution is the advanced option: the CLI signs prepared batches on your machine and submits them through Reclaim. Your private key is not sent to the service, but the service still prepares and receives the signed transaction submission.

Read the product reference for supported accounts and failure conditions before continuing.

3. Configure local signing only after the preview

Execution requires WALLET_PRIVATE_KEY on your own machine. Never paste it into a website, chat, screenshot, log, or support request.

After deciding to use local signing, copy .env.example to .env only if .env does not already exist. Open it locally and configure the signer using the repository instructions. Do not overwrite an existing signer configuration.

npm run build
npm run wallet:check

Without a public-address argument, wallet:check derives the wallet from your local signer. Confirm that it matches the wallet you intend to use, then review the estimate again. An earlier public-address preview does not choose the local execution wallet.

4. Execute one reclaim pass

npm run reclaim

This command begins execution: it requests prepared transactions, signs locally, and submits batches through Reclaim. It does not provide a browser approval popup for each batch. Agree on the wallet, estimate, and scope before running it; starting the command is not another preview.

Review transaction IDs and reported failures. Some batches may confirm while others fail. Re-scan before another pass. Network confirmation determines completion, and the service remains a dependency even though signing is local.

5. Repository and integration reference

See the official repository and README and agent workflow. For machine-readable output, use the preview-v1 command and API reference; JSON preview mode still requires an explicit public address and never falls back to a signer.