Claiming Fees
Collect your share of trading fees from your deployed tokens.
Looking to read fees without claiming? See Reading Creator Fees for REST, on-chain, and CLI options.
This page covers Doppler launches — those whose launch.launchType is doppler (GET /token-launches/:tokenAddress reports it). A bankr_v3 launch (every Arc launch, and any Arbitrum launch whose provider was bankr_v3) claims from its own Creator Fee Vault or Fee Locker: use the Fees section on the token's Trade page or in Your Tokens, POST /token-launches/:tokenAddress/fees/claim (it detects v3 launches too), or GET /launch-v3/:tokenAddress/fees?account= + POST /launch-v3/:tokenAddress/fees/build-claim to self-sign. The v3 Fees section shows the launch's fee recipient and their claimable balance to every viewer, not just to the recipient. To change who receives them, see Transferring fees → Bankr Launch v3 tokens.
Who Can Claim
Only the current fee beneficiary can claim fees from a token. By default, this is the deployer wallet. If you've redirected fees to another address, only that address can claim.
Your Share
You receive 0.665% of your token's trading volume — 95% of the 0.7% pool swap fee; your token's 0.285% LP fee compounds as locked liquidity in its own pool and never needs claiming. See the Fee Structure for the full split. Fee schedules are fixed at launch, and claiming works the same on earlier tokens.
Checking Your Fees
See how much you've accumulated:
"check my fees for TokenName"
"how much fees have I earned from 0x1234...?"
"show all my tokens with unclaimed fees"
This shows fees for tokens where you're the current beneficiary.
Claiming Fees
From the Web
Open the token's Trade page (bankr.bot/terminal/trade/<tokenAddress>) or Your Tokens in the terminal and click Claim fees. You can connect either your Bankr wallet or an external wallet (e.g. MetaMask, Coinbase Wallet). The page will check your eligibility and show your claimable amounts before you confirm.
- Bankr wallet: Signs in with your existing Bankr account and executes the claim server-side. Gas is sponsored by Bankr on Base, Robinhood Chain and Arbitrum — you can claim with a $0 ETH balance. On Arc nothing is sponsored, so the claim spends a little native USDC from your Bankr wallet. The server submits the
collectFeestransaction via your Privy-managed wallet. - External wallet: Connects via WalletConnect/RainbowKit and signs the transaction in your wallet. You pay the gas — make sure the wallet holds a little native gas on the token's chain.
Gas
| Claim path | Who pays gas | Gas needed in signing wallet |
|---|---|---|
| Web UI with Bankr wallet | Bankr (sponsored); on Arc, you | None (a little USDC on Arc) |
| Web UI with external wallet | You | A little on the token's chain |
POST /token-launches/:tokenAddress/fees/claim (auth'd API) | Bankr (sponsored); on Arc, you | None (a little USDC on Arc) |
POST /public/doppler/build-claim + self-sign | You | A little on the token's chain |
CLI bankr fees claim (uses your Bankr account) | Bankr (sponsored) | None |
CLI bankr fees claim-wallet (your private key, Base only) | You | A little ETH on Base |
API example — single-call claim (recommended)
POST /token-launches/:tokenAddress/fees/claim builds, signs, and broadcasts in one call. Auto-detects Doppler, Clanker and Bankr Launch v3.
curl -X POST https://api.bankr.bot/token-launches/0xTokenAddress/fees/claim \
-H "Authorization: Bearer $BANKR_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'
# → { "transactionHash": "0x...", "status": "success", "signer": "0x...", "chainId": 8453, "description": "..." }
Auth: Privy JWT (web) or API key (CLI/partners) via Authorization: Bearer <token>. Requires walletApiEnabled on the key. Returns a single submitted-tx receipt.
Legacy endpoints /user/doppler/claim, /user/doppler/execute-claim, /clanker/claim, and /agent/doppler/claim are deprecated: they still respond, with Deprecation and Sunset headers, but their sunset date has passed — use the unified endpoint.
Gas sponsorship covers up to 10 transactions per day per wallet across all sponsored paths, and at most $3 of gas per day; whichever runs out first ends sponsorship until the window resets. This is usually more than enough for fee claims, but high-volume agents claiming many tokens daily, or claiming on Robinhood Chain during a fee spike, should account for these ceilings.
This matters for agent wallets and partner integrations: if you don't pre-fund agent wallets at creation, route claims through a Bankr-managed wallet or the authenticated claim endpoint to avoid the chicken-and-egg problem of needing ETH to claim ETH.
From Chat
Collect your earnings via natural language:
"claim my fees for TokenName"
"claim fees for 0x1234..."
What You Receive
When you claim fees, you receive two assets:
| Asset | Description |
|---|---|
| Your token | Your share of the swap fee |
| The quote token (WETH by default) | Your share of the swap fee |
Both accumulate in the Uniswap V4 liquidity pool and are claimed together.
Tokens on the 1.75% schedule claim exactly like earlier launches — your creator share accrues on the pool's fees manager and pays out in both tokens. Only launches with the quote-only fees option claim from the hook contract's fees manager instead (the claim APIs resolve this automatically), and the entire creator share arrives in the quote token (e.g. WETH) — there is no launched-token leg.
Claim Frequency
You can claim at any time. There's no minimum threshold, but consider gas costs when claiming small amounts.
Viewing Your Tokens
See all tokens where you're a fee beneficiary:
"show all my deployed tokens"
"list my tokens with fees"
"check what tokens I'm a beneficiary for"
Fee Dashboard (CLI)
The Bankr CLI includes a dedicated fee dashboard that gives you a full picture of your historical earnings and projections:
bankr fees
The dashboard displays:
- Claimable and claimed WETH at a glance
- Daily earnings chart with bar graph and sparkline visualization
- Key statistics: total earned, daily average, best day, active days, and current streak
- Projected earnings: estimated monthly and yearly income based on your daily average
- Per-token breakdown: claimable and claimed amounts for each token you've deployed
You can customize the lookback period (1–90 days) and look up fees by token address:
bankr fees --days 7 # Last 7 days
bankr fees --token 0xTokenAddress # Fees for a specific token
bankr fees --json # Raw JSON for scripting
To claim directly from the CLI:
# Claim a single token (requires Bankr account)
bankr fees claim 0xTokenAddress
# Claim all fees for any wallet using your own private key (no Bankr account needed)
bankr fees claim-wallet
The claim-wallet command automatically reads BANKR_PRIVATE_KEY from a .env file in the current directory, derives your wallet address, scans all launches where you're a beneficiary, and lets you claim in bulk. It signs on Base only and skips launches on other chains — claim those from the web with your external wallet, or build them with POST /public/doppler/build-claim. See the CLI documentation for full details.
For Partners
If you're a Bankr partner deploying tokens via the Deploy API, your partner wallet accumulates a share of trading fees from every token launched through your integration. Use claim-wallet to claim fees across all your tokens in bulk:
# Set your partner wallet private key in .env
echo "BANKR_PRIVATE_KEY=0xYourPartnerWalletKey" > .env
# Scan all launches and claim fees
bankr fees claim-wallet --all --yes
This is the recommended way for partners to collect their fee share. It scans all launches where your wallet is a beneficiary (creator, partner, or any other role), shows claimable amounts, and submits claim transactions directly.
Troubleshooting
"No fees to claim"
- Your token may not have had recent trading activity
- Fees might have already been claimed
- Check if fees have accumulated:
"check my fees for TokenName"
"Not authorized to claim"
- You must be the current fee beneficiary for the token
- If you transferred beneficiary rights, the new beneficiary must claim
- Check who the current beneficiary is:
"who is the beneficiary for 0x1234...?" - To move beneficiary rights to a new wallet, see Transferring Fees to a New Wallet