Clanker Deploy API
Capminal x402 Flash Clanker Token Deployment API
Deploy token very easily via API, no auth needed, no account needed, paid per request via x402. Designed for speed, clarity, and wallet‑native checkout.
Clanker tokens deployed via Capminal x402 API will be the same FEE STRUCTURE as when you deploy on Capminal UI or using Captain Dackie on X.
Clanker tokens deployed via Capminal x402 API will use Clanker V4.
Endpoint
Host:
https://www.capminal.ai/api/x402Method:
POSTPath:
/deployx402Version: 2
Authentication (payment)
This endpoint is protected by x402 micropayments.
First call without
X-PAYMENT→ you’ll receive402 Payment Requiredwith live payment instructions.Pay, then retry with
X-PAYMENT: <payment-proof>.
Pricing
$0.5 per successful request on Base
Request body (JSON)
chainId(string, required): EVM chain id. Example:8453for Basename(string, required): Token namesymbol(string, required): Token symboldescription(string, optional): Short token descriptionimageUrl(string, optional): URL to token image/logo. Use can use any public upload image website to upload your logo and get the url, png/jpeg is recommended.fee(string, required): Percentage fee, e.g.,"1%"to"10%"marketCap(string, required): One of"low","medium","high"stand for 1E, 5E and 10E init marketcapownerAddress(string, required): ERC‑20 owner wallet, starts with0x+ 40 hex chars
Headers
Content-Type: application/jsonX-PAYMENT(string, on retry): Cryptographic proof of payment
Request/response
Initial request (expect 402):
Example 402 response (shape may include additional fields):
Retry with payment proof:
Success (200) response:
Errors
400 Bad Request: Missing/invalid body fields402 Payment Required: Missing/invalid payment or not yet paid503 Service Unavailable: Upstream services temporarily unavailable
Tips
Keep the request body identical between the first call and the retry
Validate
ownerAddressformat and symbol constraints on your side for best UX
Last updated