Launch a Token with a Custom Quote

A custom quote is the asset your token trades against and pays fees in. This guide starts your token on a DBC bonding curve with a Bags Fee Share config for up to 100 recipients. When the token graduates to DAMM v2, the same Fee Share configuration continues to distribute fees in that quote asset. The steps are: select a supported quote, create metadata, configure recipients, then build and confirm the bonding-curve launch.

Prerequisites

Before starting, make sure you have:

An API key from the Bags Developer Portal.
A Solana wallet with SOL for transaction fees, rent, and applicable reimbursements.
A quote with an available DBC configuration in Supported Custom Quote Tokens.
A balance of that quote token if you want an initial buy. You can also omit the buy.
A signer and RPC connection that support the requested transaction format. The examples request v0.

The examples below use the HTTP API so the request fields and response envelopes are explicit. Replace uppercase placeholders with your own values. Every request uses the base URL https://public-api-v2.bags.fm/api/v1 and the x-api-key header.

1. Pick a Quote and Configuration

Fetch Supported Custom Quote Tokens with flow=dbc:

curl 'https://public-api-v2.bags.fm/api/v1/token-launch/supported-quote-tokens?flow=dbc' \
  -H 'x-api-key: YOUR_API_KEY'

Inspect response.tokens and the flow: "dbc" entry in each token’s flows array:

asset.mint and asset.tokenProgram identify the quote. Keep both when constructing requests.
asset.decimals describes raw units; do not assume nine decimals when it is unavailable.
profileEligible describes the mint’s current compatibility with DBC.
launchAvailability.status must be "available"; inspect reason otherwise. Catalog inclusion alone does not guarantee that the mint is currently usable.
configs lists the available configType values and their graduationThresholdRaw. Select one entry and pass its configType as bagsConfigType when creating the Fee Share config.

For example, a DBC flow entry can contain these configurations. This is an illustrative fragment, not a live quote listing:

{
  "flow": "dbc",
  "profileEligible": true,
  "reviewedForLaunch": true,
  "launchAvailability": { "status": "available" },
  "configs": [
    {
      "configType": "fa29606e-5e48-4c37-827f-4b03d58ee23d",
      "graduationThresholdRaw": "85000000"
    },
    {
      "configType": "d16d3585-6488-4a6c-9a6f-e6c39ca0fda3",
      "graduationThresholdRaw": "170000000"
    }
  ]
}

Each non-WSOL quote and configuration type must first be saved by a Bags administrator. reviewedForLaunch is retained for compatibility and marks a built-in or admin-configured entry; use configs and live availability to make your selection. graduationThresholdRaw is a decimal string of raw quote units, not a USD amount. For a six-decimal quote, "85000000" represents 85 unscaled quote tokens. An issuer’s display multiplier may change the displayed quantity. Bags admins set this threshold; public config and launch requests do not accept a threshold override. For custom quotes, the selected type keeps its base-token supply, trading fee rates, liquidity distribution, vesting, and fee scheduler. Fees are collected only in the quote token before and after graduation, with no fee compounding, including types whose names contain “Compounding.” See Customize Token Fees for the supported types.

2. Create Token Metadata

Use the existing Create Token Info endpoint:

curl -X POST 'https://public-api-v2.bags.fm/api/v1/token-launch/create-token-info' \
  -H 'x-api-key: YOUR_API_KEY' \
  -F 'name=My Token' \
  -F 'symbol=MTK' \
  -F 'description=A token with shared quote fees' \
  -F 'imageUrl=https://example.com/token.png'

Save response.tokenMint as TOKEN_MINT and response.tokenMetadata as METADATA_URI. Create the Fee Share config before launching this mint. The launch’s metadata URI must fit within 200 UTF-8 bytes. Call Create Custom Quote Fee Share Config Plan. This example selects the Default configuration and allocates the entire normal recipient pool to your wallet. Use the configType you selected in step 1 as bagsConfigType:

curl -X POST 'https://public-api-v2.bags.fm/api/v1/fee-share/config/v2' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'content-type: application/json' \
  -d '{
    "baseMint": "TOKEN_MINT",
    "payer": "YOUR_WALLET",
    "admin": "YOUR_WALLET",
    "flow": "dbc",
    "quoteMint": "QUOTE_MINT",
    "quoteTokenProgram": "QUOTE_TOKEN_PROGRAM",
    "bagsConfigType": "fa29606e-5e48-4c37-827f-4b03d58ee23d",
    "claimersArray": ["YOUR_WALLET"],
    "basisPointsArray": [10000],
    "transactionFormat": "v0"
  }'

Set flow to dbc and keep the same quote for the later launch request. Omitting bagsConfigType selects Default. The exact quote/Default entry must exist; the server does not fall back to another configured type. Default uses a one-billion-base-token supply; the Default with 1K Supply type uses 1,000 base tokens. Normal recipient allocations must total 10,000 BPS, with 1–100 unique recipients. They divide the recipient pool after platform, partner, and deployer deductions. To include a partner, pass both partner and its matching partnerConfig. Set admin to the intended config manager, especially when sharing fees among multiple recipients. The config response contains:

Field	What to do with it
`needsCreation`	If true, execute the returned config plan before launching
`plan`	Follow Transaction Plans; this field is null when creation is already complete
`feeShareConfig`	Save as `FEE_SHARE_CONFIG` for the launch request
`meteoraConfigKey`	Save as `DBC_CONFIG_KEY` for the bonding-curve launch
`asset` and `flow`	Verify the selected quote and `flow: "dbc"`

Config plans may contain multiple stages. Confirm them in order. If lookup-table setup is required, complete that setup and fetch the plan again with its lookup-table addresses as described in the transaction-plan guide. Setup confirmation alone does not mean the config is ready for launch. The issued config keeps a snapshot of its launch parameters. Later admin changes to the quote’s configuration affect newly issued configs only. Continue an interrupted launch with the original request and returned config addresses; a refreshed discovery listing does not replace its issued terms.

4. Build the Launch Plan

After config creation is confirmed, call Create Custom Quote DBC Launch Plan:

curl -X POST 'https://public-api-v2.bags.fm/api/v1/token-launch/create-transaction/v2' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'content-type: application/json' \
  -d '{
    "tokenMint": "TOKEN_MINT",
    "wallet": "YOUR_WALLET",
    "feeShareConfig": "FEE_SHARE_CONFIG",
    "configKey": "DBC_CONFIG_KEY",
    "quoteMint": "QUOTE_MINT",
    "quoteTokenProgram": "QUOTE_TOKEN_PROGRAM",
    "ipfs": "METADATA_URI",
    "initialBuyQuoteRaw": "0",
    "transactionFormat": "v0"
  }'

configKey is the meteoraConfigKey returned by config creation, not the Fee Share config address. This launch starts on DBC and retains its Fee Share configuration after graduation to DAMM v2. initialBuyQuoteRaw is a decimal string of raw quote units, not SOL lamports or a floating-point token amount. The examples perform no initial buy. To buy, supply a positive raw amount backed by your wallet’s quote balance; Bags does not automatically swap SOL into that quote.

Token decimals and issuer display multipliers are different. For scaled or interest-bearing assets, raw units divided by decimals may not equal the official displayed quantity. Keep raw accounting exact and use verified display information when presenting token amounts.

5. Sign, Send, and Confirm

The launch endpoint returns the plan directly as response, whereas config creation wraps it in response.plan. Follow Transaction Plans to preserve server signatures, respect stage dependencies, and handle lookup-table readiness. Save the base mint, config addresses, request, and each transaction signature. If submission becomes uncertain, reconcile the original signature and on-chain state before requesting a replacement. Do not rerun metadata creation to resume an interrupted launch. After confirmation, use Claim Custom Quote Fees for recipient, holding, and shared role balances. Fees remain in the original quote asset, subject to its token transfer fees; no automatic SOL or USDC conversion takes place.

6. Update Recipients Later

The config manager can call Create Custom Quote Fee Share Config Update Plan with baseMint, payer, claimersArray, and basisPointsArray. This also returns a plan directly as response. The update changes recipient allocations while preserving the quote asset. Unpaid recipient entries must be settled before removal. Holding balances remain withdrawable by their owner after removal from the config. Follow the returned stages without skipping lock, update, or finalization steps.

Troubleshooting

Issue	What to check
Quote unavailable	Check the current DBC profile and launch availability
`quote_not_reviewed`	No saved entry matches this quote and `bagsConfigType`. Select a returned configuration or ask Bags to configure the pair. Omission selects Default, not any available type.
Unsupported config type	Use a type returned in `configs`; the 85% supply-locked type is unavailable for custom quotes
`setup_required`	Confirm setup, wait for lookup-table readiness, then refetch; do not treat it as a completed launch
`insufficient_quote` or `insufficient_sol`	Quote funding and SOL funding are separate requirements
`fee_limit_exceeded`	Review the changed token fee before approving a new bound
`pending_reconciliation`	Resolve the previous issuance or submission before building a replacement
Restricted asset	Freeze, pause, or other transfer restrictions can prevent execution without changing fee entitlements

Getting started

CLI

How-to Guides

Core Principles

Robinhood Chain

Robinhood Chain Guides

Robinhood Chain Reference

Prerequisites

1. Pick a Quote and Configuration

2. Create Token Metadata

4. Build the Launch Plan

5. Sign, Send, and Confirm

6. Update Recipients Later

Troubleshooting

Endpoints Used

​Prerequisites

​1. Pick a Quote and Configuration

​2. Create Token Metadata

​3. Create the Fee Share Config

​4. Build the Launch Plan

​5. Sign, Send, and Confirm

​6. Update Recipients Later

​Troubleshooting

​Endpoints Used

Prerequisites

1. Pick a Quote and Configuration

2. Create Token Metadata

3. Create the Fee Share Config

4. Build the Launch Plan

5. Sign, Send, and Confirm

6. Update Recipients Later

Troubleshooting

Endpoints Used