{ "schemaVersion": "1.0", "item": { "slug": "tator-launch-pad", "name": "Token Launcher - Tator Launch Pad", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/azep-ninja/tator-launch-pad", "canonicalUrl": "https://clawhub.ai/azep-ninja/tator-launch-pad", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/tator-launch-pad", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=tator-launch-pad", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "REFERENCE.md", "SKILL.md", "references/clanker.md", "references/flaunch.md", "references/pumpfun.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-07T17:22:31.273Z", "expiresAt": "2026-05-14T17:22:31.273Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentDisposition": "attachment; filename=\"afrexai-annual-report-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/tator-launch-pad" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/tator-launch-pad", "agentPageUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent", "manifestUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent.json", "briefUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Token Launcher", "body": "Launch tokens and keep your fees. Two paths, one goal: stop giving away 30-50% of your creator earnings to launch platforms." }, { "title": "The Problem", "body": "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." }, { "title": "The Math", "body": "A token doing $500K in trading volume on Clanker generates ~$5,000 in pool fees (1% of volume). Here's who keeps what:\n\nPathYour SharePlatform CutYou KeepDirect Mode (this skill)$5,000$0$5,000 (100%)Easy Mode (Tator API)$4,500$500 (10%)$4,500 (90%)Typical launch platforms$2,500-3,500$1,500-2,500 (30-50%)$2,500-3,500\n\nThe 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." }, { "title": "Easy Mode — Tator API", "body": "One API call, natural language, Tator handles everything.\n\nSend a prompt like \"launch a token called GATOR on base\"\nTator selects the platform, uploads metadata to IPFS, deploys the contract, configures fees\nReturns unsigned transactions — your wallet signs and broadcasts\nFee split: 90% to you, 10% to Tator as interface fee\n$0.20 per API call via x402 USDC payment\nSupports launch, claim fees, update fee recipient, check unclaimed — all via natural language\n\nBest for: Agents and developers who want token launches without writing blockchain code." }, { "title": "Direct Mode — Full SDK Integration", "body": "Call Clanker, Flaunch, or Pump.fun directly from your agent's code.\n\nIntegrate the platform SDK or build instructions manually\nYou control every parameter: rewards, sniper protection, pairing token, fee recipients\n100% of creator fees — no interface cut, no middleman\nRequires: your own RPC endpoint, wallet signing capability, SDK dependencies\n\nBest for: Agents and developers who want maximum control and zero fee overhead.\n\nSee REFERENCE.md for Direct Mode overview and the references/ folder for per-platform implementation guides." }, { "title": "Security", "body": "This skill is instruction-only — it contains no executable code. It provides documentation and code examples. No code is run at install time." }, { "title": "Credential Requirements", "body": "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.\n\nDirect Mode requires environment variables because you are running SDK code in your own infrastructure:\n\nVariableRequired ForSensitiveHow to StoreWALLET_PRIVATE_KEYSigning deploy/claim/update transactionsYes — grants full wallet controlSecrets manager (AWS SM, GCP SM, Vault). Never plaintext.RPC_URLTalking to the blockchainNo (but keep private to avoid rate limit abuse)Environment variable or configSOLANA_RPC_URLSolana operations (Pump.fun only)NoEnvironment variable or configPINATA_API_KEY or IPFS_API_KEYUploading token metadata to IPFSYesSecrets manager\n\nIf you only use Easy Mode, you do not need any of these. The skill installs and functions without any environment variables configured." }, { "title": "Easy Mode Data Flow", "body": "When you call the Tator x402 API (POST https://x402.quickintel.io/v1/tator/prompt):\n\nSent to Tator: walletAddress (public address — not sensitive), prompt (your instruction), provider (your agent name)\nNOT sent to Tator: Your private key, seed phrase, or any signing material\nx402 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\nReturned to you: Unsigned transaction(s) — you sign locally and broadcast yourself\n\nNo 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." }, { "title": "Direct Mode Data Flow", "body": "Direct Mode code runs entirely in your own infrastructure:\n\nSent to blockchain RPCs: Signed transactions (your RPC provider sees them — use a trusted provider like Alchemy, QuickNode, or Helius)\nSent to IPFS: Token metadata (name, symbol, description, image) — this is public by design\nSent to platform SDKs: Clanker SDK calls go to Clanker's infrastructure; Flaunch calls go to Base contracts; Pump.fun calls go to Solana\nNOT sent anywhere: Your private key — it stays on your machine for local signing only" }, { "title": "Key Management (Direct Mode Only)", "body": "Use a dedicated launch wallet. Never your main wallet or a wallet holding significant funds\nStore 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\nFund minimally. ~0.01 ETH on Base, ~0.05 SOL on Solana — just enough for gas\nHuman-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\nPump.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\nRevocation plan. Ensure you can abandon the launch wallet if compromised — use a fresh wallet you can walk away from" }, { "title": "Privacy Note on SDK Context Fields", "body": "Some platform SDKs (like Clanker) accept an optional context object for analytics tracking. These fields are entirely optional. If you use them, be aware:\n\ncontext.interface — your agent/app name (sent to Clanker)\ncontext.platform — where the user is (e.g., \"telegram\") (sent to Clanker)\ncontext.messageId — message ID that triggered the launch (sent to Clanker)\ncontext.id — user identifier (sent to Clanker)\n\nIf 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." }, { "title": "Verify External Endpoints", "body": "Before using any endpoint, verify you're connecting to the correct service:\n\nServiceOfficial EndpointVerify ViaTator x402 APIhttps://x402.quickintel.ioCheck TLS cert, call GET /acceptedQuick Intel Scanhttps://x402.quickintel.io/v1/scan/fullSame gatewayClanker SDKVia npm clanker-sdkVerify package on npmjs.comFlaunch contractsOn-chain on BaseVerify on BasescanPump.fun programOn-chain on SolanaVerify on Solscan — program ID: 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P" }, { "title": "Prerequisites", "body": "A wallet you control (EVM or Solana)\nUSDC for x402 API payments ($0.20 per Tator call)\nNative token for gas (ETH on EVM chains, SOL on Solana)" }, { "title": "Launch a Token", "body": "curl -X POST https://x402.quickintel.io/v1/tator/prompt \\\n -H \"Content-Type: application/json\" \\\n -H \"PAYMENT-SIGNATURE: \" \\\n -d '{\n \"prompt\": \"launch a token called Galaxy Cat with ticker GCAT on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n }'\n\nWith custom image:\n\n{\n \"prompt\": \"launch a token called Moon Dog with ticker MDOG on base with image https://example.com/dog.png\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\nOn Solana:\n\n{\n \"prompt\": \"launch a token called Cyber Frog with ticker CYFR on solana via pump.fun\",\n \"walletAddress\": \"YourSolanaWallet\",\n \"provider\": \"my-agent\"\n}\n\nWith custom fee recipient (send fees to a different wallet):\n\n{\n \"prompt\": \"launch a token called DAO Token with ticker DAOT on base, send creator fees to 0xTreasuryAddress\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\nThe 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." }, { "title": "Check Unclaimed Fees", "body": "{\n \"prompt\": \"check my unclaimed fees for token 0xTokenAddress on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}" }, { "title": "Claim Creator Fees", "body": "{\n \"prompt\": \"claim my creator fees for token 0xTokenAddress on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\nFor 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)." }, { "title": "Update Fee Recipient", "body": "{\n \"prompt\": \"update the fee recipient for token 0xTokenAddress on base to 0xNewRecipientAddress\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}" }, { "title": "Security Scan Post-Launch", "body": "Use Quick Intel ($0.03 per scan) to verify your deployed token looks clean:\n\n{\n \"chain\": \"base\",\n \"tokenAddress\": \"0xYourDeployedToken\"\n}\n\nCall POST https://x402.quickintel.io/v1/scan/full to check for honeypot flags, tax irregularities, or anything that might spook potential buyers." }, { "title": "Discovery", "body": "Call GET https://x402.quickintel.io/accepted to get all supported payment networks, pricing, and input/output schemas for auto-configuration." }, { "title": "Platform Selection", "body": "FeatureClankerFlaunchPump.funChainsBase, Arbitrum, Mainnet, Unichain, Abstract, Monad, BSCBaseSolanaPool typeUniswap V4Bonding curve → UniswapBonding curve → RaydiumSwap fee1.2% (1% pool + 0.2% protocol)ConfigurableVariable (pre/post graduation)Creator fee shareConfigurable via reward recipientsConfigurable via fee split managerConfigurable via sharing configPairing tokenWETH default, USDC/USDT availableETHSOLSniper protectionYes (decaying fee — 66.7% → 4.2% over 15s)Fair launch period (default 30 min)Bonding curve mechanicsGraduationN/A (immediate Uniswap pool)N/AYes (graduates to Raydium at threshold)Token standardERC-20ERC-20SPL (Token-2022)Supply1 billion (fixed)100 billion (configurable)Standard pump.fun supplyCreation feeFreeFreeMinimal SOL for rent" }, { "title": "When to Use What", "body": "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.\n\nFlaunch — 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.\n\nPump.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." }, { "title": "Evaluating a Concept", "body": "Before deploying anything, figure out what you actually have. Not every idea needs a token, and not every token needs to launch today." }, { "title": "The Launch Stack", "body": "Every token that sustains attention beyond the first day has four layers working together. This isn't a scorecard — it's a diagnostic tool.\n\nLayer 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.\n\nLayer 2: The Engine — The reason fees keep flowing after launch day. Types of engines:\n\nCultural engine: represents an ongoing cultural conversation\nProduct engine: funds something people actually use\nMechanic engine: built-in mechanics that create ongoing activity (burns, airdrops, staking)\nSocial engine: tied to a person/community where the audience grows independently\n\nIf there's no engine, the token will spike on launch and bleed. That's fine if you understand it.\n\nLayer 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.\n\nLayer 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." }, { "title": "Search Before You Judge", "body": "Never evaluate a concept in a vacuum. Before giving your take, search for:\n\nExisting tokens with similar names, tickers, or narratives\nCultural context — is this riding a real wave or manufacturing one?\nComparable launches — what worked, what flopped, and why?\nThe builder's blind spots — the most valuable thing you can offer is information they haven't considered" }, { "title": "⚠️ Before You Launch: Tax & Legal Reality Check", "body": "Token deployment is irreversible. Creator fees are income. Most platforms skip this section entirely." }, { "title": "When This Matters Most", "body": "Launching a meme token for fun? The tax implications exist but are relatively straightforward — mostly capital gains if and when you sell.\n\nBut 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." }, { "title": "What Every Builder Should Know", "body": "This is general information, not tax or legal advice. Tax treatment varies by jurisdiction. Consult a qualified professional.\n\nCreator 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.\nEvery transaction can be a taxable event — Selling tokens, swapping, receiving fee payments, distributing airdrops — each can trigger tax obligations.\nYou 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.\nRecord-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.\nRegulatory enforcement is increasing globally — Governments are investing in blockchain analytics and expanding reporting requirements." }, { "title": "Jurisdiction Overview", "body": "🇺🇸 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.\n\n🇬🇧 United Kingdom — HMRC treats crypto as property. Income from token fees is income tax. CGT allowance currently £3,000.\n\n🇩🇪 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.\n\n🇦🇺 Australia — ATO treats crypto as property. 50% CGT discount available for holdings over 12 months. Fee income assessable at fair market value when received.\n\n🇸🇬 Singapore — No capital gains tax for individuals (current rules). Business income from token activities may be taxable.\n\n🇦🇪 UAE — Currently no federal income tax on individuals. Regulatory framework developing under VARA.\n\n🇨🇦 Canada — CRA treats crypto as a commodity. 50% capital gains inclusion rate. Business income from regular token activities fully taxable.\n\nThe pattern: creator fee income is almost universally taxable. Capital gains treatment varies. Long-term holding is often rewarded. Enforcement is increasing everywhere." }, { "title": "⛔ Mandatory Confirmation Before Launch", "body": "Before executing any token deployment, the builder MUST explicitly confirm they understand the following. Do not proceed without this confirmation.\n\nBEFORE WE DEPLOY — Please confirm you understand:\n\n1. TOKEN DEPLOYMENT IS IRREVERSIBLE\n Once deployed, the token exists permanently on-chain.\n\n2. CREATOR FEES ARE INCOME\n Fee income from your token is likely taxable in your jurisdiction.\n Consult a tax professional if you plan to earn meaningful revenue.\n\n3. RECORD-KEEPING IS YOUR RESPONSIBILITY\n Track all fee income, transactions, and fiat values from day one.\n\n4. SET ASIDE FUNDS FOR TAXES\n Do not reinvest 100% of fee income. Reserve 30-40% for potential\n tax obligations (varies by jurisdiction).\n\n5. NO GUARANTEED RETURNS\n Most tokens lose value. Creator fees depend on trading volume.\n\n6. THIS IS NOT TAX OR LEGAL ADVICE\n This skill provides tools, not counsel.\n\nDo you confirm you understand these points and want to proceed?\n\nDo not deploy until the builder explicitly confirms. This is non-negotiable." }, { "title": "Pre-Launch Checklist", "body": "Launch Stack evaluated — hook is sharp, engine identified, story holds, moat considered\n Name and narrative locked\n Platform and chain chosen (Clanker / Flaunch / Pump.fun)\n Wallet ready with native token for gas\n Fee recipient confirmed (your wallet or custom address)\n Image/branding prepared\n Mandatory tax/legal confirmation received\n Security scan planned for post-deployment" }, { "title": "Post-Launch", "body": "Run a Quick Intel scan — Verify the deployed token looks clean externally before promoting\nMonitor fee accumulation — Check unclaimed fees regularly\nClaim on a cadence — Periodic claims rather than letting fees pile up (better for tax tracking, reduces exposure)\nWatch reinvestment risk — If putting all fees back into trading, remember: taxes are owed on the income regardless\nRevisit the Launch Stack — If volume drops, diagnose which layer is failing" }, { "title": "File Structure", "body": "FileWhat's InsideSKILL.md (this file)Strategy, Easy Mode walkthrough, platform selection, tax/legalREFERENCE.mdDirect Mode overview, fee economics deep dive, shared patternsreferences/clanker.mdClanker v4 SDK — launch, claim, update recipient, sniper configreferences/flaunch.mdFlaunch — launch, fee split manager, claim, transfer sharereferences/pumpfun.mdPump.fun — manual instructions, fee sharing, graduation handling" }, { "title": "What This Skill Is NOT", "body": "Not tax advice. General information provided for awareness. Consult a professional.\nNot legal advice. Token launches may have securities law implications.\nNot a guarantee of profits. Most tokens lose value.\nNot a \"get rich quick\" tool. This skill helps builders launch responsibly and keep more of what they earn." } ], "body": "Token Launcher\n\nLaunch tokens and keep your fees. Two paths, one goal: stop giving away 30-50% of your creator earnings to launch platforms.\n\nThe Problem\n\nMost 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.\n\nThe Math\n\nA token doing $500K in trading volume on Clanker generates ~$5,000 in pool fees (1% of volume). Here's who keeps what:\n\nPath\tYour Share\tPlatform Cut\tYou Keep\nDirect Mode (this skill)\t$5,000\t$0\t$5,000 (100%)\nEasy Mode (Tator API)\t$4,500\t$500 (10%)\t$4,500 (90%)\nTypical launch platforms\t$2,500-3,500\t$1,500-2,500 (30-50%)\t$2,500-3,500\n\nThe 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.\n\nTwo Paths\nEasy Mode — Tator API\n\nOne API call, natural language, Tator handles everything.\n\nSend a prompt like \"launch a token called GATOR on base\"\nTator selects the platform, uploads metadata to IPFS, deploys the contract, configures fees\nReturns unsigned transactions — your wallet signs and broadcasts\nFee split: 90% to you, 10% to Tator as interface fee\n$0.20 per API call via x402 USDC payment\nSupports launch, claim fees, update fee recipient, check unclaimed — all via natural language\n\nBest for: Agents and developers who want token launches without writing blockchain code.\n\nDirect Mode — Full SDK Integration\n\nCall Clanker, Flaunch, or Pump.fun directly from your agent's code.\n\nIntegrate the platform SDK or build instructions manually\nYou control every parameter: rewards, sniper protection, pairing token, fee recipients\n100% of creator fees — no interface cut, no middleman\nRequires: your own RPC endpoint, wallet signing capability, SDK dependencies\n\nBest for: Agents and developers who want maximum control and zero fee overhead.\n\nSee REFERENCE.md for Direct Mode overview and the references/ folder for per-platform implementation guides.\n\nSecurity\n\nThis skill is instruction-only — it contains no executable code. It provides documentation and code examples. No code is run at install time.\n\nCredential Requirements\n\nEasy 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.\n\nDirect Mode requires environment variables because you are running SDK code in your own infrastructure:\n\nVariable\tRequired For\tSensitive\tHow to Store\nWALLET_PRIVATE_KEY\tSigning deploy/claim/update transactions\tYes — grants full wallet control\tSecrets manager (AWS SM, GCP SM, Vault). Never plaintext.\nRPC_URL\tTalking to the blockchain\tNo (but keep private to avoid rate limit abuse)\tEnvironment variable or config\nSOLANA_RPC_URL\tSolana operations (Pump.fun only)\tNo\tEnvironment variable or config\nPINATA_API_KEY or IPFS_API_KEY\tUploading token metadata to IPFS\tYes\tSecrets manager\n\nIf you only use Easy Mode, you do not need any of these. The skill installs and functions without any environment variables configured.\n\nEasy Mode Data Flow\n\nWhen you call the Tator x402 API (POST https://x402.quickintel.io/v1/tator/prompt):\n\nSent to Tator: walletAddress (public address — not sensitive), prompt (your instruction), provider (your agent name)\nNOT sent to Tator: Your private key, seed phrase, or any signing material\nx402 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\nReturned to you: Unsigned transaction(s) — you sign locally and broadcast yourself\n\nNo 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.\n\nDirect Mode Data Flow\n\nDirect Mode code runs entirely in your own infrastructure:\n\nSent to blockchain RPCs: Signed transactions (your RPC provider sees them — use a trusted provider like Alchemy, QuickNode, or Helius)\nSent to IPFS: Token metadata (name, symbol, description, image) — this is public by design\nSent to platform SDKs: Clanker SDK calls go to Clanker's infrastructure; Flaunch calls go to Base contracts; Pump.fun calls go to Solana\nNOT sent anywhere: Your private key — it stays on your machine for local signing only\nKey Management (Direct Mode Only)\nUse a dedicated launch wallet. Never your main wallet or a wallet holding significant funds\nStore 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\nFund minimally. ~0.01 ETH on Base, ~0.05 SOL on Solana — just enough for gas\nHuman-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\nPump.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\nRevocation plan. Ensure you can abandon the launch wallet if compromised — use a fresh wallet you can walk away from\nPrivacy Note on SDK Context Fields\n\nSome platform SDKs (like Clanker) accept an optional context object for analytics tracking. These fields are entirely optional. If you use them, be aware:\n\ncontext.interface — your agent/app name (sent to Clanker)\ncontext.platform — where the user is (e.g., \"telegram\") (sent to Clanker)\ncontext.messageId — message ID that triggered the launch (sent to Clanker)\ncontext.id — user identifier (sent to Clanker)\n\nIf 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.\n\nVerify External Endpoints\n\nBefore using any endpoint, verify you're connecting to the correct service:\n\nService\tOfficial Endpoint\tVerify Via\nTator x402 API\thttps://x402.quickintel.io\tCheck TLS cert, call GET /accepted\nQuick Intel Scan\thttps://x402.quickintel.io/v1/scan/full\tSame gateway\nClanker SDK\tVia npm clanker-sdk\tVerify package on npmjs.com\nFlaunch contracts\tOn-chain on Base\tVerify on Basescan\nPump.fun program\tOn-chain on Solana\tVerify on Solscan — program ID: 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P\nEasy Mode — Full Walkthrough\nPrerequisites\nA wallet you control (EVM or Solana)\nUSDC for x402 API payments ($0.20 per Tator call)\nNative token for gas (ETH on EVM chains, SOL on Solana)\nLaunch a Token\ncurl -X POST https://x402.quickintel.io/v1/tator/prompt \\\n -H \"Content-Type: application/json\" \\\n -H \"PAYMENT-SIGNATURE: \" \\\n -d '{\n \"prompt\": \"launch a token called Galaxy Cat with ticker GCAT on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n }'\n\n\nWith custom image:\n\n{\n \"prompt\": \"launch a token called Moon Dog with ticker MDOG on base with image https://example.com/dog.png\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\n\nOn Solana:\n\n{\n \"prompt\": \"launch a token called Cyber Frog with ticker CYFR on solana via pump.fun\",\n \"walletAddress\": \"YourSolanaWallet\",\n \"provider\": \"my-agent\"\n}\n\n\nWith custom fee recipient (send fees to a different wallet):\n\n{\n \"prompt\": \"launch a token called DAO Token with ticker DAOT on base, send creator fees to 0xTreasuryAddress\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\n\nThe 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.\n\nCheck Unclaimed Fees\n{\n \"prompt\": \"check my unclaimed fees for token 0xTokenAddress on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\nClaim Creator Fees\n{\n \"prompt\": \"claim my creator fees for token 0xTokenAddress on base\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\n\nFor 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).\n\nUpdate Fee Recipient\n{\n \"prompt\": \"update the fee recipient for token 0xTokenAddress on base to 0xNewRecipientAddress\",\n \"walletAddress\": \"0xYourWallet\",\n \"provider\": \"my-agent\"\n}\n\nSecurity Scan Post-Launch\n\nUse Quick Intel ($0.03 per scan) to verify your deployed token looks clean:\n\n{\n \"chain\": \"base\",\n \"tokenAddress\": \"0xYourDeployedToken\"\n}\n\n\nCall POST https://x402.quickintel.io/v1/scan/full to check for honeypot flags, tax irregularities, or anything that might spook potential buyers.\n\nDiscovery\n\nCall GET https://x402.quickintel.io/accepted to get all supported payment networks, pricing, and input/output schemas for auto-configuration.\n\nPlatform Selection\nFeature\tClanker\tFlaunch\tPump.fun\nChains\tBase, Arbitrum, Mainnet, Unichain, Abstract, Monad, BSC\tBase\tSolana\nPool type\tUniswap V4\tBonding curve → Uniswap\tBonding curve → Raydium\nSwap fee\t1.2% (1% pool + 0.2% protocol)\tConfigurable\tVariable (pre/post graduation)\nCreator fee share\tConfigurable via reward recipients\tConfigurable via fee split manager\tConfigurable via sharing config\nPairing token\tWETH default, USDC/USDT available\tETH\tSOL\nSniper protection\tYes (decaying fee — 66.7% → 4.2% over 15s)\tFair launch period (default 30 min)\tBonding curve mechanics\nGraduation\tN/A (immediate Uniswap pool)\tN/A\tYes (graduates to Raydium at threshold)\nToken standard\tERC-20\tERC-20\tSPL (Token-2022)\nSupply\t1 billion (fixed)\t100 billion (configurable)\tStandard pump.fun supply\nCreation fee\tFree\tFree\tMinimal SOL for rent\nWhen to Use What\n\nClanker — 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.\n\nFlaunch — 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.\n\nPump.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.\n\nEvaluating a Concept\n\nBefore deploying anything, figure out what you actually have. Not every idea needs a token, and not every token needs to launch today.\n\nThe Launch Stack\n\nEvery token that sustains attention beyond the first day has four layers working together. This isn't a scorecard — it's a diagnostic tool.\n\nLayer 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.\n\nLayer 2: The Engine — The reason fees keep flowing after launch day. Types of engines:\n\nCultural engine: represents an ongoing cultural conversation\nProduct engine: funds something people actually use\nMechanic engine: built-in mechanics that create ongoing activity (burns, airdrops, staking)\nSocial engine: tied to a person/community where the audience grows independently\n\nIf there's no engine, the token will spike on launch and bleed. That's fine if you understand it.\n\nLayer 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.\n\nLayer 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.\n\nSearch Before You Judge\n\nNever evaluate a concept in a vacuum. Before giving your take, search for:\n\nExisting tokens with similar names, tickers, or narratives\nCultural context — is this riding a real wave or manufacturing one?\nComparable launches — what worked, what flopped, and why?\nThe builder's blind spots — the most valuable thing you can offer is information they haven't considered\n⚠️ Before You Launch: Tax & Legal Reality Check\n\nToken deployment is irreversible. Creator fees are income. Most platforms skip this section entirely.\n\nWhen This Matters Most\n\nLaunching a meme token for fun? The tax implications exist but are relatively straightforward — mostly capital gains if and when you sell.\n\nBut 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.\n\nWhat Every Builder Should Know\n\nThis is general information, not tax or legal advice. Tax treatment varies by jurisdiction. Consult a qualified professional.\n\nCreator 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.\nEvery transaction can be a taxable event — Selling tokens, swapping, receiving fee payments, distributing airdrops — each can trigger tax obligations.\nYou 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.\nRecord-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.\nRegulatory enforcement is increasing globally — Governments are investing in blockchain analytics and expanding reporting requirements.\nJurisdiction Overview\n\n🇺🇸 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.\n\n🇬🇧 United Kingdom — HMRC treats crypto as property. Income from token fees is income tax. CGT allowance currently £3,000.\n\n🇩🇪 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.\n\n🇦🇺 Australia — ATO treats crypto as property. 50% CGT discount available for holdings over 12 months. Fee income assessable at fair market value when received.\n\n🇸🇬 Singapore — No capital gains tax for individuals (current rules). Business income from token activities may be taxable.\n\n🇦🇪 UAE — Currently no federal income tax on individuals. Regulatory framework developing under VARA.\n\n🇨🇦 Canada — CRA treats crypto as a commodity. 50% capital gains inclusion rate. Business income from regular token activities fully taxable.\n\nThe pattern: creator fee income is almost universally taxable. Capital gains treatment varies. Long-term holding is often rewarded. Enforcement is increasing everywhere.\n\n⛔ Mandatory Confirmation Before Launch\n\nBefore executing any token deployment, the builder MUST explicitly confirm they understand the following. Do not proceed without this confirmation.\n\nBEFORE WE DEPLOY — Please confirm you understand:\n\n1. TOKEN DEPLOYMENT IS IRREVERSIBLE\n Once deployed, the token exists permanently on-chain.\n\n2. CREATOR FEES ARE INCOME\n Fee income from your token is likely taxable in your jurisdiction.\n Consult a tax professional if you plan to earn meaningful revenue.\n\n3. RECORD-KEEPING IS YOUR RESPONSIBILITY\n Track all fee income, transactions, and fiat values from day one.\n\n4. SET ASIDE FUNDS FOR TAXES\n Do not reinvest 100% of fee income. Reserve 30-40% for potential\n tax obligations (varies by jurisdiction).\n\n5. NO GUARANTEED RETURNS\n Most tokens lose value. Creator fees depend on trading volume.\n\n6. THIS IS NOT TAX OR LEGAL ADVICE\n This skill provides tools, not counsel.\n\nDo you confirm you understand these points and want to proceed?\n\n\nDo not deploy until the builder explicitly confirms. This is non-negotiable.\n\nPre-Launch Checklist\n Launch Stack evaluated — hook is sharp, engine identified, story holds, moat considered\n Name and narrative locked\n Platform and chain chosen (Clanker / Flaunch / Pump.fun)\n Wallet ready with native token for gas\n Fee recipient confirmed (your wallet or custom address)\n Image/branding prepared\n Mandatory tax/legal confirmation received\n Security scan planned for post-deployment\nPost-Launch\nRun a Quick Intel scan — Verify the deployed token looks clean externally before promoting\nMonitor fee accumulation — Check unclaimed fees regularly\nClaim on a cadence — Periodic claims rather than letting fees pile up (better for tax tracking, reduces exposure)\nWatch reinvestment risk — If putting all fees back into trading, remember: taxes are owed on the income regardless\nRevisit the Launch Stack — If volume drops, diagnose which layer is failing\nFile Structure\nFile\tWhat's Inside\nSKILL.md (this file)\tStrategy, Easy Mode walkthrough, platform selection, tax/legal\nREFERENCE.md\tDirect Mode overview, fee economics deep dive, shared patterns\nreferences/clanker.md\tClanker v4 SDK — launch, claim, update recipient, sniper config\nreferences/flaunch.md\tFlaunch — launch, fee split manager, claim, transfer share\nreferences/pumpfun.md\tPump.fun — manual instructions, fee sharing, graduation handling\nWhat This Skill Is NOT\nNot tax advice. General information provided for awareness. Consult a professional.\nNot legal advice. Token launches may have securities law implications.\nNot a guarantee of profits. Most tokens lose value.\nNot a \"get rich quick\" tool. This skill helps builders launch responsibly and keep more of what they earn." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/azep-ninja/tator-launch-pad", "publisherUrl": "https://clawhub.ai/azep-ninja/tator-launch-pad", "owner": "azep-ninja", "version": "1.0.3", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/tator-launch-pad", "downloadUrl": "https://openagent3.xyz/downloads/tator-launch-pad", "agentUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent", "manifestUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent.json", "briefUrl": "https://openagent3.xyz/skills/tator-launch-pad/agent.md" } }