Create mascots and canvases

The Studio migration replaces the unused named character registry with mascots and independently owned canvases. Older CLI create, graph, run and hosted character commands call the retired registry and need a matching client update before they can be used against this backend. The matching local client provides masko studio METHOD path --file request.json --json, using your existing login. For example, masko studio GET mascots --json lists authoring mascots. Authentication and local playback commands remain separate.

Use the Studio REST migration guide for authoring, generation, checkpoints and complete releases. Check the target server OpenAPI before switching a production integration. Existing /v1/collections consumers continue through temporary compatibility routes with the same IDs and credentials.

For customer playback, retrieve one release’s signed delivery from your backend. See application integration. Do not put an authoring API key in a website or distributed app.