Token Launcher

Token Launcher

Launch tokens and keep your fees. Two paths, one goal: stop giving away 30-50% of your creator earnings to launch platforms.

The Problem

Most token launch platforms take 30-50% of your creator fee earnings. Some charge upfront launch fees on top of that. Others layer in subscriptions, required platform tokens, or custodial wallets that hold your funds. You build the token, drive the volume, and someone else keeps the biggest slice.

The Math

A token doing $500K in trading volume on Clanker generates ~$5,000 in pool fees (1% of volume). Here's who keeps what:

The difference compounds. At $5M volume, Direct Mode keeps you an extra $15,000-25,000 versus typical platforms. Easy Mode saves you $10,000-20,000.

Two Paths

Easy Mode — Tator API

One API call, natural language, Tator handles everything.

• Send a prompt like "launch a token called GATOR on base"
• Tator selects the platform, uploads metadata to IPFS, deploys the contract, configures fees
• Returns unsigned transactions — your wallet signs and broadcasts
• Fee split: 90% to you, 10% to Tator as interface fee
• $0.20 per API call via x402 USDC payment
• Supports launch, claim fees, update fee recipient, check unclaimed — all via natural language

Best for: Agents and developers who want token launches without writing blockchain code.

Direct Mode — Full SDK Integration

Call Clanker, Flaunch, or Pump.fun directly from your agent's code.

• Integrate the platform SDK or build instructions manually
• You control every parameter: rewards, sniper protection, pairing token, fee recipients
• 100% of creator fees — no interface cut, no middleman
• Requires: your own RPC endpoint, wallet signing capability, SDK dependencies

Best for: Agents and developers who want maximum control and zero fee overhead.

See REFERENCE.md for Direct Mode overview and the references/ folder for per-platform implementation guides.

Security

This skill is instruction-only — it contains no executable code. It provides documentation and code examples. No code is run at install time.

Credential Requirements

Easy Mode requires ZERO environment variables. It works with any x402-compatible wallet provider (Lobster, AgentWallet, Vincent, local signer). The Tator API only receives your public wallet address — your wallet provider handles payment signing separately. The skill never touches your private key.

Direct Mode requires environment variables because you are running SDK code in your own infrastructure:

If you only use Easy Mode, you do not need any of these. The skill installs and functions without any environment variables configured.

Easy Mode Data Flow

When you call the Tator x402 API (POST https://x402.quickintel.io/v1/tator/prompt):

1. Sent to Tator: walletAddress (public address — not sensitive), prompt (your instruction), provider (your agent name)
2. NOT sent to Tator: Your private key, seed phrase, or any signing material
3. x402 payment: Your wallet provider signs a USDC authorization locally → the signed payment header is sent with the request. The API verifies the signature on-chain — it never has your key
4. Returned to you: Unsigned transaction(s) — you sign locally and broadcast yourself

No private keys ever leave your machine in Easy Mode. The skill itself never has access to your private key — your wallet provider handles signing independently.

Direct Mode Data Flow

Direct Mode code runs entirely in your own infrastructure:

1. Sent to blockchain RPCs: Signed transactions (your RPC provider sees them — use a trusted provider like Alchemy, QuickNode, or Helius)
2. Sent to IPFS: Token metadata (name, symbol, description, image) — this is public by design
3. Sent to platform SDKs: Clanker SDK calls go to Clanker's infrastructure; Flaunch calls go to Base contracts; Pump.fun calls go to Solana
4. NOT sent anywhere: Your private key — it stays on your machine for local signing only

Key Management (Direct Mode Only)

• Use a dedicated launch wallet. Never your main wallet or a wallet holding significant funds
• Store keys in a secrets manager. AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, or equivalent. Never hardcode in source code. Never store in plaintext .env files in production
• Fund minimally. ~0.01 ETH on Base, ~0.05 SOL on Solana — just enough for gas
• Human-in-the-loop recommended. If your agent runs autonomously, require human approval before any transaction-signing operation. Do not give autonomous agents unsupervised access to signing keys
• Pump.fun bot wallet: Solana requires a bot wallet that signs directly (unlike EVM where unsigned transactions can be returned). This wallet needs SOL for gas but should never hold significant value. See references/pumpfun.md
• Revocation plan. Ensure you can abandon the launch wallet if compromised — use a fresh wallet you can walk away from

Privacy Note on SDK Context Fields

Some platform SDKs (like Clanker) accept an optional context object for analytics tracking. These fields are entirely optional. If you use them, be aware:

• context.interface — your agent/app name (sent to Clanker)
• context.platform — where the user is (e.g., "telegram") (sent to Clanker)
• context.messageId — message ID that triggered the launch (sent to Clanker)
• context.id — user identifier (sent to Clanker)

If privacy is a concern, omit the context object entirely or use non-identifying values. The context object is not required for any operation to succeed. See the Clanker reference for details.

Verify External Endpoints

Before using any endpoint, verify you're connecting to the correct service:

Easy Mode — Full Walkthrough

Prerequisites

• A wallet you control (EVM or Solana)
• USDC for x402 API payments ($0.20 per Tator call)
• Native token for gas (ETH on EVM chains, SOL on Solana)

Launch a Token

curl -X POST https://x402.quickintel.io/v1/tator/prompt \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <x402_payment>" \
  -d '{
    "prompt": "launch a token called Galaxy Cat with ticker GCAT on base",
    "walletAddress": "0xYourWallet",
    "provider": "my-agent"
  }'

With custom image:

{
  "prompt": "launch a token called Moon Dog with ticker MDOG on base with image https://example.com/dog.png",
  "walletAddress": "0xYourWallet",
  "provider": "my-agent"
}

On Solana:

{
  "prompt": "launch a token called Cyber Frog with ticker CYFR on solana via pump.fun",
  "walletAddress": "YourSolanaWallet",
  "provider": "my-agent"
}

With custom fee recipient (send fees to a different wallet):

{
  "prompt": "launch a token called DAO Token with ticker DAOT on base, send creator fees to 0xTreasuryAddress",
  "walletAddress": "0xYourWallet",
  "provider": "my-agent"
}

The response includes unsigned transaction(s) for your wallet to sign and broadcast. After confirmation, you'll get back the deployed token address, transaction hash, and fee configuration details.

Check Unclaimed Fees

{
  "prompt": "check my unclaimed fees for token 0xTokenAddress on base",
  "walletAddress": "0xYourWallet",
  "provider": "my-agent"
}

Claim Creator Fees

{
  "prompt": "claim my creator fees for token 0xTokenAddress on base",
  "walletAddress": "0xYourWallet",
  "provider": "my-agent"
}

For Pump.fun tokens that have graduated to Raydium, Tator automatically handles the two-step process (transfer WSOL from AMM vault → distribute SOL from pump vault).

Update Fee Recipient

{
  "prompt": "update the fee recipient for token 0xTokenAddress on base to 0xNewRecipientAddress",
  "walletAddress": "0xYourWallet",
  "provider": "my-agent"
}

Security Scan Post-Launch

Use Quick Intel ($0.03 per scan) to verify your deployed token looks clean:

{
  "chain": "base",
  "tokenAddress": "0xYourDeployedToken"
}

Call POST https://x402.quickintel.io/v1/scan/full to check for honeypot flags, tax irregularities, or anything that might spook potential buyers.

Discovery

Call GET https://x402.quickintel.io/accepted to get all supported payment networks, pricing, and input/output schemas for auto-configuration.

Platform Selection

When to Use What

Clanker — Your default for EVM launches. Widest chain support (7 chains), Uniswap V4 pools with built-in sniper protection, stable token pairing option. Best liquidity depth and DEX integration.

Flaunch — When you want a fair launch period on Base. The 30-minute fair launch window prevents snipers by design. Custom fee split manager gives you fine-grained control over fee distribution.

Pump.fun — For Solana launches. Bonding curve model means the token graduates to Raydium once it hits market cap threshold. Strong Solana ecosystem visibility — tokens show up in pump.fun's discovery feed.

Evaluating a Concept

Before deploying anything, figure out what you actually have. Not every idea needs a token, and not every token needs to launch today.

The Launch Stack

Every token that sustains attention beyond the first day has four layers working together. This isn't a scorecard — it's a diagnostic tool.

Layer 1: The Hook — The thing that makes someone stop scrolling. The name, the visual, the one-liner. Say the name out loud. Does it land instantly or need explanation? If it takes more than one sentence to explain why this exists, the hook isn't sharp enough. A mediocre name with great execution still underperforms a great name with decent execution.

Layer 2: The Engine — The reason fees keep flowing after launch day. Types of engines:

• Cultural engine: represents an ongoing cultural conversation
• Product engine: funds something people actually use
• Mechanic engine: built-in mechanics that create ongoing activity (burns, airdrops, staking)
• Social engine: tied to a person/community where the audience grows independently

If there's no engine, the token will spike on launch and bleed. That's fine if you understand it.

Layer 3: The Story — The narrative that justifies increasing price. Strong stories sound like "this token funds [specific thing] and every holder is backing it." Weak stories sound like "it's a community token" (what community? why this token?). If there's no answer to "why would someone who discovers this in 3 months want to buy it?" — the story needs work.

Layer 4: The Moat — What makes this token hard to replicate. First-mover on a narrative, builder credibility, integrated product, community lock-in, or technical integration. If there's no moat, launch fast — speed itself is a moat.

Search Before You Judge

Never evaluate a concept in a vacuum. Before giving your take, search for:

• Existing tokens with similar names, tickers, or narratives
• Cultural context — is this riding a real wave or manufacturing one?
• Comparable launches — what worked, what flopped, and why?
• The builder's blind spots — the most valuable thing you can offer is information they haven't considered

⚠️ Before You Launch: Tax & Legal Reality Check

Token deployment is irreversible. Creator fees are income. Most platforms skip this section entirely.

When This Matters Most

Launching a meme token for fun? The tax implications exist but are relatively straightforward — mostly capital gains if and when you sell.

But the moment your token becomes "more than just a meme" — meaning you plan to earn ongoing creator fees, build a product funded by fee income, use fee income to pay for development, or launch tokens regularly — that's when the tax and legal implications get serious, and you need professional guidance before you launch. Not after. Before.

What Every Builder Should Know

This is general information, not tax or legal advice. Tax treatment varies by jurisdiction. Consult a qualified professional.

• Creator fee income is likely taxable income — In most jurisdictions, ongoing fees are treated as income, not capital gains. Higher tax rates and potentially self-employment tax.
• Every transaction can be a taxable event — Selling tokens, swapping, receiving fee payments, distributing airdrops — each can trigger tax obligations.
• You owe taxes when you receive income, not when you cash out — If you earn $50K in creator fees and reinvest it all, then the token crashes, you likely still owe taxes on the $50K.
• Record-keeping starts at launch — Track: token creation date, every fee payment received (with fiat value at time of receipt), every sale or swap, gas fees paid.
• Regulatory enforcement is increasing globally — Governments are investing in blockchain analytics and expanding reporting requirements.

Jurisdiction Overview

🇺🇸 United States — Digital assets treated as property (IRS Notice 2014-21). Creator fee income likely ordinary income, possibly self-employment income. Starting 2025: Form 1099-DA reporting, wallet-by-wallet cost basis.

🇬🇧 United Kingdom — HMRC treats crypto as property. Income from token fees is income tax. CGT allowance currently £3,000.

🇩🇪 Germany — Crypto held over 1 year is tax-free on disposal for individuals. Under 1 year: income tax rates up to 45%. Fee income may be treated differently.

🇦🇺 Australia — ATO treats crypto as property. 50% CGT discount available for holdings over 12 months. Fee income assessable at fair market value when received.

🇸🇬 Singapore — No capital gains tax for individuals (current rules). Business income from token activities may be taxable.

🇦🇪 UAE — Currently no federal income tax on individuals. Regulatory framework developing under VARA.

🇨🇦 Canada — CRA treats crypto as a commodity. 50% capital gains inclusion rate. Business income from regular token activities fully taxable.

The pattern: creator fee income is almost universally taxable. Capital gains treatment varies. Long-term holding is often rewarded. Enforcement is increasing everywhere.

⛔ Mandatory Confirmation Before Launch

Before executing any token deployment, the builder MUST explicitly confirm they understand the following. Do not proceed without this confirmation.

BEFORE WE DEPLOY — Please confirm you understand:

1. TOKEN DEPLOYMENT IS IRREVERSIBLE
   Once deployed, the token exists permanently on-chain.

2. CREATOR FEES ARE INCOME
   Fee income from your token is likely taxable in your jurisdiction.
   Consult a tax professional if you plan to earn meaningful revenue.

3. RECORD-KEEPING IS YOUR RESPONSIBILITY
   Track all fee income, transactions, and fiat values from day one.

4. SET ASIDE FUNDS FOR TAXES
   Do not reinvest 100% of fee income. Reserve 30-40% for potential
   tax obligations (varies by jurisdiction).

5. NO GUARANTEED RETURNS
   Most tokens lose value. Creator fees depend on trading volume.

6. THIS IS NOT TAX OR LEGAL ADVICE
   This skill provides tools, not counsel.

Do you confirm you understand these points and want to proceed?

Do not deploy until the builder explicitly confirms. This is non-negotiable.

Pre-Launch Checklist

• Launch Stack evaluated — hook is sharp, engine identified, story holds, moat considered
• Name and narrative locked
• Platform and chain chosen (Clanker / Flaunch / Pump.fun)
• Wallet ready with native token for gas
• Fee recipient confirmed (your wallet or custom address)
• Image/branding prepared
• Mandatory tax/legal confirmation received
• Security scan planned for post-deployment

Post-Launch

1. Run a Quick Intel scan — Verify the deployed token looks clean externally before promoting
2. Monitor fee accumulation — Check unclaimed fees regularly
3. Claim on a cadence — Periodic claims rather than letting fees pile up (better for tax tracking, reduces exposure)
4. Watch reinvestment risk — If putting all fees back into trading, remember: taxes are owed on the income regardless
5. Revisit the Launch Stack — If volume drops, diagnose which layer is failing

File Structure

What This Skill Is NOT

• Not tax advice. General information provided for awareness. Consult a professional.
• Not legal advice. Token launches may have securities law implications.
• Not a guarantee of profits. Most tokens lose value.
• Not a "get rich quick" tool. This skill helps builders launch responsibly and keep more of what they earn.