token-launcher

What this skill does

# 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:

| Path | Your Share | Platform Cut | You Keep |
|------|-----------|-------------|----------|
| **Direct 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** |

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](./REFERENCE.md) for Direct Mode overview and the [references/](./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:**

| Variable | Required For | Sensitive | How to Store |
|----------|-------------|-----------|-------------|
| `WALLET_PRIVATE_KEY` | Signing deploy/claim/update transactions | **Yes — grants full wallet control** | Secrets manager (AWS SM, GCP SM, Vault). Never plaintext. |
| `RPC_URL` | Talking to the blockchain | No (but keep private to avoid rate limit abuse) | Environment variable or config |
| `SOLANA_RPC_URL` | Solana operations (Pump.fun only) | No | Environment variable or config |
| `PINATA_API_KEY` or `IPFS_API_KEY` | Uploading token metadata to IPFS | Yes | Secrets manager |

**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](./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:

| Service | Official Endpoint | Verify Via |
|---------|------------------|-----------|
| Tator x402 API | `https://x402.quickintel.io` | Check TLS cert, call `GET /accepted` |
| Quick Intel Scan | `https://x402.quickintel.io/v1/scan/full` | Same gateway |
| Clanker SDK | Via npm `clanker-sdk` | Verify package on npmjs.com |
| Flaunch contracts | On-chain on Base | Verify on Basescan |
| Pump.fun program | On-chain on Solana | Verify on Solscan — program ID: `6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P` |

---

## 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

```bash
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:**
```json
{
  "prompt": "launch a token called Moon Dog with ticker MDOG on base with image https://example.com/dog.png",
  "walletAddress": "0xYourWall