MCP generate_video max_spend_usd for Wan 3.0: 480p, 720p, 1080p

For a Wan 3.0 call over the hosted MCP server, max_spend_usd should be the clip price: $0.625 for 10 seconds at 480p up to $7.50 for 30 seconds at 1080p. The server enforces the cap only when you send it, so an agent that omits it has no per-call ceiling.

Prices to put in the cap

Wan 3.0 is $0.0625, $0.125 and $0.25 per second at 480p, 720p and 1080p. The two durations below are the middle and the maximum of its 2 to 30 second range.

Preview first, then submit

dry_run: true returns an admission and cost preview and does not submit the job. Paid tools require idempotency_key. Read the exact payload fields with tools_schema for generate_video instead of guessing them; only payload.model is shown here.

{
  "idempotency_key": "wan-720p-demo-001",
  "dry_run": true,
  "max_spend_usd": 1.25,
  "payload": { "model": "wan-3.0" }
}

Limits and gotchas

Send max_spend_usd on every paid call, because it is optional and unenforced when missing. OAuth sessions need the Write toggle (mcp:write) to see the paid tools at all; a read-only session gets insufficient_scope. There is no mcp:paid scope.

• Omitting payload.model routes to sume/auto, so pin wan-3.0 when the price table matters.
• After submit, call jobs_wait with the job id; one call holds at most 55 seconds.
• Use a fresh idempotency_key per distinct clip.