Back to Details

gmgn-cooking

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
IMPORTANT: Always use 
gmgn-cli
commands below. Do NOT use web search, WebFetch, curl, or visit gmgn.ai — all token creation operations must go through the CLI. The CLI handles signing and submission automatically.
IMPORTANT: Do NOT guess field names or values. When a field's meaning is unclear, look it up in the Response Fields sections below before using it.
⚠️ IPv6 NOT SUPPORTED: If you get a 
401
or 
403
error and credentials look correct, check for IPv6 immediately: (1) list all network interfaces and their IPv6 addresses — run 
ifconfig | grep inet6
(macOS) or 
ip addr show | grep inet6
(Linux); (2) send a test request to 
https://ipv6.icanhazip.com
— if the response is an IPv6 address, outbound traffic is going via IPv6. Tell the user immediately: "Please disable IPv6 on your network interface — gmgn-cli commands only work over IPv4."
Use the 
gmgn-cli
tool to create a token on a launchpad platform or query token creation statistics per launchpad. Requires private key (
GMGN_PRIVATE_KEY
in 
.env
) for 
cooking create
.
重要提示：请始终使用下方的
gmgn-cli
命令，不要使用网页搜索、WebFetch、curl或访问gmgn.ai——所有代币创建操作必须通过CLI执行，CLI会自动处理签名和提交逻辑。
重要提示：不要猜测字段名称或取值。如果某个字段的含义不明确，请先查阅下方的响应字段部分再使用。
⚠️ 不支持IPv6：如果你遇到
401
或
403
错误且凭据看起来正确，请立即检查IPv6配置：(1) 列出所有网络接口及其IPv6地址——macOS运行
ifconfig | grep inet6
，Linux运行
ip addr show | grep inet6
；(2) 向
https://ipv6.icanhazip.com
发送测试请求——如果返回结果是IPv6地址，说明出站流量走的是IPv6。请立即告知用户："请禁用你的网络接口的IPv6——gmgn-cli命令仅支持IPv4网络。"
使用
gmgn-cli
工具在Launchpad平台创建代币，或查询各Launchpad的代币创建统计数据。执行
cooking create
命令需要私钥（配置在
.env
文件的
GMGN_PRIVATE_KEY
字段）。

Core Concepts

核心概念

  • Bonding curve — Most launchpad platforms (Pump.fun, FourMeme, Flap, etc.) launch tokens on an internal bonding curve. The token price rises as buyers enter. Once the threshold is reached, the token "graduates" to an open DEX (e.g. Raydium on SOL, PancakeSwap on BSC). Token creation happens on the bonding curve — not the open market.
  • --buy-amt
    is in human units     — 
    --buy-amt
    is expressed in full native token units, not smallest unit. 
    0.01
    = 0.01 SOL. 
    0.05
    = 0.05 BNB. Always confirm the human-readable amount with the user before executing.
  • --dex
    identifiers     — Each launchpad has a fixed identifier passed to 
    --dex
    . These are not free-form names — use only the identifiers listed in the Supported Launchpads table. Never guess a 
    --dex
    value not in that table.
  • Image input — Token logo can be provided as base64-encoded data (
    --image
    , max 2MB decoded) or a publicly accessible URL (
    --image-url
    ). Provide one or the other — not both. If the user gives a file path, read and base64-encode it before passing to 
    --image
    . If they give a URL, use 
    --image-url
    directly.
  • Status polling via 
    order get
     — 
    cooking create
    is asynchronous. The immediate response may show 
    pending
    . Poll with 
    gmgn-cli order get --chain <chain> --order-id <order_id>
    until 
    confirmed
    . The new token's contract address is in the 
    output_token
    field of the 
    order get
    response, not in the initial create response.
  • Critical auth — 
    cooking create
    requires both 
    GMGN_API_KEY
    and 
    GMGN_PRIVATE_KEY
    . The private key never leaves the machine — the CLI uses it only for local signing. 
    cooking stats
    uses normal auth (API Key only).
  • Slippage — The initial buy is executed as part of the same transaction as token creation. Slippage applies to that buy. Use 
    --slippage
    (decimal, e.g. 
    0.01
    = 1%) or 
    --auto-slippage
    . One of the two is required when 
    --buy-amt
    is set.
  • 联合曲线（Bonding curve） — 大多数Launchpad平台（Pump.fun、FourMeme、Flap等）都会在内部联合曲线体系下发行代币，代币价格会随着购买者增加而上涨。达到阈值后，代币会"升级"到公开DEX（比如SOL链的Raydium、BSC链的PancakeSwap）。代币创建操作是在联合曲线阶段完成，而非公开市场阶段。
  • --buy-amt
    使用常规可读单位     — 
    --buy-amt
    参数取值是原生代币的完整单位，而非最小单位。
    0.01
    代表0.01 SOL，
    0.05
    代表0.05 BNB。执行前务必和用户确认这个可读的金额是否正确。
  • --dex
    标识符     — 每个Launchpad都有固定的标识符传入
    --dex
    参数，不支持自定义名称，仅可使用支持的Launchpad列表中给出的标识符。绝对不要猜测列表以外的
    --dex
    取值。
  • 图片输入 — 代币Logo可通过base64编码数据提供（
    --image
    参数，解码后最大2MB），或公开可访问的URL提供（
    --image-url
    参数），二者仅能选其一。如果用户提供的是文件路径，先读取文件并转为base64编码再传入
    --image
    ；如果用户提供的是URL，直接使用
    --image-url
    参数即可。
  • 通过
    order get
    轮询状态     — 
    cooking create
    是异步操作，即时响应可能返回
    pending
    （处理中）状态。使用
    gmgn-cli order get --chain <chain> --order-id <order_id>
    轮询，直到状态变为
    confirmed
    （已确认）。新代币的合约地址在
    order get
    响应的
    output_token
    字段中，不会在初始创建响应中返回。
  • 关键鉴权规则 — 
    cooking create
    需要同时配置
    GMGN_API_KEY
    和
    GMGN_PRIVATE_KEY
    ，私钥永远不会离开本地设备，CLI仅用它做本地签名。
    cooking stats
    仅需要常规鉴权（仅API Key即可）。
  • 滑点（Slippage） — 初始购买操作和代币创建是在同一个交易中执行的，初始购买会涉及滑点。可使用
    --slippage
    （小数格式，比如
    0.01
    代表1%）或
    --auto-slippage
    参数，设置了
    --buy-amt
    时必须二选一。

Financial Risk Notice

金融风险提示

This skill executes REAL, IRREVERSIBLE blockchain transactions.
  • Every 
    cooking create
    command deploys an on-chain token contract and spends real funds (initial buy amount).
  • Token deployments cannot be undone once confirmed on-chain.
  • The AI agent must never auto-execute a create — explicit user confirmation is required every time, without exception.
  • Only use this skill with funds you are willing to spend. Initial buy amounts are non-refundable.
本功能会执行真实的、不可撤销的区块链交易。
  • 每一条
    cooking create
    命令都会部署链上代币合约，并消耗真实资产（初始购买金额）。
  • 代币部署一旦在链上确认就无法撤销。
  • AI Agent绝对不能自动执行创建操作——每次都必须获得用户明确确认，没有例外。
  • 仅使用你可承受损失的资产执行本操作，初始购买金额不予退还。

Sub-commands

子命令

Sub-commandDescription
cooking stats
Get token creation count statistics grouped by launchpad platform (normal auth)
cooking create
Deploy a new token on a launchpad platform (requires private key)
子命令说明
cooking stats
获取按Launchpad平台分组的代币创建数量统计（常规鉴权即可）
cooking create
在Launchpad平台部署新代币（需要私钥）

Supported Chains

支持的链

sol
/ 
bsc
/ 
base
/ 
eth
/ 
ton
sol
/ 
bsc
/ 
base
/ 
eth
/ 
ton

Supported Launchpads by Chain

各链支持的Launchpad

Chain
--dex
values
sol
pump
/ 
raydium
/ 
bonk
/ 
bags
/ 
memoo
/ 
letsbonk
/ 
bonkers
bsc
pancakeswap
/ 
flap
/ 
fourmeme
base
clanker
/ 
flaunch
/ 
baseapp
/ 
basememe
/ 
zora
/ 
virtuals_v2
When the user names a platform colloquially (e.g. "pump.fun", "four.meme", "PancakeSwap"), map it to the correct 
--dex
identifier from this table before running the command.
链
--dex
取值
sol
pump
/ 
raydium
/ 
bonk
/ 
bags
/ 
memoo
/ 
letsbonk
/ 
bonkers
bsc
pancakeswap
/ 
flap
/ 
fourmeme
base
clanker
/ 
flaunch
/ 
baseapp
/ 
basememe
/ 
zora
/ 
virtuals_v2
如果用户使用平台的俗称（比如"pump.fun"、"four.meme"、"PancakeSwap"），运行命令前请先映射为上表中对应的
--dex
标识符。

Prerequisites

前置要求

  • cooking stats
    : Only 
    GMGN_API_KEY
    required
  • cooking create
    : Both 
    GMGN_API_KEY
    and 
    GMGN_PRIVATE_KEY
    must be configured in 
    ~/.config/gmgn/.env
    . The private key must correspond to the wallet bound to the API Key.
  • gmgn-cli
    installed globally — if missing, run: 
    npm install -g gmgn-cli
  • cooking stats
    ：仅需要
    GMGN_API_KEY
  • cooking create
    ：
    GMGN_API_KEY
    和
    GMGN_PRIVATE_KEY
    都必须配置在
    ~/.config/gmgn/.env
    文件中，私钥对应的钱包必须和API Key绑定的钱包一致。
  • 全局安装了
    gmgn-cli
    ——如果没有安装，运行：
    npm install -g gmgn-cli

Rate Limit Handling

限流处理

All cooking routes go through GMGN's leaky-bucket limiter with 
rate=10
and 
capacity=10
. Sustained throughput is roughly 
10 ÷ weight
requests/second.
CommandWeight
cooking create
5
cooking stats
1
When a request returns 
429
:
  • Read 
    X-RateLimit-Reset
    from the response headers — Unix timestamp for when the limit resets.
  • cooking create
    is a real transaction: never loop or auto-resubmit after a 
    429
    . Wait until the reset time, then ask for confirmation again before retrying.
  • For 
    RATE_LIMIT_EXCEEDED
    or 
    RATE_LIMIT_BANNED
    , repeated requests during cooldown extend the ban by 5 seconds each time, up to 5 minutes.
First-time setup (if credentials are not configured):
  1. Generate key pair and show the public key to the user:
    bash
    openssl genpkey -algorithm ed25519 -out /tmp/gmgn_private.pem 2>/dev/null && \
  openssl pkey -in /tmp/gmgn_private.pem -pubout 2>/dev/null
    Tell the user: "This is your Ed25519 public key. Go to https://gmgn.ai/ai, paste it into the API key creation form (enable swap/cooking capability), then send me the API Key value shown on the page."
  2. Wait for the user's API key, then configure both credentials:
    bash
    mkdir -p ~/.config/gmgn
echo 'GMGN_API_KEY=<key_from_user>' > ~/.config/gmgn/.env
echo 'GMGN_PRIVATE_KEY="<pem_content_from_step_1>"' >> ~/.config/gmgn/.env
chmod 600 ~/.config/gmgn/.env
所有cooking相关接口都走GMGN的漏桶限流规则，
rate=10
、
capacity=10
，持续吞吐量约为
10 ÷ 权重
次请求/秒。
命令权重
cooking create
5
cooking stats
1
当请求返回
429
错误时：
  • 读取响应头中的
    X-RateLimit-Reset
    ——这是限流重置的Unix时间戳。
  • cooking create
    是真实交易：遇到
    429
    后绝对不要循环或自动重提，等到重置时间后，再次向用户申请确认再重试。
  • 对于
    RATE_LIMIT_EXCEEDED
    或
    RATE_LIMIT_BANNED
    错误，冷却期内重复请求会每次延长封禁5秒，最长延长到5分钟。
首次配置流程（如果还没配置凭据）：
  1. 生成密钥对并向用户展示公钥：
    bash
    openssl genpkey -algorithm ed25519 -out /tmp/gmgn_private.pem 2>/dev/null && \
  openssl pkey -in /tmp/gmgn_private.pem -pubout 2>/dev/null
    告知用户："这是你的Ed25519公钥，请前往**https://gmgn.ai/ai**，把它粘贴到API Key创建表单中（开启swap/cooking权限），然后把页面上显示的API Key发给我。"
  2. 等待用户提供API Key，然后配置两个凭据：
    bash
    mkdir -p ~/.config/gmgn
echo 'GMGN_API_KEY=<用户提供的key>' > ~/.config/gmgn/.env
echo 'GMGN_PRIVATE_KEY="<步骤1生成的pem文件内容>"' >> ~/.config/gmgn/.env
chmod 600 ~/.config/gmgn/.env

Credential Model

凭据模型

  • GMGN_PRIVATE_KEY
    is used exclusively for local message signing — the private key never leaves the machine. The CLI computes an Ed25519 signature in-process and transmits only the base64-encoded result in the 
    X-Signature
    request header.
  • GMGN_API_KEY
    is transmitted in the 
    X-APIKEY
    header over HTTPS.
  • Neither credential is ever passed as a command-line argument.
  • GMGN_PRIVATE_KEY
    仅用于本地消息签名——私钥永远不会离开本地设备，CLI会在进程内计算Ed25519签名，仅把base64编码的签名结果放在
    X-Signature
    请求头中传输。
  • GMGN_API_KEY
    通过HTTPS放在
    X-APIKEY
    请求头中传输。
  • 两个凭据都不会作为命令行参数传递。

cooking stats
Usage

cooking stats
用法

bash
gmgn-cli cooking stats [--raw]
bash
gmgn-cli cooking stats [--raw]

cooking stats
Response Fields

cooking stats
响应字段

FieldTypeDescription
launchpad
stringLaunchpad identifier (e.g. 
pump
, 
raydium
, 
pancakeswap
)
token_count
intNumber of tokens created via GMGN on that launchpad
字段类型说明
launchpad
stringLaunchpad标识符（比如
pump
、
raydium
、
pancakeswap
）
token_count
int通过GMGN在该Launchpad创建的代币数量

cooking create
Parameters

cooking create
参数

ParameterRequiredDescription
--chain
YesChain: 
sol
/ 
bsc
/ 
base
/ 
eth
/ 
ton
--dex
YesLaunchpad platform identifier — see Supported Launchpads table. Never guess this value.
--from
YesWallet address (must match API Key binding)
--name
YesToken full name (e.g. 
Doge Killer
)
--symbol
YesToken ticker symbol (e.g. 
DOGEK
)
--description
NoToken description / project pitch
--buy-amt
YesInitial buy amount in human-readable native token units (e.g. 
0.01
= 0.01 SOL). This is NOT in smallest unit.
--image
No*Token logo as base64-encoded data (max 2MB decoded). Mutually exclusive with 
--image-url
. One of the two is required.
--image-url
No*Token logo as a publicly accessible URL. Mutually exclusive with 
--image
. One of the two is required.
--slippage
No*Slippage tolerance, e.g. 
0.01
= 1%. Mutually exclusive with 
--auto-slippage
 — provide one or the other.
--auto-slippage
No*Enable automatic slippage. Mutually exclusive with 
--slippage
.
--website
NoProject website URL
--twitter
NoTwitter / X URL
--telegram
NoTelegram group URL
--priority-fee
NoPriority fee in SOL (SOL only, ≥ 0.0001 SOL)
--tip-fee
NoTip fee (SOL ≥ 0.00001 / BSC ≥ 0.000001 BNB; ignored on ETH/BASE)
--gas-price
NoGas price in wei (EVM chains)
--anti-mev
NoEnable anti-MEV protection
* 
--image
or 
--image-url
: provide exactly one. 
--slippage
or 
--auto-slippage
: provide exactly one.
参数必填说明
--chain
是链：
sol
/ 
bsc
/ 
base
/ 
eth
/ 
ton
--dex
是Launchpad平台标识符——参考支持的Launchpad表格，绝对不要猜测该值。
--from
是钱包地址（必须和API Key绑定的地址一致）
--name
是代币全称（比如
Doge Killer
）
--symbol
是代币代码（比如
DOGEK
）
--description
否代币描述/项目介绍
--buy-amt
是初始购买金额，单位为可读的原生代币完整单位（比如
0.01
= 0.01 SOL），不是最小单位。
--image
否*代币Logo的base64编码数据（解码后最大2MB），和
--image-url
互斥，二者必须填一个。
--image-url
否*代币Logo的公开可访问URL，和
--image
互斥，二者必须填一个。
--slippage
否*滑点容忍度，比如
0.01
= 1%，和
--auto-slippage
互斥，二者必须填一个。
--auto-slippage
否*开启自动滑点，和
--slippage
互斥。
--website
否项目官网URL
--twitter
否Twitter/X主页URL
--telegram
否Telegram群组URL
--priority-fee
否优先级费用，单位SOL（仅SOL链有效，≥ 0.0001 SOL）
--tip-fee
否小费（SOL ≥ 0.00001 / BSC ≥ 0.000001 BNB；ETH/BASE链忽略）
--gas-price
否Gas价格，单位wei（EVM链适用）
--anti-mev
否开启反MEV保护
* 
--image
和
--image-url
二选一必填；
--slippage
和
--auto-slippage
二选一必填。

cooking create
Response Fields

cooking create
响应字段

FieldTypeDescription
status
string
pending
/ 
confirmed
/ 
failed
hash
stringTransaction hash (may be empty while 
pending
)
order_id
stringOrder ID — pass to 
gmgn-cli order get
to poll for final status
error_code
stringError code on failure
error_status
stringError description on failure
字段类型说明
status
string
pending
（处理中） / 
confirmed
（已确认） / 
failed
（失败）
hash
string交易哈希（
pending
状态时可能为空）
order_id
string订单ID——传给
gmgn-cli order get
轮询最终状态
error_code
string失败时的错误码
error_status
string失败时的错误描述

Status Polling

状态轮询

Token creation is asynchronous. If the initial 
cooking create
response shows 
status: pending
:
  1. Poll with 
    gmgn-cli order get
    every 2 seconds, up to 30 seconds:
    bash
    gmgn-cli order get --chain <chain> --order-id <order_id>
  2. The new token's contract / mint address is in the 
    output_token
     field of the 
    order get
    response — it is NOT returned by 
    cooking create
    directly.
  3. Stop polling once 
    status
    is 
    confirmed
    , 
    failed
    , or 
    expired
    .
  4. On 
    confirmed
    : display 
    output_token
    as the token address and include the block explorer link.
  5. On 
    failed
    / 
    expired
    : report the 
    error_status
    and do not retry automatically.
代币创建是异步操作，如果初始
cooking create
响应返回
status: pending
：
  1. 每2秒调用一次
    gmgn-cli order get
    轮询，最多轮询30秒：
    bash
    gmgn-cli order get --chain <chain> --order-id <order_id>
  2. 新代币的合约/发行地址在
    order get
    响应的**
    output_token
    **字段中——不会直接由
    cooking create
    返回。
  3. 当
    status
    变为
    confirmed
    、
    failed
    或
    expired
    时停止轮询。
  4. 状态为
    confirmed
    时：展示
    output_token
    作为代币地址，并附上区块浏览器链接。
  5. 状态为
    failed
    /
    expired
    时：上报
    error_status
    ，不要自动重试。

Usage Examples

使用示例

bash
undefined
bash
undefined

Get token creation statistics per launchpad

获取各Launchpad的代币创建统计

gmgn-cli cooking stats
gmgn-cli cooking stats

Create a token on Pump.fun (SOL) — with URL image

在SOL链的Pump.fun创建代币——使用URL形式的图片

gmgn-cli cooking create
--chain sol
--dex pump
--from <wallet_address>
--name "My Token"
--symbol MAT
--buy-amt 0.01
--image-url https://example.com/logo.png
--slippage 0.01
--priority-fee 0.001
gmgn-cli cooking create
--chain sol
--dex pump
--from <钱包地址>
--name "My Token"
--symbol MAT
--buy-amt 0.01
--image-url https://example.com/logo.png
--slippage 0.01
--priority-fee 0.001

Create a token on PancakeSwap (BSC) — with URL image and social links

在BSC链的PancakeSwap创建代币——使用URL形式的图片和社交链接

gmgn-cli cooking create
--chain bsc
--dex pancakeswap
--from <wallet_address>
--name "BSC Token"
--symbol BSCT
--buy-amt 0.05
--image-url https://example.com/logo.png
--slippage 0.02
--gas-price 5000000000
--website https://mytoken.io
--twitter https://twitter.com/mytoken
gmgn-cli cooking create
--chain bsc
--dex pancakeswap
--from <钱包地址>
--name "BSC Token"
--symbol BSCT
--buy-amt 0.05
--image-url https://example.com/logo.png
--slippage 0.02
--gas-price 5000000000
--website https://mytoken.io
--twitter https://twitter.com/mytoken

Create a token on FourMeme (BSC) — using base64 image from local file

在BSC链的FourMeme创建代币——使用本地文件转base64的图片

gmgn-cli cooking create
--chain bsc
--dex fourmeme
--from <wallet_address>
--name "Four Token"
--symbol FOUR
--buy-amt 0.05
--image "$(base64 -i /path/to/logo.png)"
--auto-slippage
gmgn-cli cooking create
--chain bsc
--dex fourmeme
--from <钱包地址>
--name "Four Token"
--symbol FOUR
--buy-amt 0.05
--image "$(base64 -i /path/to/logo.png)"
--auto-slippage

Create a token on letsbonk (SOL)

在SOL链的letsbonk创建代币

gmgn-cli cooking create
--chain sol
--dex letsbonk
--from <wallet_address>
--name "Bonk Token"
--symbol BNKT
--buy-amt 0.01
--image-url https://example.com/logo.png
--auto-slippage
--anti-mev
undefined
gmgn-cli cooking create
--chain sol
--dex letsbonk
--from <钱包地址>
--name "Bonk Token"
--symbol BNKT
--buy-amt 0.01
--image-url https://example.com/logo.png
--auto-slippage
--anti-mev
undefined

Output Format

输出格式

Pre-create Confirmation

创建前确认

Before every 
cooking create
, present this summary and wait for explicit user confirmation:
⚠️ Token Creation Confirmation Required

Chain:        {chain}
Platform:     {--dex} (e.g. pump / fourmeme)
Wallet:       {--from}
Token Name:   {--name}
Symbol:       {--symbol}
Initial Buy:  {--buy-amt} {native currency} (e.g. 0.01 SOL)
Slippage:     {--slippage}% (or "auto")
Image:        {--image-url or "base64 provided"}
Social:       {twitter / telegram / website if provided}

Reply "confirm" to deploy this token. This action is IRREVERSIBLE.
每次执行
cooking create
前，都要先展示以下汇总信息，等待用户明确确认：
⚠️ 需要确认代币创建操作

链:        {chain}
平台:     {--dex}（比如pump / fourmeme）
钱包:       {--from}
代币名称:   {--name}
代码:       {--symbol}
初始购买:  {--buy-amt} {原生代币符号}（比如0.01 SOL）
滑点:     {--slippage}% 或 "auto"
图片:        {--image-url 或 "已提供base64"}
社交链接:       {如果提供了twitter/telegram/website则展示}

回复"confirm"部署该代币，该操作不可撤销。

Post-create Receipt

创建后凭证

After polling confirms a successful deployment:
✅ Token Created

Token:    {--name} ({--symbol})
Address:  {output_token from order get}
Chain:    {chain}
Platform: {--dex}
Tx:       {explorer link for hash}
Order ID: {order_id}
Block explorer links:
ChainExplorer
sol
https://solscan.io/tx/<hash>
bsc
https://bscscan.com/tx/<hash>
base
https://basescan.org/tx/<hash>
eth
https://etherscan.io/tx/<hash>
轮询确认部署成功后展示：
✅ 代币创建成功

代币:    {--name} ({--symbol})
地址:  {order get返回的output_token}
链:    {chain}
平台: {--dex}
交易:       {哈希对应的区块浏览器链接}
订单ID: {order_id}
区块浏览器链接：
链浏览器链接格式
sol
https://solscan.io/tx/<hash>
bsc
https://bscscan.com/tx/<hash>
base
https://basescan.org/tx/<hash>
eth
https://etherscan.io/tx/<hash>

Guided Launch Flow

引导式发行流程

When a user says they want to launch / create / deploy a token but has not provided all required information, do NOT ask for everything at once. Collect information in this order, one step at a time:
当用户表示想要发行/创建/部署代币，但没有提供所有必填信息时，不要一次性询问所有信息，按以下顺序分步收集，每次只问一步：

Step 1 — Chain & Platform

步骤1 — 链和平台

Ask: "Which chain and platform do you want to launch on?"
Show the available options:
ChainPlatform
--dex
SolanaPump.fun
pump
Solanaletsbonk
letsbonk
SolanaRaydium
raydium
SolanaBAGS
bags
SolanaMemoo
memoo
SolanaBonkers
bonkers
BSCFourMeme
fourmeme
BSCPancakeSwap
pancakeswap
BSCFlap
flap
BaseClanker
clanker
BaseZora
zora
BaseFlaunch
flaunch
BaseVirtuals
virtuals_v2
If the user is unsure, recommend: Pump.fun (SOL) or FourMeme (BSC) — the two most active launchpads.
询问："你想要在哪个链和平台上发行代币？"
展示可用选项：
链平台
--dex
SolanaPump.fun
pump
Solanaletsbonk
letsbonk
SolanaRaydium
raydium
SolanaBAGS
bags
SolanaMemoo
memoo
SolanaBonkers
bonkers
BSCFourMeme
fourmeme
BSCPancakeSwap
pancakeswap
BSCFlap
flap
BaseClanker
clanker
BaseZora
zora
BaseFlaunch
flaunch
BaseVirtuals
virtuals_v2
如果用户不确定，推荐：Pump.fun (SOL) 或 FourMeme (BSC)——这两个是最活跃的Launchpad。

Step 2 — Token Identity

步骤2 — 代币基本信息

Ask for name, symbol, and description together:
"What is your token's name, ticker symbol, and a short description?"
  • Name: the full display name (e.g. 
    Doge Killer
    )
  • Symbol: short uppercase ticker, typically 3–8 characters (e.g. 
    DOGEK
    )
  • Description: optional but recommended — a one-line pitch shown on the launchpad
一起询问名称、代码和描述：
"你的代币的名称、代码和简短介绍是什么？"
  • 名称：完整展示名（比如
    Doge Killer
    ）
  • 代码：短的大写代码，通常3-8个字符（比如
    DOGEK
    ）
  • 描述：可选但推荐，展示在Launchpad上的一句话介绍

Step 3 — Logo

步骤3 — Logo

Ask: "Do you have a logo image? You can share a file path (e.g. 
/Users/you/logo.png
) or an image URL."
  • If the user provides a file path: silently run 
    base64 -i <path>
    and pass the result to 
    --image
    . Do not mention "base64" to the user.
  • If the user provides a URL: use 
    --image-url
    directly.
  • If the user has no logo: note that most platforms accept a launch without one, but it significantly reduces visibility. Ask if they want to proceed without it.
询问："你有Logo图片吗？你可以提供文件路径（比如
/Users/you/logo.png
）或者图片URL。"
  • 如果用户提供文件路径：静默运行
    base64 -i <路径>
    ，把结果传给
    --image
    ，不要和用户提"base64"相关内容。
  • 如果用户提供URL：直接使用
    --image-url
    参数。
  • 如果用户没有Logo：告知大多数平台支持无Logo发行，但会大幅降低曝光度，询问用户是否要无Logo继续。

Step 4 — Social Links (optional)

步骤4 — 社交链接（可选）

Ask: "Do you have a Twitter, Telegram, or website to attach to the token? You can skip this."
Collect any combination of 
--twitter
, 
--telegram
, 
--website
. If the user skips, proceed to the next step.
询问："你有要绑定到代币的Twitter、Telegram或官网吗？可以跳过。"
收集任意组合的
--twitter
、
--telegram
、
--website
，如果用户跳过就进入下一步。

Step 5 — Initial Buy Amount

步骤5 — 初始购买金额

Ask: "How much {SOL / BNB / ETH} do you want to spend on the initial buy?"
Pass the user's answer directly to 
--buy-amt
— this is already in full token units (e.g. 
0.01
= 0.01 SOL), do NOT convert to lamports or wei.
询问："你想要花多少{SOL / BNB / ETH}做初始购买？"
直接把用户的回答传给
--buy-amt
——该值已经是完整代币单位（比如
0.01
= 0.01 SOL），不要转换为lamport或wei。

Step 6 — Confirmation & Execute

步骤6 — 确认和执行

Once all information is collected, present the pre-create confirmation summary (see Output Format section) and wait for the user to reply "confirm" before executing.
收集完所有信息后，展示创建前确认汇总（参考输出格式部分），等待用户回复"confirm"后再执行。

Execution Guidelines

执行指南

  • [REQUIRED] Pre-create confirmation — Before executing 
    cooking create
    , present the full summary above and receive explicit "confirm" from the user. No exceptions. Do NOT auto-create.
  • [REQUIRED] 
    --dex
    validation     — Before running, look up the user's named platform in the Supported Launchpads table and resolve to the correct 
    --dex
    identifier. Never guess or pass a freeform platform name. If the chain/platform combination is not in the table, tell the user it is unsupported.
  • Slippage requirement — Either 
    --slippage
    or 
    --auto-slippage
    must be provided. If the user did not specify, suggest 
    --auto-slippage
    for volatile new tokens or ask for a preference.
  • Image handling — If the user provides a file path, run 
    base64 -i <path>
    and pass the result to 
    --image
    . If they provide a URL, use 
    --image-url
    . If neither is provided, ask before building the confirmation — most platforms require a logo.
  • Address validation — Validate 
    --from
    wallet address format before submitting: 
    • sol
      : base58, 32–44 characters
    • bsc
      / 
      base
      / 
      eth
      : 
      0x
      + 40 hex digits
  • Chain-wallet compatibility — SOL addresses are incompatible with EVM chains and vice versa. Warn the user and abort if the address format does not match the chain.
  • Order polling — After 
    cooking create
    , if 
    status
    is 
    pending
    , poll 
    order get
    every 2 seconds up to 30 seconds. The token address is in 
    output_token
    . Do not report success until 
    status
    is 
    confirmed
    .
  • Credential sensitivity — 
    GMGN_API_KEY
    and 
    GMGN_PRIVATE_KEY
    can execute real transactions. Never log, display, or expose these values.
  • [必填] 创建前确认 — 执行
    cooking create
    前，必须展示上面的完整汇总信息，获得用户明确的"confirm"回复，没有例外，绝对不要自动创建。
  • [必填] 
    --dex
    校验     — 运行前，在支持的Launchpad表格中查找用户提到的平台，解析为正确的
    --dex
    标识符，绝对不要猜测或传入自定义平台名称。如果链/平台组合不在表格中，告知用户不支持。
  • 滑点要求 — 必须提供
    --slippage
    或
    --auto-slippage
    中的一个。如果用户没有指定，推荐 volatile新代币使用
    --auto-slippage
    ，或者询问用户偏好。
  • 图片处理 — 如果用户提供文件路径，运行
    base64 -i <路径>
    把结果传给
    --image
    ；如果提供URL直接用
    --image-url
    ；如果都没有提供，生成确认信息前先询问——大多数平台要求有Logo。
  • 地址校验 — 提交前校验
    --from
    钱包地址格式： 
    • sol
      ：base58格式，32-44个字符
    • bsc
      / 
      base
      / 
      eth
      ：
      0x
      开头 + 40位十六进制字符
  • 链-钱包兼容性 — SOL地址和EVM链地址不兼容，如果地址格式和链不匹配，警告用户并终止操作。
  • 订单轮询 — 执行
    cooking create
    后，如果
    status
    是
    pending
    ，每2秒轮询一次
    order get
    ，最多轮询30秒。代币地址在
    output_token
    字段中，
    status
    变为
    confirmed
    之前不要上报成功。
  • 凭据敏感度 — 
    GMGN_API_KEY
    和
    GMGN_PRIVATE_KEY
    可以执行真实交易，绝对不要记录、展示或泄露这些值。

Notes

注意事项

  • cooking create
    uses critical auth (API Key + signature) — CLI handles signing automatically.
  • cooking stats
    uses normal auth (API Key only — no private key needed).
  • The new token's mint address is in 
    output_token
    from 
    gmgn-cli order get
    , not in the initial 
    cooking create
    response.
  • Use 
    --raw
    on any command to get single-line JSON for further processing.
  • cooking create
    使用关键鉴权（API Key + 签名）——CLI会自动处理签名。
  • cooking stats
    使用常规鉴权（仅需要API Key，不需要私钥）。
  • 新代币的发行地址在
    gmgn-cli order get
    返回的
    output_token
    字段中，不会在初始
    cooking create
    响应中返回。
  • 任意命令都可以加
    --raw
    参数获取单行JSON格式结果，用于后续处理。

References

参考

SkillDescription
gmgn-swapContains 
order get
command used for polling token creation status
gmgn-tokenToken security check, info, holders, and traders — useful after launch to monitor your token
gmgn-market
market trenches
for tracking bonding curve progress; 
market trending
to see if your token is gaining traction
gmgn-trackSmart money and KOL trade tracking — monitor whether smart wallets are buying your token after launch
gmgn-portfolioWallet holdings and P&L — check your own wallet balance before deciding on 
--buy-amt
Skill说明
gmgn-swap包含用于轮询代币创建状态的
order get
命令
gmgn-token代币安全检测、信息查询、持仓用户和交易者查询——发行后用于监控代币非常实用
gmgn-market
market trenches
用于跟踪联合曲线进度；
market trending
用于查看你的代币是否在 gaining traction
gmgn-track聪明钱和KOL交易跟踪——监控发行后是否有聪明钱包购买你的代币
gmgn-portfolio钱包持仓和盈亏——确定
--buy-amt
前可以查询自己的钱包余额