What you cannot do

The public API is deliberately scoped. These are not available with a customer service key:

• No fleet/admin operations. You cannot create, list, or manage runners or MT5 servers, view cross-account data, or read system logs. All /api/admin/* routes require the operator master key. Runners and servers are provisioned/assigned by Atlaas; instance creation auto-assigns an available runner.
• No account or billing control. You cannot create AtlasAccounts or add credits via the API — that's handled in the dashboard/billing. An account at 0 credits is suspended (401).
• No cross-tenant access. A key only ever sees its own account's instances, keys, and data. Requests for anything else return 404/403.
• No trailing stops over REST. Position modification changes SL/TP only. (Trailing-stop behaviour lives inside the MT5 EA, not as a public REST endpoint.)
• No pending-order price edits over REST. The modify endpoint sets SL/TP; it does not move a pending order's entry price.
• No batch order/close endpoints. Submit orders/closes individually.
• No trading on a non-running instance. Calls require the instance to be RUNNING with its runner connected, or you'll get 400/503.
• No reading a key's secret after creation. Only the prefix is retrievable; lost keys must be regenerated.
• Runner/EA endpoints are internal. /api/runner*, /api/runners/*, /api/runner-pairing/*, and the credential vault are machine-to-machine surfaces for the Atlaas runner daemon, not for customers.