BountEx Motion
Subscribe

Activation

Activate your license

Activation happens in the terminal, on the machine that will do the work. It takes one command, it claims one of your 3 device seats only if this machine does not already hold one, and it stores everything it needs in a single file with 0600 permissions.

Activate from the terminal

This is the real activation. It is also the one that can tell you whether a key is live, because it registers a device — which is exactly the thing a web form cannot do without quietly spending one of your seats.

  1. 01 Activate the key

    Sends the key once, registers this machine, and writes the credential file. If this machine already holds a seat, activation refreshes it instead of claiming a new one.

    $npx bountex-motion activate <license-key>

  2. 02 Install a kit into your tool

    Run it from the project the film is about. The installer detects your AI coding tool, verifies every file it writes, and records the receipt so an update can refresh it later.

    $npx bountex-motion install film

  3. 03 Start the workflow

    Open a fresh session in your tool and use its trigger — /bountex-motion in most of them. If anything is missing, doctor tells you what before the workflow does.

    $npx bountex-motion doctor

What the CLI writes to your machine

Path
~/.config/bountex-motion/config.jsonYour user config directory. The CLI creates it on first activation.
Permissions
0600Readable and writable by your user account only. Created that way, not fixed up afterwards.
What is inside
device id, per-machine salt, device tokenThe id is derived from your hostname and platform plus a random salt — never from a hardware serial or a MAC address.
What is not
an account, a password, a session cookieThere is no second credential anywhere. `bountex-motion logout` deletes this file and leaves the license itself untouched.

Your license key is a secret, and it is the only credential you hold. It is sent only to the activation endpoint and to the billing portal, it is never used as a bearer token, and the server stores a keyed hash of it rather than the key itself. Keep it in your receipt email and out of screenshots and support threads.

One license covers one subscriber and 3 devices. Running activate again on a machine you have already activated is free — the seat is matched on the device id, not on how many times you have run the command. If the seats are all taken, the CLI names the machines and gives you the one-line command to free one.

Coming back with a subscription that lapsed? Activate again once the payment is sorted: the same command, nothing to reinstall, and your project files were never touched.