Skip to main content

Token Launching Overview

Launch a token for your AI agent and earn trading fees automatically. This is how agents fund themselves.

Why Launch a Token?​

When you launch a token through Bankr:

  1. Liquidity pool is created — Your token is immediately tradeable
  2. Trading fees accumulate — Every trade generates fees
  3. Fees flow to you — Claim your earnings anytime
  4. Fund your compute — Use fees to pay for your agent's API costs
  5. Hold an allocation — 15% of supply vests to you over 1 year (30-day cliff)

Launching via Natural Language​

Simply tell Bankr what you want to deploy. Tokens deploy to Robinhood Chain by default — say on base to deploy on Base instead:

"deploy a token called MyAgent with symbol AGENT"
"launch a token called CoolBot"

Available via the Bankr Terminal, bankr agent, and social platforms.

Launching via Social (Built-in Virality)​

Deploy directly from X (Twitter) by tagging @bankrbot:

@bankrbot deploy a token called MyAgent

This creates instant social proof and discoverability for your token.

Launching via CLI​

The Bankr CLI provides an interactive wizard for token launches with full control over metadata and fee routing:

# Interactive wizard (recommended for first-time launches)
bankr launch

# Headless launch with all options
bankr launch --name "MyToken" \
  --image "https://example.com/logo.png" \
  --tweet "https://x.com/user/status/123" \
  --website "https://example.com" \
  --yes

# Launch on Robinhood Chain
bankr launch --name "MyToken" --chain robinhood --yes

# With fee recipient (route fees to collaborators)
bankr launch --name "MyToken" --fee "@partner" --fee-type x --yes

The CLI wizard prompts for:

  • Token name (required)
  • Image URL (optional)
  • Chain: Base or Robinhood Chain (defaults to Base)
  • Associated tweet for social proof (optional)
  • Project website (optional)
  • Fee recipient: X/Farcaster handle, ENS, or wallet address (optional)

All bankr launch commands deploy to Base unless --chain robinhood is passed, and display a summary before confirmation. Use --yes to skip confirmation in automated scripts.

Install the CLI:

npm install -g @bankr/cli

See the CLI documentation for full options and examples.

Launching with OpenClaw​

For AI agents using OpenClaw, the Token Strategist skill provides intelligent token planning and deployment:

install the skill from https://github.com/BankrBot/token-strategist

Token Strategist evaluates your concept against five market forces, sets up fee distribution, and executes launches through the Bankr CLI. This is ideal for agents that need to autonomously manage token economics and deployment strategy.

Learn more: Token Strategist on GitHub

Deployment Limits​

User TypeTokens Per Day
Standard50
Bankr Club100

The daily cap counts every attempt in the trailing 24h (including failed ones). You can also deploy at most one token per minute. Gas is sponsored for your first 3 deploys/day (Standard) or 10/day (Club); beyond that you pay your own gas up to the daily cap.

Wallet age requirement (anti-sybil)

Bankr can require your wallet to be at least 24 hours old — measured from when the wallet was created, not your X/social account age — before it may launch a token. When this gate is enabled, a deploy from a newer wallet is rejected with a message telling you roughly how many hours remain. This is an anti-sybil safeguard and is off by default; when it is in effect, partner (org Partner Key) launches are always exempt.

Spam detection

High-volume deploys in a short period can trigger Bankr's automated spam protections and result in temporary or permanent restrictions on your account. This is enforced hardest on the X (Twitter) path, where a mention can kick off a deploy: repeatedly breaching the one-per-minute limit will restrict your account for 24 hours — a limited state, not a lockout (you can still log in, view balances, and withdraw), you just have to wait for it to lift before launching again. Legitimate high-volume use cases (e.g. programmatic deploy products) may be accommodated — open a support ticket explaining your use case before scaling up.

Fee Structure​

Every trade pays a 0.7% swap fee on the pool — and 95% of it goes to you, the creator (0.665% of trading volume). On top of that, the hook adds the Bankr protocol fee + BNKR buyback and LP fee — including your token's own 0.285% LP fee, which automatically compounds as permanently locked liquidity in your pool, deepening your coin's liquidity floor with every trade. All-in, the total swap fee is 1.75% of trading volume:

RecipientShare of volume
Creator (you) — 95% of the 0.7% pool swap fee; paid directly, claim anytime0.665%
LP fee (via hook) — compounds as permanently locked liquidity in your pool0.285%
Bankr protocol fee (via hook)0.475%
BNKR buyback (via hook — BNKR buybacks + protocol-owned BNKR liquidity)0.2375%
Protocol (Doppler)~0.0875%

That's the 0.7% pool fee with 95% going to you, plus the hook-added Bankr protocol fee + BNKR buyback and LP fee — and since the LP fee compounds in your token's own pool, the creator side totals 0.95% of volume.

Fees accumulate in your token and WETH. Use the Terminal or bankr agent "claim my token fees" to collect your share.

Existing tokens are unaffected

Fee schedules are fixed at launch and never change retroactively. Tokens launched earlier keep the schedule they launched with — the creator's 95% of the 0.7% pool fee works the same; only the hook add-on differs. The split above applies to new launches only.

Token Supply​

Fixed supply of 100 billion tokens (not mintable after deployment), allocated at launch (default):

AllocationShareWhere it goes
Liquidity pool85%Seeded into the Uniswap V4 pool — immediately tradeable
Creator vesting15%Vested to the fee recipient over 1 year (30-day cliff)

Creator vesting​

By default, every Bankr launch premints 15% of supply to the fee recipient and vests it 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 liquidity pool, so trading starts clean.

  • Recipient — the fee recipient set at launch (your own wallet by default, or a third party you designate — the same address that earns the creator fee share).
  • Fixed at launch — the vesting recipient is locked when the token is created and can't be reassigned. Transferring your fee rights later does not move the vested allocation; it stays with the original recipient.
  • Optional — you can turn vesting off at launch. Ask the agent 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 supply is sold into the pool and no allocation is preminted. There is no custom percentage or schedule — vesting is either the default 15% or off.

Quote-only fees​

By default, creator fees accrue as a mix of the launched token and the quote token (e.g. WETH). At launch you can instead opt into quote-only fees, so all creator fees are collected in the quote token — your total take is identical either way. Ask the agent to "launch a token with quote-only fees", toggle it in the web launch form, pass quoteOnlyFees: true to the deploy API, or use --quote-only-fees in the CLI. Like the fee schedule itself, this option is fixed at launch.

Partner / org launches

Launches deployed with an org Partner Key sell the full 100% into the pool and do not include creator vesting.

End-to-end Flow​

Most integrations follow the same three-step lifecycle. Each step has a narrative guide and, for endpoints currently covered, an interactive "Try it" reference.

1. Deploy​

Launch a new token on Robinhood Chain or Base (default Robinhood Chain). Returns the token address and Uniswap V4 pool metadata. Pass "chain": "base" in the request body to deploy on Base — partner deploys remain Base-only.

  • Interactive reference: Deploy a token →
  • Endpoint: POST /token-launches/deploy
  • Auth: X-Partner-Key (org-level) or X-API-Key / Authorization: Bearer (wallet-level)
curl -X POST https://api.bankr.bot/token-launches/deploy \
  -H "Content-Type: application/json" \
  -H "X-Partner-Key: bk_ptr_YOUR_KEY" \
  -d '{ "tokenName": "MyToken", "tokenSymbol": "MTK", "feeRecipient": { "type": "wallet", "value": "0x…" } }'

2. Check fees​

Query claimable + claimed + historical fees for a token or beneficiary. Unauthenticated.

  • Interactive reference: Check fees →
  • Guide: Reading Creator Fees →
  • Per-token snapshot: GET /token-launches/:tokenAddress/fees?days=30
  • Per-wallet dashboard: GET /public/doppler/creator-fees/:walletAddress
  • Scan all beneficiary positions for a wallet: GET /public/doppler/beneficiary-fees/:walletAddress
curl "https://api.bankr.bot/token-launches/0xTokenAddress/fees?days=30"

3. Claim​

Collect your share of trading fees. One HTTP call — server auto-detects Doppler vs Clanker, builds the calldata, signs via Privy, and broadcasts.

curl -X POST https://api.bankr.bot/token-launches/0xTokenAddress/fees/claim \
  -H "Authorization: Bearer $BANKR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Response: { transactionHash, status, signer, chainId, description, blockNumber?, gasUsed? }.

External wallets (Safe multisig, hardware wallets, third-party signers) use the batch-capable public endpoint POST /public/doppler/build-claim — see Claiming Fees for the self-custody flow.

Discover Recent Launches​

List the 50 most recent Bankr token launches. Unauthenticated. Programmatic access to the data behind bankr.bot/launches.

curl https://api.bankr.bot/token-launches

Next Steps​