Personal Keys and disabling access
Manage account Keys, API permissions and personal credits.
What a Key does
Your personal .motion download includes your own account Key. After verifying the package and signed download receipt, official tools use that Key directly with MotionGit generation APIs. No separate Key file is needed. Different templates and updates reuse the same account Key, independent of the uploader. Requests follow its permissions, budgets and account status.
The first personal download initializes an account Key for an account without Keys. Existing permissions, budgets and disabled status are preserved. When the legacy server retained only a hash, one successful authenticated API request can encrypt and preserve your original Key; you can also restore it in account settings. With multiple Keys, select the one for future downloads. If the original is lost, explicitly revoke and replace it. Replacement is never automatic.
Disable or revoke
Open API & credits, find the account Key and choose Disable. Its Key inside downloaded packages then stops calling online APIs; you can enable it again. Revoking permanently disables the original Key. Old packages do not acquire a replacement automatically; download again. You can inspect permissions and set a monthly credit limit. Local source files and previously downloaded assets remain available.
Share the website template link so recipients download with their own Keys. Finished videos and exported project files contain no Key. Upload your author project package when publishing a template; personal download packages cannot be reuploaded directly. When asking for help, provide only the Key name and prefix.