Manage your account and connected access

Check the account actually being used

Open Account Center and verify the signed-in email, verification state, subscription, and credit balance. A browser session and an AI client's OAuth session can belong to different accounts.

If you have more than one sign-in method, confirm they lead to the intended account before buying credits or reconnecting a client. Do not assume matching display names mean matching identities. Use only the account-linking controls offered by the product.

Account verification, active subscription, export entitlement, and available credits are separate checks. See credits and access.

Review billing without confusing cancellation and deletion

Account Center shows the current subscription and billing-period information. Use its subscription-management link when available for that billing provider.

A cancellation scheduled for the end of a billing period is not the same as immediate account deletion. Check the displayed effective date and status instead of assuming access has already ended. Credit packs do not create a recurring subscription or a higher storage tier.

Before reducing a plan, inspect stored usage and download important assets. Do not rely on the website as your only backup.

API keys belong in trusted environments

Create and manage keys in Account → Developer. Give each integration the minimum scopes it needs, store its secret outside client-side bundles, and revoke unused or exposed keys.

Never paste a key into prompts, screenshots, documentation feedback, source control, or a support email. Do not use the website's login token as a public API key.

After an uncertain paid request, rotating to another key changes the idempotency identity. First reconcile the known task or request rather than blindly resubmitting through the new key. Read safe retries.

MCP uses OAuth grants, not copied API keys

The official remote MCP is available in public beta. Connect through its client setup guide and review the requested scopes on the AnimGen authorization page.

In the developer account area, review connected MCP applications and revoke access you no longer need. Remove a disconnected client's local configuration separately if you no longer use it. Revoking an OAuth grant does not cancel a job already submitted or refund completed work.

Authorization grants capabilities; it does not approve every future charge. Require a concrete request, quote, and approval before paid generation.

If access looks compromised

Stop using the affected integration, revoke the exposed key or grant, and review your recent task and billing activity. If there was an ambiguous paid submission, retain its task ID for reconciliation.

Contact support with a concise issue description and relevant times. Provide private identifiers only through an appropriate private support channel; omit tokens, signed URLs, passwords, and raw payment details.