Skip to article

Projects & save destinations

Select an existing project or use your default destination.

Choose where results are saved

Omit projectId to use the existing default project behavior. Supply an existing owned projectId to keep a generation with your game. Use folderId for a compatible existing folder, or null for the project root. Generation services validate ownership and destination compatibility.

Find a project

Call GET /api/v1/projects or MCP list_projects with tasks:read. Select an ID from the returned list. Follow pagination cursors when present. Do not infer ownership from an ID copied from another account.

Save a generation

Put projectId and optional folderId in the operation's input. The same destination participates in the idempotency fingerprint. Changing it after an accepted request creates different parameters, so an identical idempotency key will conflict.

Character destinations

A character belongs to a project and may impose its own destination. Use Character assets and actions before supplying character fields. The integration selects existing destinations; create, rename, delete and full project management remain workspace operations.