Other Platforms

Bags, Bonk/USD1, BNB / Nadfun / Clanker / Stroid — create_token fields and auto_sell.

All examples use POST {region}/submit with "type": "create_token" and the right mode.

Bags (`mode: bags`)

Field	Type	Description
`bags_creator_share`	number	Creator share in basis points (10000 = 100%)
`bags_fee_claimers`	array	`{ "username", "bps", "provider"? }` — fee claimers; creator + claimers must sum to 10000 bps
`bags_config_type`	string	Optional preset UUID string (see app for known ids)
`telegram`	string	Optional

Bundle / sniper / auto_sell follow the same patterns as pump where the server supports them.

Example

{
  "type": "create_token",
  "session_id": "<jwt>",
  "api_key": "<encrypted>",
  "mode": "bags",
  "name": "My Bags Token",
  "ticker": "BAGS",
  "buy_amount": 5,
  "bags_creator_share": 2000,
  "bags_fee_claimers": [
    { "username": "somehandle", "bps": 8000, "provider": "twitter" }
  ],
  "image_url": "https://example.com/token-image.png"
}

Bonk / USD1 (`mode: bonk` or `mode: usd1`)

Field	Type	Default	Description
`bonkers_mode`	boolean	false	letsbonk.fun-style config when applicable

Supports bundle / bundle_wallets, sniper_wallets, and auto_sell where enabled server-side.

BNB / Nadfun / Clanker

Use mode": "bnb", "nadfun", or "clanker". Put your EVM encrypted key in api_key (see How to get an API key).

Field	Type	Description
`gwei`	number	Gas price hint (default 5 when omitted)
`bnb_currency`	string	e.g. `bnb` or `usd1` for Four.Meme-style BNB deploys

BNB + USD1 base example

{
  "type": "create_token",
  "session_id": "<jwt>",
  "api_key": "<encrypted_evm_key>",
  "mode": "bnb",
  "name": "My Token",
  "ticker": "MTK",
  "buy_amount": 0.1,
  "gwei": 5,
  "bnb_currency": "usd1"
}

Launches a token on the stroid.fun LaunchpadV3 (Ethereum mainnet). EVM mode — put your EVM encrypted key in api_key. Every option below is independently optional; pass nothing extra and you get the V3 default launch (100% of the creator slice → msg.sender, no partner attribution, ~1 ETH virtual LP, dynamic gas).

Stroid-only fields

Field	Type	Default	Description
`buy_amount`	number	`0`	Dev buy in ETH (not SOL). Sent as `msg.value` to `launchStroidDotFun()` minus the on-chain creation fee.
`recipients`	array \| string	empty → 100% to creator	Per-token creator-fee splits. Array of `{ "wallet": "0x…", "bps": <int> }` (max 5 entries, all `bps` must sum to exactly 10000). CSV escape hatch also accepted: `"0xAAA…:5000,0xBBB…:5000"`. Frozen on-chain at launch.
`partner`	string	`0x0000…0000` (none)	Partner-attribution wallet. Only earns fees if an admin has registered it via `FeeHookV3.setPartnerBps` — otherwise the partner slice routes back to the protocol. Pass `null`, `""`, or omit for "no partner".
`sqrt_price_tier`	integer (u8)	`0` (= tier 1 = ~1 ETH virtual LP, V2 default)	Virtual-LP starting tier. The index is the ETH-amount label (e.g. `5` = ~5 ETH virtual LP). Aliases: `tier`, `liquidity_tier`. Range `0..=255` — tier `0` is treated as alias for tier `1`.
`gas_gwei`	number	dynamic (`eth_gasPrice` × 1.5, floored at 1.5 gwei)	Banana / Maestro-style flat gas override. Sets both `maxFeePerGas` and `maxPriorityFeePerGas` to this value in gwei. Aliases: `priority_fee_gwei`, `max_fee_per_gas_gwei`.
`inline_metadata`	boolean	`false`	Skip the hosted R2 metadata upload and bake a `data:application/json;base64,…` URI on-chain. Use only for fully private deploys — most clients should leave this off so the token gets a normal `https://metadata.j7tracker.io/…` URI.
`metadata_uri`	string	auto	Pre-uploaded JSON metadata URI to use verbatim. When set, `inline_metadata` and the auto-upload are both skipped.
`private_desc`	boolean	`false`	When auto-uploading metadata, omit the default "Deployed using https://j7tracker.io" description.
`image_type`	string	`""`	Optional image-handling hint forwarded to the metadata upload (e.g. `letter`, `ascii`, `sol_ascii`, `url`).
`description`	string	`"Deployed using https://j7tracker.io"`	Token description in metadata.

Bundle / sniper / auto_sell are not wired for stroid — the LaunchpadV3 contract is single-tx and bundling Ethereum txs in the same block is a different protocol entirely.

Recipients — array form

{
  "type": "create_token",
  "external": true,
  "session_id": "<jwt>",
  "api_key": "<encrypted_evm_key>",
  "mode": "stroid",
  "name": "My Stroid Token",
  "ticker": "STRO",
  "buy_amount": 0.05,
  "image_url": "https://example.com/stroid.png",
  "twitter": "https://x.com/myhandle",
  "website": "https://example.com",
  "recipients": [
    { "wallet": "0xAAA0000000000000000000000000000000000001", "bps": 5000 },
    { "wallet": "0xBBB0000000000000000000000000000000000002", "bps": 3000 },
    { "wallet": "0xCCC0000000000000000000000000000000000003", "bps": 2000 }
  ],
  "sqrt_price_tier": 3,
  "gas_gwei": 2.5
}

5000 + 3000 + 2000 = 10000 → valid.

Recipients — CSV escape hatch

{
  "type": "create_token",
  "external": true,
  "session_id": "<jwt>",
  "api_key": "<encrypted_evm_key>",
  "mode": "stroid",
  "name": "My Stroid Token",
  "ticker": "STRO",
  "buy_amount": 0.05,
  "recipients": "0xAAA0000000000000000000000000000000000001:5000,0xBBB0000000000000000000000000000000000002:5000"
}

Defaults launch (no extras)

{
  "type": "create_token",
  "external": true,
  "session_id": "<jwt>",
  "api_key": "<encrypted_evm_key>",
  "mode": "stroid",
  "name": "My Stroid Token",
  "ticker": "STRO",
  "buy_amount": 0.01
}

→ 100% of the creator slice routes to the deployer wallet, no partner, ~1 ETH virtual LP, dynamic gas (eth_gasPrice × 1.5, floored at 1.5 gwei).

Stroid response shape

The success payload is richer than Solana deploys — includes the FeeHook contract that was bound to the token (used later for sells / claim_fee) and the dev-buy token amount in both raw 18-decimal and human-readable form.

{
  "type": "token_create_success",
  "mode": "stroid",
  "launchpad_version": "v3",
  "name": "My Stroid Token",
  "ticker": "STRO",
  "address": "0x…",
  "mint_address": "0x…",
  "signature": "0x…",
  "tx_hash": "0x…",
  "fee_hook": "0x…",
  "buy_amount": 0.05,
  "creator_wallet": "0x…",
  "image": "https://…",
  "token_balance": "12345.6789",
  "token_balance_raw": "12345678900000000000000",
  "all_sigs": ["0x…"]
}

The error payload is identical to other modes (type: "token_create_error", plus mode: "stroid", message, error, username).

Latency

Stroid deploys wait for the on-chain receipt before responding (Ethereum block time is ~12s). The deploy-server-side HTTP timeout is therefore much longer than for Solana modes — plan for up to ~45s between sending the request and receiving token_create_success.

`auto_sell`

When auto_sell is true, the server includes auto-sell for modes it supports (commonly pump, bonk, usd1, bags). Use auto_sell_wallets for structured multi-wallet auto-sell where implemented.