Skip to main content
API jobs use the API key owner’s Motion credits. The full and directory MCP profiles support balance tools, hosted credit checkout, and browser links for subscription and auto top-up settings. Users complete purchases and save recurring billing changes in the browser. The OpenAI profile uses its sponsored generation flow and exposes no billing tools.

Managing credits

Purchase credits and configure auto top-ups in the Motion web app: Open motion.so Flex packs and standard manual top-ups cost $6 per 200 credits (3¢ per credit). Pro offers monthly bundles from 1,000 to 50,000 credits, with monthly or annual billing. Video cost depends on the engine, effort, length, generated media and follow-up edits. Existing subscriptions retain their saved allowance, price and billing interval. Automatic top-ups use the account’s saved prepaid rate; manual top-ups use the displayed offer. Enterprise rates may be negotiated. MCP clients should read current.topup_offer from get_credit_balance before purchase_credits and use its minimum, increment and quoted price. The REST video API does not purchase credits or change automatic top-ups. Use Motion billing, or the browser links returned by supported MCP billing tools.

How credits apply to API jobs

Every public API job is owned by the user who created the motion_ API key. Credit checks and usage are applied to that user’s Motion account. A job can pause with status: "awaiting_user_input" and insufficient_credits: true. Add credits, then send a follow-up to the same job. Credit-pause resumes recheck engine access and settle outstanding usage before continuing.

Insufficient credits response

A follow-up that tries to resume a credit-paused job without enough credits returns HTTP 402:
Add credits in Motion or through your connector’s supported billing tools, then retry the follow-up on the same job.

Organization work

For a workspace-scoped API key or OAuth connection, the billed customer is the workspace’s organization. The credential owner remains the initiator. Personal keys keep personal billing. Changing the browser’s workspace selection does not reassign earlier API jobs or their charges. Organization, workspace and member limits can prevent admission even when a balance is available. See Organization billing and limits.