How Do I Launch a Token?

Deploying a token for your agent allows you to earn trading fees automatically. Tokens launched through Bankr use fair launch mechanics via the Doppler protocol. Launches deploy to Robinhood Chain by default; add on base to your request to deploy on Base instead.

Ways to Launch

There are three main ways to launch a token:

In the Chat: Simply tell Bankr what you want to do. For example: "launch a token called FROG" (deploys on Robinhood Chain) or "deploy a token named MYAGENT with the ticker MAGNT on base".
Via the CLI: Use the Bankr CLI for an interactive wizard that gives you more control over metadata and fee routing: bankr launch. You can also run headless launches with all options specified. The CLI deploys to Base unless you pass --chain robinhood.
On X (Twitter): You can launch a token by tagging @bankrbot with your launch request.

Token Strategist Skill

For agents that need to autonomously manage token economics and deployment strategy, you can install the Token Strategist skill. It evaluates your concept, sets up fee distribution, and executes launches through the Bankr CLI.

To install it, ask Bankr: install the skill from https://github.com/BankrBot/token-strategist

Daily Limits

To ensure network stability, there are daily deployment limits:

Standard/Wallet-level deployments: Up to 50 tokens per day (Standard) or 100 per day (Bankr Club). The daily cap counts every attempt in the trailing 24 hours — including failed ones — and you can deploy at most one token per minute.
Partner Organizations: Deployment limits are governed by your organization-specific rate limits, not the per-account daily cap.

Gas sponsorship: Bankr sponsors gas for your first 3 deploys per day (Standard) or 10 per day (Bankr Club). Beyond that, you pay your own gas, up to the daily cap.

Wallet age: as an anti-sybil safeguard, Bankr can require your wallet to be at least 24 hours old (measured from wallet creation, not your X/social account age) before it will launch a token. When this gate is on, a deploy from a newer wallet is rejected with a message showing roughly how many hours remain. It is off by default, and partner (org Partner-Key) launches are always exempt.

Token Supply and Creator Allocation

Every Bankr launch has a fixed supply of 100 billion tokens (not mintable after deployment). By default, 15% of supply is preminted to your fee recipient wallet as an automatic creator allocation, vesting over 1 year total with a 30-day cliff: nothing unlocks for the first 30 days, then it vests continuously until fully unlocked at the one-year mark (the cliff is inside the one-year window, not added to it). The remaining 85% seeds the Uniswap V4 pool, so trading starts clean.

Vesting is optional. You can turn it off at launch — ask Bankr to deploy "with no vesting", pick No vesting in the web launch flow's Vesting step, or pass disableVesting: true to the deploy API (--no-vesting in the CLI). With vesting off, 100% of the supply is sold into the pool and no creator allocation is preminted. There is no custom percentage or schedule — vesting is either the default 15% or off. Partner/org launches never vest.

Degen Mode

Degen mode starts your token at a $2,500 starting market cap — much lower than the standard start — for maximum early volatility. It is off by default and has to be requested explicitly — naming your token DEGEN, or generic "make it risky" language, will not turn it on.

Three ways to enable it:

In the chat: "launch a token called FROG in degen mode"
In the web launch flow: flip the Degen mode toggle in the launch panel.
Via the deploy API: pass degenMode: true.

The degen starting market cap is fixed at $2,500 — there is no custom value to set, and it can't be changed after deployment. Nothing else about the launch changes: same supply, same fee structure, same vesting default. Degen mode is not available for partner/org launches (those requests are rejected), and the CLI's bankr launch does not expose it yet.

Stock-Paired Token Launches

You can pair your launch with a tokenized stock instead of WETH, so the pool is quoted in that stock (for example TSLA, AAPL, or NVDA). This is supported on two chains:

Robinhood Chain — Robinhood-issued tokenized stocks and ETFs.
Base — the Coinbase-issued B20 tokenized equities (AAPL, TSLA, NVDA, and more).

Name the stock when you launch:

"launch a token called MyToken paired with TSLA"
"launch it against AAPL stock"
"launch MyToken on base paired with NVDA"

The stock has to live on the chain you're launching on — the two registries are entirely separate contracts, even where the tickers match, so a Base launch pairs with the B20 equity and a Robinhood Chain launch pairs with the Robinhood one. You must also have passed the tokenized-stock location check (a one-time login at bankr.bot). Stock pairing isn't available for partner/org launches.

Thin liquidity is a warning, not a block. Before deploying, Bankr measures the paired stock's on-chain pool depth and flags it if it's below roughly $10K in liquidity — too thin to trade comfortably. The launch still goes ahead — but a pool quoted in an illiquid stock is hard for your traders to get in and out of. The Base B20 equities are newer contracts, so many still have thin pools; check the liquidity badge in the launch wizard before committing.

Trading fees on a stock-paired pool accrue in your token and in the paired stock rather than WETH. Bankr values that stock leg using the stock's live price, so your earnings and trading volume appear in the same fee dashboards and lifetime stats as a WETH-paired launch — no separate accounting on your side.

Fee Structure

Every trade on your token's pool pays a 0.7% swap fee — and 95% of it goes to you, claimable anytime. On top of the pool fee, the hook adds the Bankr protocol fee, a BNKR buyback, and an LP fee that compounds as permanently locked liquidity in your token's own pool — 1.75% all-in. The full current breakdown is in the Token Launching FAQ.

Fee schedules are fixed at launch — tokens launched before the current structure keep the schedule they launched with. Partners with custom arrangements can have exact allocations across additional beneficiaries; fee distribution for your organization is returned in every deploy response.

Fees accumulate in your token and in the pool's pairing asset — WETH by default, or the tokenized stock if you launched stock-paired — funding the "Self-Funding Loop" for your agent's LLM compute costs via the LLM Gateway.

Anti-Snipe Launch Fee

At the moment of launch, the swap fee starts at 80% and decays to the normal trading fee over roughly 10 seconds. This is intentional — it protects fair launches from snipers. Anyone buying inside that window pays the elevated fee, which is collected as the Bankr platform fee and is not recoverable.

If you're buying a fresh launch, wait at least 10–15 seconds after deployment before buying. If you're the creator, warn your community about the window too.

Managing Your Token

Checking and Claiming Fees

You can check your earnings at any time by asking Bankr:

"check my fees for TokenName"
"how much fees have I earned from 0x1234...?"
"show all my tokens with unclaimed fees"

To claim your share of the fees:

Ask Bankr: "claim my fees for TokenName"
Or click Claim in the Tokens section of the terminal sidebar.
Or navigate to the token detail page at /launches/<tokenAddress> and click Claim Fees.

Only the current fee beneficiary can claim fees. By default, this is the deployer wallet.

Transferring Fees to a New Wallet

If you need to redirect fees on an existing token (e.g., migrating to a multisig), the current beneficiary must call updateBeneficiary(poolId, newBeneficiary) on the Fees Manager contract on-chain.

Glidepaths

A Glidepath allows you to commit a portion of your tokens to be sold gradually as the market cap grows. This provides transparent treasury liquidity without causing market shocks. See How Do I Use Glidepath? for the full flow.

Important Limitations

Metadata: Doppler-launched tokens (the current launcher) cannot have their image or description updated after launch. Older Clanker-launched tokens can — ask Bankr to update it with a valid image URL. Not sure which launcher your token used? Ask: Show me my token launches.
Vested Allocation: If you launch with vesting, the recipient of the 15% Vested Allocation can not be modified after launch.
Degen mode: The $2,500 starting market cap is set at deployment and cannot be changed afterwards.

Troubleshooting

"No fees to claim" — Your token may not have had recent trading activity, or fees might have already been claimed.
"Not authorized to claim" — Only the current fee beneficiary wallet can claim.
"Degen mode is not supported for partner token launches" — Partner/org deploys use a separate launch configuration. Drop degenMode from the request, or launch from a standard wallet.
Deployments consistently failing — This can be caused by IPFS storage limits being exceeded on the platform side (which fails all deployments). Workaround: host your token image externally (Imgur, Cloudinary, your own server) and pass that direct URL during deployment instead of uploading via IPFS.
Token not showing in 'Your Tokens' — A known issue for some Doppler-launched tokens; the token and fees still exist on-chain. Open a ticket at the Bankr Help Center and the team can verify.

For technical specifications and API documentation, visit docs.bankr.bot.