A marketplace bot is a creator's reviewed software configured through approved setup fields. You supply your Discord application and its token, choose the offered hosting configuration and manage the instance from your purchase library. Your own-code hosting dashboard has a separate workflow for uploading and editing projects.
1. Review the listing
Browse the bot marketplace without creating an account. Read the description, screenshots, creator information, setup instructions and the creator’s Discord support username. Check the one-time software price, required hosting tier and any paid external services before continuing.
The listing determines the hosting choices available for that release. A Free-compatible configuration may also offer Starter. Other configurations require their stated tier. Compare the plan limits and billing periods against those requirements.
New purchases and hosting depend on current listing and program availability. An unavailable action does not create a purchase or reserve hosting. You can still review listings and setup information that are publicly available.
2. Sign in and review the order
Use the listing's purchase or setup action to continue to the portal. Review the software charge separately from the hosting term. If the offer or approved release changed while you signed in, review the updated details before confirming.
If you already have hosting, read any reuse or replacement options the checkout offers. An occupied Free slot may need a separate replacement review. Keep your current bot and its data until you understand the proposed change.
Complete payment approval yourself when required. Returning from a payment page does not by itself prove that payment or setup has completed. Follow the order status and your purchase library for the next available step.
3. Create your Discord application
Follow the creator's setup instructions and use the Discord Developer Portal to create your application. Enable only the intents required for the bot's features, and invite it with the documented permissions.
Enter the bot token in the private configuration field. Keep it out of support messages, screenshots and public repositories. See tokens and environment variables for credential handling and replacement.
4. Complete the approved configuration
Open the instance from My purchases and fill in the required settings. These may include channel IDs, staff roles or credentials for an external service. The creator defines the supported fields; the platform controls runtime execution settings.
Managed marketplace purchases do not include the source-code editor, source download or ordinary own-code file controls. If you need to modify a program, review the source-code versus hosted-bot guide before choosing your product.
Save the configuration, start the bot when the control is available, and test its main workflow in a test server. For a ticket bot, check access using both a normal member and a staff role. A running process does not prove that channel permissions and features are configured correctly.
Manage hosting and support
Use the instance page to update allowed settings and start or stop your bot. Open the listing's support route when the supplied software behaves differently from its documented features. Share relevant nonsecret settings and a clear description of the problem.
Software purchases and hosting terms are tracked separately. Review the cancellation screen and purchase library for the effects of ending hosting, retained access and any supported rehosting choices. Do not assume that a stopped bot has canceled its paid hosting term.
For help choosing a product, use the buyer's checklist. For your own code, follow the ordinary hosting setup guide.
Still stuck? Contact support