clawpump

Launch a token on ClawPump from your terminal. Sign in with Google — no accounts to pre-create, no API keys to copy.

npx clawpump launch

A browser opens, you sign in with Google, and answer a few questions (name, ticker, avatar, dev-buy, free?). ClawPump mints the token on your behalf, so you keep 65% of every trade's creator fee. Your first 3 Solana launches are gasless & free; Robinhood Chain venues have their own free allowance per payout wallet, and the CLI tells you when it runs out.

Commands

npx clawpump pools      # mint on Uniswap (pools.trade)  (alias: uniswap)
npx clawpump launch     # sign in and mint a token (Solana)
npx clawpump pons       # mint on Robinhood Chain  (alias: rh)
npx clawpump pairs      # the assets a pons launch can be paired with
npx clawpump status     # where your Robinhood Chain launches stand
npx clawpump            # same as launch
npx clawpump logout     # forget the saved session on this machine
npx clawpump help       # help  (--version prints the version)

Uniswap (pools.trade)

npx clawpump pools

Three prompts — name, ticker, payout address — and your token is live in a Uniswap v4 pool on Robinhood Chain. Gasless: ClawPump fronts the gas.

Creator fees are collected hourly and split 65% to your payout address, 35% to ClawPump. The fee stream is a Uniswap v4 position NFT which ClawPump’s collector has to hold — Uniswap only lets a position’s owner realise its fees — so the split happens on every collection rather than at the pool.

npx clawpump pools --name "ClawBot" --ticker CLAW --payout 0xYourAddress --json

npx clawpump uniswap, npx clawpump deploy pools and npx clawpump launch --chain pools do the same thing.

Robinhood Chain

npx clawpump pons

Four prompts — name, ticker, pair asset, payout address — and your token is live on Robinhood Chain. Gasless: ClawPump's collector fronts the RH fee and gas, and creator fees land in the 0x payout address you give, paid in ETH or in the asset you pair with.

That payout address is written on-chain at launch and cannot be changed afterwards, so the CLI never guesses it or reuses a cached one. It is checked against its EIP-55 checksum, so a mistyped character is caught before anything is minted rather than routing your fees into a void.

Buy your own token at launch

npx clawpump pons --dev-buy 0.05

The buy happens in the same transaction as the mint, through pons' launch-and-buy router, so nobody can get in front of it. Pons opens every launch with a 99% snipe tax that decays to zero over ~5 seconds, and it is keyed on the recipient — so your buy is exempt while anyone racing it pays almost everything to the curve.

The allocation is never sponsored. The amount is in ETH, and the launch goes like this:

1. ClawPump quotes the total: the launch fee plus your allocation.
2. You send exactly that ETH from your payout wallet to ClawPump's collector on Robinhood Chain. A payment from any other address is not matched.
3. Paste the transaction hash at the prompt, or resume later:

npx clawpump pons --agent-id <id> --name "…" --ticker CLAW --payout 0x… \
  --dev-buy 0.05 --payment-tx 0xYourPaymentTxHash

The CLI prints that exact command, so nothing is lost between the quote and the payment. With --json the quote is emitted as {"status":"payment_required", "pay":{…},"resume":"…"}. The payment must be confirmed and recent (the service rejects payments older than about 30 minutes).

Leave --dev-buy off and you own 0% of your own token, which is what every ClawPump launch did before this flag existed.

--dev-buy works on pools.trade too, paid the same way. It is not atomic there: their launcher has no payable entry point and cannot bundle a buy, so ClawPump buys through the Uniswap v4 router right after the pool exists.

Dev buys are ETH-paired launches only for now: pons' router pulls an ERC-20 quote from the collector instead of taking it as payment, so the service refuses --dev-buy together with --pair, and so does the CLI, before anything is created.

Links

Pons shows a website, X, Telegram, Discord and Farcaster next to the token. They are written on-chain with the launch. The interactive run asks for X right after the pair asset (Enter to skip) and offers the other four behind one question; flags work too. Handles are fine for X, Telegram and Farcaster; everything else must be an https:// URL.

npx clawpump pons --website https://clawbot.xyz --x @clawbot --telegram @clawbot

pools.trade does not take links through the API, so pools has no such flags.

Non-interactive (for agents and CI):

npx clawpump pons --name "ClawBot" --ticker CLAW \
  --payout 0xYourRobinhoodChainAddress --logo https://your-logo.png \
  --website https://clawbot.xyz --x @clawbot --json

npx clawpump deploy pons and npx clawpump launch --chain rh do the same thing.

Pair against a real-world asset

Pons v2 can pair your token against a tokenised stock, an ETF, cbBTC or USDG instead of ETH. Creator fees are then paid in that asset. The interactive run asks for it (press Enter for ETH); --pair answers it up front:

npx clawpump pons --pair AMZN     # or NVDA, TSLA, AAPL, SPY, USDG, cbBTC …
npx clawpump pons --pair 0x…      # any asset the factory has approved
npx clawpump pairs                # the full list, with addresses and decimals

The CLI knows all 42 assets the factory approves today. The factory keeps the authoritative allowlist, so a newly added asset works immediately by address — no CLI update needed.

Before it mints

Interactive runs show what is about to happen and wait for a Y — a launch is irreversible, so nothing is created until you confirm. --yes and --json skip the prompt by design, so agents and CI are unaffected.

Names, tickers and addresses are validated before any account or agent is created, so a typo costs you a re-prompt instead of leaving a launcher behind with no token on it. A local logo file is uploaded before the launcher exists too, and a failed upload is an error rather than a quiet swap to a generated image. If a launch does fail after the launcher exists, the CLI prints the exact command to reuse it — with every flag you gave — rather than making another:

npx clawpump pons --agent-id <id> --name "..." --ticker CLAW --payout 0x... --pair AMZN --logo "..."

Every launch request carries an idempotency key, so a retry after a network timeout replays the same launch instead of minting a second token.

A Robinhood Chain launch settles asynchronously, and the service may have to re-broadcast it with a new transaction. The CLI waits up to ten minutes and shows a replaced hash; if it has to stop waiting, npx clawpump status reports where each launch stands and nudges an in-flight one along.

Zero dependencies

Node 18+ only — no packages. The EIP-55 check needs keccak-256, which Node's crypto does not provide (its sha3-256 is a different function), so keccak is vendored in and verified against the published digest vectors, the four EIP-55 reference addresses, and node:crypto's SHA3-256 across every block boundary.

How it works

• Sign-in uses a device-authorization flow (like gh auth login): the CLI opens clawpump.tech/cli/authorize, you approve in the browser, and a short-lived key is handed back to the terminal. Nothing to copy or paste. The session is cached in ~/.clawpump; --fresh signs in again, logout forgets it. Signing in on another machine revokes the earlier key, so the next run there simply signs in again.
• --json prints one JSON payload on stdout. The sign-in URL and a payment quote go to stderr, so an agent on a fresh machine still sees them.
• Avatar: press Enter to auto-generate an on-brand image, paste an image URL, or give a local .png, .jpg, .gif or .webp file to upload.
• Free vs. self-funded: gasless (free) for your first 3 Solana launches; after that you fund your own agent wallet and ClawPump still mints for you.

No dependencies — just Node 18+.

License

MIT