aicut-motion-control
Make a character from a picture copy the motion of a reference video (a dance, a walk, a gesture) with the aicut CLI (aicut transform motion-control). Use when the user wants to animate a character picture with the movement of another clip.
Copy a video's motion onto a character
Make a character from a picture copy the motion of a reference video with the aicut CLI: price the motion transfer by the clip's length, ask, run it and wait.
Setup
Check the CLI first: aicut --version. If the command is missing, install it with npm i -g aicut-cli (Node 20 or newer), then sign in with aicut login: it opens the browser and the user approves. aicut account shows who is signed in and the token balance. More in references/setup.md.
Never read the CLI's credentials file and never run aicut token: the CLI looks after its own session.
Spending tokens: the rule
Creating video, images and audio costs tokens from the user's aicut balance. Every command that spends can price itself first. The flow, every time:
- Run the command with
--estimate. It prints the price and charges nothing. - Tell the user the price and what it buys, in the same message as your ask, and wait for their explicit go for THAT purchase. A bare "yes" counts only as the direct answer to your priced ask, with nothing else raised or outstanding; if it is ambiguous, ask which purchase they mean.
- Only after the go, run the same command with
--max-tokens <quote> --yes, where<quote>is the price you told them.
Without a terminal (you, a script, CI) --max-tokens on its own is already a go: the command spends as soon as the quote is within the number. So never put --max-tokens on a command before the user has said go. --yes only skips the y/N question, and only together with --max-tokens.
Two steps need more than a go:
aicut story firegenerates every scene video and cannot be undone or refunded. It needs a go that NAMES firing ("fire it"), given in reply to an ask about firing alone, and then--confirm-fire --max-tokens <quote> --yes. A bare "yes" never fires.aicut post publishputs a post live under the user's name. It needs a go that NAMES publishing, and then--confirm-publish.
A go covers one purchase at the price you quoted. If anything changes (the model, the length, the text, a setting) estimate again and ask again. A retry after a failure is a new purchase: new estimate, new go. But a paid command your shell cut off may already be charged, so never run it again: find the job (aicut list videos|images|audio, or aicut story get <id>) and follow it with aicut wait <id>. Never switch to a cheaper model or lower settings to save tokens without saying so. Pictures of real people only with their permission, never public figures. When a price is more than the balance the command refuses and prints a top-up link: give it to the user and stop.
The flow
MOTION CONTROL: make a character from a picture copy the motion of a reference video (a dance, a walk, a gesture).
This text is a guide, not the user's go. It authorizes no spend: the paid call below is priced first and made only after the user's go for that purchase.
- Run
aicut accountto see the balance. If it is 0, the account has no tokens: tell the user so, give them https://www.aicut.pro/billing, and stop until they have added some. Price nothing first. (A price above the balance is refused later with the same link: give it to the user and stop.) - Ask the user for two things and nothing else: the picture of the character, and the video whose motion to copy. The clip supplies the movement only; the character comes entirely from the picture. The clip must be 3 to 30 seconds (10 if the picture is a still portrait), and each may be a URL (public https, or from an earlier generation) or a file on their machine (below). CONSENT: only a picture of the user, of someone who gave their permission, or of a fictional or AI-generated character; never a real person without their permission, and never a public figure or celebrity (decline and offer a generated character). A file on the user's own machine: pass its path where the flag takes a URL (for example
--character ./photo.png); the CLI uploads it first and uses the finished url. A file that is already a URL needs no upload. - Pick the model:
kling-2.6-motion-controlis the everyday choice,kling-3.0-motion-controlis better and about four times dearer. Name both with their price in the ask and let the user choose; never pick the dear one for them.--resolutionis required: use720punless the user asked for1080p, and name the choice.--character-orientationisvideo(the default) for a full-body or moving subject andimagefor a still portrait. - Price it:
aicut transform motion-control --model <id> --character <file or url> --motion <file or url> --resolution 720pwith--estimate. There is no length flag: the server measures the clip and the price is its length times a per-second rate (a 30-second clip costs ten times a 3-second one). A local file is uploaded first, even with--estimate(it costs no tokens), because the server measures what it prices. A clip it cannot measure is refused with nothing charged: re-encode it to MP4. An external URL costs one media-ingest slot, so quote and create from the SAME URL. Say the price and what it buys in ONE message, ask, and wait for the user's go for this purchase. - After their go, run the same command again with
--max-tokens <the price you quoted> --yes --wait. Never put--max-tokenson a command before that go: without a terminal it is itself the go.--waitblocks until the job is done (up to 10 minutes) and prints the media url; add-o <path>to save the file too. If your shell tool cuts a command off sooner than that, leave--waitoff from the start: the command prints the job id, then runaicut wait <id> --timeout 90again until it prints the url (exit code 3 means still running, not failed). If a run that had--max-tokensis cut off, NEVER run it again: the job exists and is charged, so find it withaicut list videos|images|audioand follow it withaicut wait <id>. - Tell the user the media url and one line about the result.
If the job fails, read its error: line and tell the user what went wrong. Any resubmit is a new purchase with its own price and go, and never the identical request twice: change the model or the prompt, or ask.
References
references/setup.md: install, sign in, output and exit codesreferences/spend.md: how the spend guard decides
- Downloads
- 67All time
- Security audit
- Pass
- Last updated
- 3d ago
- Current version
- v1.0.0
- License
- MIT-0
