Help Center
Everything you need to launch, commit, and claim on HOODML Launchpad.
Frequently Asked Questions
Tutorials for New Users
1. Create a token
- Go to Create Token in the sidebar.
- Enter token name, symbol, and description.
- Set raise target, token price, and per-wallet caps.
- Review the live preview & $HOODML pairing, then deploy.
2. Set raise rules
- Choose a realistic raise target in ETH.
- Set the token price (ETH per token).
- Define min and max commit per wallet to keep it fair.
- Pick a duration — the launch auto-ends when time expires.
3. Launch & commit
- Your launch goes active immediately on deploy.
- Browse Active Launches and open one.
- Enter an ETH amount within the caps.
- Commit — your allocation preview shows tokens and any expected refund.
4. Allocation & refund
- When the launch ends it's finalized.
- If oversubscribed, you get pro-rata tokens and the excess ETH is refunded.
- If undersubscribed, the launch fails and your full commitment is refunded.
- Claim refunds from the Refund Center.
Agent API (x402 — agents pay for launches)
AI agents can launch tokens programmatically over HTTP 402 — gasless USDC on Base mainnet via x402 v2 (permit2), settled by the Dexter public facilitator (https://x402.dexter.cash). No wallet UI is required; the agent signs the payment off-chain and the gate settles on-chain (facilitator sponsors gas).
Endpoint
POST https://hoodml-base-flow.base44.app/functions/x402GateServices
hoodml-launchProgrammatic token launch (agent API)$2
hoodml-boostLaunch boost / featured slot$5
Flow
- Agent POSTs
{ serviceId, launchConfig }to the gate. - Gate returns 402 Payment Required (x402 v2) with a
PAYMENT-REQUIREDheader (base64 payment requirements: USDC amount, pay-to treasury, permit2 payload). - Agent signs the permit2 payment message (x402 v2) and retries the same request with a
PAYMENT-SIGNATUREheader (base64 PaymentPayload). - Gate verifies via the Dexter facilitator (https://x402.dexter.cash), settles the USDC transfer on-chain (gas sponsored), creates the Launch record, and returns 200 with the created launch + a
PAYMENT-RESPONSEheader (base64 settlement receipt incl. transaction hash).
Example (hoodml-launch):
curl -X POST https://hoodml-base-flow.base44.app/functions/x402Gate \
-H "Content-Type: application/json" \
-d '{"serviceId":"hoodml-launch","launchConfig":{"token_name":"AgentCoin","token_symbol":"AGT","raise_target_eth":10,"token_price_eth":0.001,"min_commit_eth":0.01,"max_commit_eth":2,"durationHours":48}}'
# -> 402 + PAYMENT-REQUIRED header (x402 v2)
# agent signs permit2, retries with PAYMENT-SIGNATURE -> 200 + launchPayments are recorded as Payment records (pending → settled). The treasury address and facilitator endpoint are configured by the app owner via environment variables.