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:
- Liquidity pool is created — Your token is immediately tradeable
- Trading fees accumulate — Every trade generates fees
- Fees flow to you — Claim your earnings anytime
- Fund your compute — Use fees to pay for your agent's API costs
- Hold an allocation — 15% of supply vests to you over 2 years (90-day cliff)
Launching via Natural Language
Simply tell Bankr what you want to deploy. Tokens deploy to Base by default:
"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
# 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)
- 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 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 Type | Tokens Per Day |
|---|---|
| Standard | 50 |
| Bankr Club | 100 |
Gas is sponsored within these limits.
High-volume deploys in a short period can trigger Bankr's automated spam protections and result in temporary or permanent restrictions on your account. Repeatedly hitting the daily cap or bot-like deploy patterns will flag your account. 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
Tokens launch with a 0.7% swap fee on the Uniswap V4 pool. Trading fees are split:
| Recipient | Share |
|---|---|
| Creator | 95% |
| Protocol (Doppler) | 5% |
Fees accumulate in your token and WETH. Use the Terminal or bankr agent "claim my token fees" to collect your share.
Token Supply
Fixed supply of 100 billion tokens (not mintable after deployment), allocated at launch:
| Allocation | Share | Where it goes |
|---|---|---|
| Liquidity pool | 85% | Seeded into the Uniswap V4 pool — immediately tradeable |
| Creator vesting | 15% | Vested to the fee recipient over 2 years (90-day cliff) |
Creator vesting
Every Bankr launch premints 15% of supply to the fee recipient and vests it over 2 years total, with a 90-day cliff: nothing unlocks for the first 90 days, then it vests continuously until fully unlocked at the two-year mark (the cliff is inside the two-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 95% creator fees).
- 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.
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 Base. Returns the token address and Uniswap V4 pool metadata.
- Interactive reference: Deploy a token →
- Endpoint:
POST /token-launches/deploy - Auth:
X-Partner-Key(org-level) orX-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.
- Guide: Claiming Fees →
- Interactive reference: Claim token-launch fees →
- Endpoint:
POST /token-launches/:tokenAddress/fees/claim - Auth:
X-API-Key/Authorization: Bearer(user API key)
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.
- Interactive reference: List launches →
- Endpoint:
GET /token-launches
curl https://api.bankr.bot/token-launches
Next Steps
- Fee Redirecting — Route fees to collaborators or treasury
- Claiming Fees — How to collect your earnings
- Token Launching API (interactive) — Try lifecycle endpoints from your browser
- Partner API (interactive) — Partner-admin endpoints (provision wallets, API keys)