Backend mascot integration

Use a workspace API key from your backend to work with mascots and canvases. Keep the key on your server. Your application authenticates its own customers and delivers only the media they are entitled to use.

The earlier developer character registry and temporary character playback URL interface are retired in the Studio migration. Existing application records and credentials are retained, but new integrations should use the canonical REST contract. Installed Desktop packages and their pinned runtime releases are unchanged.

See the Studio migration guide and your server's OpenAPI specification for current availability. A purchased mascot library provides licensed identities and assets; it does not promise an included playable canvas.