> For the complete documentation index, see [llms.txt](https://www.degenbot.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.degenbot.wiki/help-and-account/frequently-asked-questions.md).

# Frequently asked questions

Straightforward answers to the questions new members are most likely to ask.

### Does Degen trade automatically?

The product covered by this guide is alerts-only. A LONG or SHORT notification does not place, manage, or close an order. Earlier Ninja Bot pages describe a different product scope.

### Do I need an exchange API key or a funded account?

Not to read alerts from the hosted alerts-only service. Do not grant trading or withdrawal permissions to activate notifications.

### Do I have to install the code or keep my computer on?

You do not need to self-host the service to use the hosted Telegram bot. You need the appropriate access and a way to read messages. Running the code is an operator task, not member onboarding.

### Is 1m LONG+SHORT a one-minute trade?

Not necessarily. A timeframe label is not the same as the outcome window. Read the actual horizon and rules in the release.

### Does Fast Move always predict a move before it begins?

Do not assume that. Read the event and send times and whether the message describes an early condition or movement already observed. A move reported after it began is not an advance prediction of the entire move.

### Is Consensus always more reliable?

Its name does not establish that. Compare the defined task, version, sample, and baseline. Several related inputs can agree without providing independent confirmation.

### Does an 80 confidence score mean an 80% chance of success?

Only if the method explicitly establishes that probabilistic interpretation. Otherwise it is a score, not a calibrated probability.

### Where do I see results?

Use `/performance` in the private bot conversation. Read the period, method, eligible sample size, and scoring rules alongside the percentages.

### Does a 70% accuracy mean I will make money?

No. Accuracy describes the outcome definition used by the report. Returns also depend on the size of gains and losses, timing, execution, and costs. The arithmetic example in **Accuracy, null, and edge** shows the distinction.

### Why did I get no alerts today?

The conditions may not have qualified, preferences or access may restrict delivery, or a service issue may exist. Check a fresh request and any service notice; silence alone does not identify the cause.

### Why did two streams disagree?

They may use different conditions or horizons. Compare the instrument, observation time, version, and evaluation window. Report an apparent contradiction that remains after those checks.

### Can I change which markets or streams I receive?

Use the preferences actually offered by your release. Selecting a market for analysis does not necessarily filter automatic alerts. This draft does not promise a particular filter.

### Why is my bot different from the old guide?

The current guide concerns an alerts service. The legacy archive preserves an earlier execution-focused bot. Use the live interface and current release documentation instead of archived trading instructions.

### Does muting Telegram stop billing?

No. Manage cancellation through the provider that charged you. See **Billing and cancellation**.

### How do I get help?

Use the support route in the verified bot or purchase account. Include the exact issue, time and timezone, relevant message reference, and a redacted screenshot. Never include secrets or login codes.

### Where is the official bot link?

Use the access link attached to the verified product or onboarding. The exact official URL still needs owner verification in this draft; the guide deliberately does not guess a username.