The creator workspace separates your public profile, a bot's editable draft, its submitted release and publication. Prepare a complete, testable release and explain what customers need to configure. Saving a profile or draft does not publish a bot.
Create your creator profile
Open the creator dashboard and choose profile setup. Enter a public creator name, a biography and a URL handle using lowercase letters, numbers and hyphens. The name appears on your listings, so use something buyers can recognize.
Confirm the age and program terms shown in the form. The initial creator program supports US creators aged at least 18. You can submit bots, publish after review and accumulate earnings without a Stripe payout account. Complete the dashboard's hosted Stripe setup when you are ready to withdraw. Identity verification and payout eligibility are required before money can be transferred; changing a profile field cannot supply that verification.
Profile saving remains available during a submission pause. Listing creation, review submission and publication depend on the current program's available actions. A completed profile alone does not enable sales or payouts.
Prepare the project before uploading
Test the bot in a fresh Discord server with a clean configuration. Include its entry file, declared dependencies and any required local modules in the source package. Remove installed dependency directories, development caches, real user data and credentials.
The current marketplace editor supports Node.js and Python. Choose the runtime and entry file that match the tested project. For other own-code hosting workflows, see supported runtimes.
Check your rights to publish hosted copies of the code and assets. Preserve required dependency notices and describe the customer's hosted-use rights clearly. Review Discord's Developer Policy, including applicable monetization requirements.
Complete the listing draft
Provide a specific name, a short summary, a full feature description, a category and relevant tags. Upload an icon and screenshots that demonstrate the actual workflow. Keep credentials and personal information out of public images.
Upload the private project ZIP using the Source upload purpose. Source uploads are separate from the public listing images. Include everything needed to reproduce the intended deployment without your personal development environment.
Set the hosting configuration and declare any required paid external service. Explain external costs in the listing so buyers can compare the full operating cost. The configured hosting tier should match the release you tested.
Define the buyer's setup fields
Declare the settings a customer needs, such as role IDs, channel IDs or an external API credential. Give each field a useful label, a clear explanation and the appropriate type. Required fields and secret fields should match the program's actual requirements.
The Discord bot token is collected by the configuration workflow. Keep real tokens out of defaults and example values. Runtime commands, dependency settings and execution options remain platform-controlled; buyers configure approved fields rather than editing your source.
Use the customer-form preview to check that someone unfamiliar with the code can understand every setting. The buyer setup guide shows the workflow those instructions need to support.
Add pricing, instructions and support
Set the one-time software price and review the displayed amount. Hosting is billed separately. Explain the complete setup sequence and state the hosted deployment rights or license. Your linked Discord username appears automatically as your public support contact on bot listings. Check it in the listing preview and manage the connection in Account settings.
Describe the support you can provide and any important limitations. The creator dashboard explains current earnings rules, eligibility and payout status. Recorded earnings, amounts on hold and amounts available for payout are separate figures.
Preview and submit the release
Save the draft, preview its listing and select the source upload that belongs to this version. Review the screenshots, setup fields, hosting requirement and support information together before submitting the current revision when submission is available.
Independent review can request changes or leave a release awaiting publication readiness. Follow the private feedback and submit a consistent updated release. Publicly visible listings must correspond to the reviewed version; a saved edit is not automatic publication.
Read the guide to selling a Discord bot for packaging and support planning, and use the buyer's checklist to check whether your listing answers a customer's practical questions.
Still stuck? Contact support