Using Parallax Background in your workflow
Sorceress brings this custom workflow into a shared API catalog. Select this model explicitly, check its supported inputs, and keep your API key on your server. Model capabilities differ; the schema and options on this page describe this entry rather than every model from the same brand.
- Convert a saved Parallax V2 scene into generated and keyed layers.
- Retain workspace metadata and download the resulting layer archive for your game.
Pricing and availability
Pricing varies by action and model; see the actions below. Successful work is billed in Sorceress credits. Defaults and optional inputs can affect the total.
Inputs and supported options
assetIdstring · requiredresolutionstring · optional1K, 2K or 4K
aspectRatiostring · optionalscreenstring · optionalgreen or blue
Workflow actions
Corridor Key green/blue-screen removal for any still image. Pass imageUrl, poll until succeeded, use transparentUrl. Same cloud GPU as /corridor-chroma. keyColor "auto" detects the plate. For AutoSprite videos use autosprite_key; for Parallax layers you may use this or parallax_key. Async — poll GET /api/v1/jobs/:id.
Same as UI Corridor Chroma stills: ~1 credit per image at ≤512px (2× above 512). VIP free. Charged only on success. Local GPU via sorcgcs-server is free.
Parallax Background agent guide: 4-layer roles, scene presets with ready prompts, green-screen/edge/seamless clauses, engine depth/composite hints, and Corridor Key vs classic chroma instructions. Synchronous / free. Call this first.
0 credits per successful call
Magic Prompt Helper: turn a scene idea into four Parallax layer prompts (Ground, Midground, Background, Foreground) with green-screen clauses baked in. Synchronous / free. Next: image_generate each finalized prompt, then parallax_key on slots 0/1/3.
0 credits per successful call
Corridor Key green/blue-screen removal for still Parallax layer images. DEFAULT after image_generate for Ground/Midground/Foreground — pass imageUrl, poll until succeeded, use transparentUrl. Do not key Background (slot 2). Prefer over DIY chroma unless the user asks. For general stills use corridor_key. Async — poll GET /api/v1/jobs/:id.
Same as UI Corridor Key stills: ~1 credit per image at ≤512px (2× above 512). VIP free. Charged only on success.
List Parallax projects saved in the website UI for this account (Project dropdown). Synchronous / free. Then call parallax_get with projectId or name to load full config + layer URLs.
0 credits per successful call
Load one saved Parallax project by projectId or name (e.g. "forest 2") — prompts, aspect, per-layer image/transparent URLs, scale/offset, BG-removal settings, engineHints. Same snapshot as the website Project dropdown. Synchronous / free.
0 credits per successful call
Convert a saved V2 reference scene into four matching layers, key the three foreground layers, save back to the same scene and export a ZIP. Persisted async workflow. Each successful image/key operation uses existing pricing; completed child jobs remain billed if a later step fails.
Four images at current model pricing plus successful keying operations; no additional orchestration charge.
Create an owned workspace in the V2 gallery.
0 credits per successful call
Save an image from your completed image job into a V2 workspace, with a gallery thumbnail.
0 credits per successful call
List saved workspaces and scenes from /parallax-v2 for this account.
0 credits per successful call
Load a saved V2 scene with its four generated layers, transparent URLs and placement settings.
0 credits per successful call
API request template
Replace placeholders and choose valid values from the input contract.
POST /api/v1/tools/parallax_v2_convert
Authorization: Bearer $SORCERESS_API_KEY
Content-Type: application/json
{
"assetId": "<assetId>"
}Completion, results and billing
Save the job identifier returned by asynchronous requests and poll the jobs endpoint until the job succeeds or fails. Do not resubmit a generation just because it is still processing. Chat returns a completed reply and usage details. A multi-step workflow can include separately billed successful steps even if a later step fails. Keep returned asset links with your project, and consult each action for its output format.
Coding agents can discover the current catalog and input requirements from the Sorceress agent instructions. Use a Sorceress key; provider credentials stay on the server.
