Skip to navigation

Submit a bot

What reviewers check, the five review stages, and how to get approved faster.
View as Markdown

FluxerList is the bot directory for Fluxer. Before your bot goes live it goes through a structured review to confirm it works on Fluxer and is safe for communities to add.

Core requirements

Prefix-based commands

Your bot must use prefix commands, for example !command or .help.

A valid OAuth2 invite

The invite URL must look like fluxer.app/oauth2/authorize?client_id=…&scope=bot&permissions=….

Permissions match usage

Request only what your bot uses. Requesting Administrator (bitfield 8) needs a documented reason.

Responds in 3 to 5 seconds

Commands must answer within 3 to 5 seconds under normal conditions.

Review stages

1

Submission

Your bot enters the queue and a reviewer is assigned.

2

Initial review

Reviewers verify your invite link, description, tags, and basic submission details.

3

Testing

Your bot is added to a private Fluxer test community, and reviewers verify every command, permission, and behaviour.

4

Approved

Your bot is listed publicly on FluxerList. Approval earns you 5 FL Tokens.

5

Monitoring

Approved bots can be reported. Reviewers monitor for terms violations and may delist if issues arise.

Bot reviews typically take 2 to 5 days. You can submit up to 5 bots per account. Your submission also needs to disclose what data your bot collects - see the Bot Guidelines for exactly what to state.

Open source bots

If your bot is open source, link its GitHub repository in your submission. Reviewers verify gateway and connection behaviour directly from the source, which can speed up testing. Closed source bots are reviewed through behavioural testing only and take longer.

Co-developers and server counts

Add up to 5 co-developers to your listing. They can edit it on your behalf and can also use their own API keys to push your bot’s server count.

Tips to get approved faster

  • Write a detailed long description with every command, what it does, and any setup steps.
  • Request only the permissions your bot needs. Over-requesting is a common rejection reason.
  • Fill in every optional field honestly. A complete submission signals a trustworthy developer.
  • Keep your bot online and reachable while it’s in review. An offline bot can’t be tested.
  • Name every external service in the External APIs field.
  • Respond promptly to change requests. Unactioned submissions may be closed after 14 days.