Documentation

Core operating guidance for worker, private, affiliate, and deployment flows.

Operational docs

Use the right system, key type, and command surface from day one.

MuskServices DTA is split into worker and private lanes. Worker mode is operator-managed. Private mode is credit-managed and export-enabled. Affiliate tracking is layered on top, not mixed into core generation permissions.

Quick Start

Use this order to avoid avoidable misconfiguration.

  1. Choose the correct lane: worker or private.
  2. Receive the correct key type: `OPT-...` for worker, `PRV-...` for private.
  3. Set the generator config mode accordingly.
  4. Set `ip_rotation` to `adb`, `vpn`, `proxy`, or `none`.
  5. Validate the key before generation starts.
  6. For private mode, ensure the key has credits before running.

Mode Reference

The product separates business logic from network-rotation logic.

System Mode
`worker` or `private` decides where generation results are routed and what permissions apply to the user.
IP Rotation
`adb`, `vpn`, `proxy`, or `none` controls the network strategy independently of system mode.
Worker Key
`OPT-...` keys are operator-managed and do not grant self-export rights.
Private Key
`PRV-...` keys are credit-backed and allow the owner to export their own EVs.