Assets and actions have different destinations
An existing character can receive compatible generated design assets or animation actions. Asset targets identify a slot; action targets identify an existing action and any required directional context. These fields are part of each business input Schema.
Select an existing character
Call GET /api/v1/characters or list_characters with tasks:read, optionally filtering by project. Use the returned character and action IDs. Inspect the operation Schema for characterTarget variants instead of inventing a target object.
Archive a result
- Select an existing character in the workspace or list it through the integration.
- Choose a compatible asset slot or existing action.
- Supply both
characterIdandcharacterTargetwith the generation input. - Query the original task until the generation and asset processing finish.
- Review the saved result in the character workspace.
Animation operations require action destinations; they do not accept design asset slots. Direction generation checks the character's current design and direction mode. If the character changes while you are preparing a request, refresh its data and resolve the conflict before generating.
Scope of this integration
NPC generation creates a cast in a project and does not create character records. Full character management and version adoption are not exposed. Generated files remain searchable and reusable through their asset IDs.
