Photo dance via hosted MCP: kling-motion-control_create needs a key

Sume's hosted MCP lists kling-motion-control_create among its paid generation tools, so an agent in a client such as an IDE can make a still copy the movement of a driving video. Like every paid tool it requires an idempotency_key, and an 8-second driver costs 8 x $0.1575 = $1.26.

What the docs say

The MCP tools and gates page groups kling-motion-control_create with the other paid generation tools: generate_image, generate_video, music_create, tts_create, stt_create, image_upscale_create, rmbg_create and video_upscale_create. For paid tools, the idempotency_key is required, and it is a stable key for transport and dedup, not human approval.

Why the key matters

Agents retry. If the client times out after Sume accepted the call, a retry with a new key would start a second job and a second reservation. A retry with the same key is deduplicated. For a 30-second driver the difference is $4.725 per mistaken repeat, so have the agent derive the key from the still URL, the driver URL and the length, rather than invent one each time.

Who approves the spend

The docs say the key is not human approval. Wallet and admission rules still apply, so the balance must cover the reservation. If you want a person to confirm each paid call, set that up in the client's tool-approval settings, since the key does not do it. Hosted MCP also cannot read files from your laptop; upload the still and the driver first, then pass their public HTTPS URLs.

A safe agent recipe

Give the agent a short instruction: upload the still and the driver, measure the driver, build the idempotency key from the three, call the tool once, then wait for the job. If the call times out, the agent should repeat the same call with the same key, not a new one.

Set a spending guard in your own client: refuse any driver over 10 seconds without asking you, which caps the call at 10 x $0.1575 = $1.575. The MCP gate does not do that for you.

Reading the result uses the same job pattern as the REST API: status, then result, with Sume-hosted artifacts.