| name | flaunch-web2-api |
| description | Integrate the Flaunch Web2 API to upload images, queue memecoin launches, poll launch status, and create treasury managers on Base and Base Sepolia. |
Flaunch Web2 API Skill
Use this skill when the user is integrating with flaunch-web2-api.
This skill is a router plus checklist. Use the reference that matches the API task.
What This API Is
This API is a backend wrapper around Flaunch flows. It adds:
- REST endpoints for launch/manager operations
- async queue processing (
jobId)
- launch status polling
- image upload + moderation + IPFS storage
- creator identity resolution (wallet/email/twitter/farcaster)
It is not a replacement for full SDK flexibility. For low-level transaction orchestration, use the SDK skill.
Supported Chains
- Base Mainnet route slug:
base (chainId 8453)
- Base Sepolia route slug:
base-sepolia (chainId 84532)
Core Endpoints
GET /livez
POST /api/v1/upload-image
POST /api/v1/{chain}/launch-memecoin
GET /api/v1/launch-status/{jobId}
POST /api/v1/{chain}/create-revenue-manager
POST /api/v1/{chain}/create-fee-split-manager
Route By Task
- standard token launch flow:
references/token-launch-flow.md
- fee split manager creation:
references/fee-split-manager-flow.md
- revenue manager creation:
references/revenue-manager-flow.md
- app-side launch, trade, liquidity, or watcher work: route to
../sdk/SKILL.md
Example Prompts
- Launch a token on Base through the Web2 API.
- Show me the Flaunch API flow for creating a fee split manager.
- What fields do I need for a revenue manager request on Base Sepolia?
Launch Request Essentials
Required fields:
name
symbol
description
imageIpfs
Creator identity options (pick one):
creatorAddress
creatorEmail
creatorTwitterUsername
creatorFarcasterUsername
Treasury options:
- Do not send conflicting manager options in one request.
- Fee split recipients are validated and resolved to wallet addresses.
Useful launch detail:
- optional social fields such as
websiteUrl, discordUrl, twitterUrl, and telegramUrl may be included when the launch surface supports them
- practical field limits commonly include
name max 32 chars and symbol max 10 chars
- image upload has format, size, moderation, and rate-limit constraints; see
references/token-launch-flow.md
Unsupported Fit
This skill is not the first choice when the builder needs:
- direct wallet-driven launches
- TypeScript SDK integration
- trade, liquidity, import, or event watcher flows
Route those requests to ../sdk/SKILL.md.
Manager Workflows
Create Revenue Manager
Route:
POST /api/v1/{chain}/create-revenue-manager
High-signal inputs:
- recipient identity (wallet/email/twitter/farcaster)
protocolFee in basis points (0 to 10000)
- optional owner override
Create Fee Split Manager
Route:
POST /api/v1/{chain}/create-fee-split-manager
High-signal inputs:
- owner identity (wallet/email/twitter/farcaster)
recipients array (wallet/email/twitter/farcaster entries)
- optional
creatorShare / ownerShare
- optional custom recipient
split values
Fee split constraints:
- max recipients limit applies
- if any recipient has custom
split, all must
- total recipient splits must equal
10,000,000 (100.00000%)
- duplicate resolved addresses are rejected
Async Job Semantics (Important)
- Launch is queue-based and asynchronous.
launch-memecoin returns quickly with jobId; it does not mean onchain completion.
- Poll status endpoint for final result.
- queue metadata such as position and estimated wait may be returned on submission
- Failed jobs may still include submitted tx hash context; instruct users to verify onchain.
Error and Retry Guidance
- Common error envelope:
{ success: false, error: "..." }
- Expect
429 rate-limiting; implement retry with backoff
- Moderation errors can include detailed NSFW payloads
- Route slug mismatch is common (
base-sepolia vs SDK baseSepolia)
Do / Don't
Do:
- Store and track
jobId
- Poll until terminal state
- Validate chain slug explicitly
- Surface
transactionHash and status to users
Don't:
- Assume synchronous launch completion
- Mix incompatible manager options in one request
- Assume schema file is always up-to-date with route implementation
Output Expectations
When helping builders, include:
- exact endpoint path
- required request fields
- async status handling using
jobId
- one error/retry pattern (
429, validation, failed job)
- expected success response fields (
transactionHash, collectionToken, manager addresses when applicable)
Related Skill
- SDK skill:
../sdk/SKILL.md