# What UpScalp Does and Does Not Automate

**Last reviewed:** 2026-05-22.

UpScalp does not automate the same things in every product path. Read this before assuming a signal, guide, or trading principle means the product will take action for you.

## Lite and Premium are decision-support paths

For Lite and Premium, treat UpScalp as signal delivery and decision support.

That means UpScalp can help you:

1. See structured setups.
2. Read entry, stop loss, and take-profit levels.
3. Check context before entry.
4. Decide whether to act, wait, or skip.

Lite and Premium do not automatically place trades for you.

## Private Beta API is a controlled path

The API path is a controlled Premium Holder Private Beta for approved users.

It may support exchange-connected actions only where the approved beta product path explicitly supports them. Do not assume API behavior from Lite, Premium, or education pages.

If API access has not been approved for you, treat API behavior as unavailable. Do not create exchange API keys before approval, and never enable withdrawal permissions for any exchange connection.

## When API is mentioned in public docs

Public Help Center pages may mention API access to explain boundaries. That does not mean API access is open to every user.

| If you see this                 | Treat it this way                                                                               |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| Lite or Premium signal guidance | Manual decision support. No automatic trade placement.                                          |
| Private Beta API wording        | Approved-user-only context. Wait for explicit approval.                                         |
| API-key safety warning          | A protection rule, not an instruction to create a key.                                          |
| Automation example or doctrine  | Educational context unless the page says it is current approved product behavior for your path. |

If a page or message makes API setup look self-serve, stop and verify through the official Access Bot or support route before taking action.

## Education is not automation

Some pages explain trading doctrine:

1. Partial profit.
2. Breakeven protection.
3. Skip rules.
4. Risk sizing.
5. Context checks.

Those pages explain how to think. They do not prove that every product path performs those actions automatically.

## Automation still has risk

Even when an approved beta workflow automates an exchange action, automation does not remove:

1. Market risk.
2. Execution risk.
3. Slippage and fees.
4. API setup risk.
5. The need to understand what the product is allowed to do.

Never treat automation as a guarantee.

## Check the page type before relying on behavior

Ask:

1. Is this page teaching a principle?
2. Is it explaining signal interpretation?
3. Is it describing current product behavior?
4. Is it for approved beta users only?

If the page is not explicitly a current product-behavior page for your path, assume it is guidance, not automation.

## Related

1. [How to Complete UpScalp Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)
2. [Partial Profit and Breakeven in UpScalp Trading](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-partial-profit-and-breakeven)
3. [UpScalp Legal Notice and Trading Risk Disclosure](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-legal-and-risk-notice)
4. [How to Protect Your UpScalp and Exchange Accounts](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-security-and-account-protection)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.