Build with Corridor Key
Make your first request
Use your Sorceress API key on your server. The playground uses your signed-in account; your application uses the same model with an API key.
curl -X POST 'https://sorceress.games/api/v1/tools/corridor_key' \
-H 'Authorization: Bearer $SORCERESS_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"imageUrl": "<imageUrl>"
}'Inputs & settings
imageUrlstringRequiredhttps URL of a chroma-screen still (green or blue). e.g. images[0].url from image_generate, or a publicUrl from file_upload.
keyColorstring"auto" (default — detect green or blue plate from image borders) or a hex like "#00b140" / "#0040FF".
screenColorstringCorridor Key checkpoint: "auto" (default, from the detected/hex plate), "green", or "blue". Use when auto-detect is unsure.
tolerancenumberChroma distance tolerance for the alpha hint (default 80).
maxSidenumberMax working side before Corridor Key (512 = fast default, 1024 or 1536 = higher quality). Source is fit inside this box without upscaling.
labelstringOptional short label stored on the job / gallery row (e.g. filename).
Full input schema
{
"required": [
"imageUrl"
],
"properties": {
"imageUrl": {
"type": "string",
"title": "image Url",
"description": "https URL of a chroma-screen still (green or blue). e.g. images[0].url from image_generate, or a publicUrl from file_upload.",
"format": "uri"
},
"keyColor": {
"type": "string",
"title": "key Color",
"description": "\"auto\" (default — detect green or blue plate from image borders) or a hex like \"#00b140\" / \"#0040FF\"."
},
"screenColor": {
"type": "string",
"title": "screen Color",
"description": "Corridor Key checkpoint: \"auto\" (default, from the detected/hex plate), \"green\", or \"blue\". Use when auto-detect is unsure."
},
"tolerance": {
"type": "number",
"title": "tolerance",
"description": "Chroma distance tolerance for the alpha hint (default 80)."
},
"maxSide": {
"type": "number",
"title": "max Side",
"description": "Max working side before Corridor Key (512 = fast default, 1024 or 1536 = higher quality). Source is fit inside this box without upscaling."
},
"label": {
"type": "string",
"title": "label",
"description": "Optional short label stored on the job / gallery row (e.g. filename)."
}
}
}Results, saved runs & billing
Media requests return a job ID. Poll GET /api/v1/jobs/:id until it succeeds or fails; keep the same ID while it is processing. Long chat requests can also return a saved job to poll. Completed outputs are stored in your account, and successful work is billed using your model's current rates.
A multi-step workflow may include separately billed successful actions. If a connection drops, check your saved run before submitting it again.



