Concurrent Submit | OpenAI Sora API Plus节点

OpenAI's Sora, through a reseller, in a ten-wide video queue. ComflyConcurrent_OpenAI_Sora_API_Plus_Submit is the Plus Sora node of the pack - the tier that adds hd and 15-second durations - wrapped into the shared 10-slot video pool.

The pack's history here is a soap opera, and it's genuinely useful context. The README documents Sora 2 as OpenAI's perpetually flaky product: 500 errors that are usually OpenAI's fault (just re-run), throttled groups, "sora-vip" token groups being the only reliably working lane, watermarked drafts, and node timeouts that don't mean the job failed. "Plus" was the version the author added for the four newer models with HD and 15-second support. You're not just using a node; you're riding the openai risk-control rollercoaster through a middleman.

How it works - and the quirk

Despite the name, this node doesn't call a Sora-specific endpoint. It hits {base_url}/chat/completions with stream: true - an OpenAI-compatible chat streaming call - and parses the video URL out of the streamed content, then downloads and converts it. The base_url defaults to https://ai.t8star.org/v1, the overseas store's OpenAI-compatible front door. So it's Sora wearing a chat API costume. If streaming returns nothing, the node degrades to a non-streaming request.

• base_url - defaults to https://ai.t8star.org/v1. This is the overseas endpoint (the Sora nodes use the ai.t8star.org store, not the domestic seedance one).
• model - a free-text string, default sora_video2. The README lists the Plus-era model names (sora_video2-portrait-15s, sora_video2-landscape-hd-15s, etc.) - paste whichever the site currently offers.
• api_key - your Zhenzhen key, typed straight into the field. No settings node here.
• user_prompt - the video description (Chinese default placeholder; write whatever).
• aspect_ratio - 16:9 / 9:16.
• hd - boolean, default true. HD is the Plus feature.
• duration - default 15 (10/15 options), the Plus length.
• seed - cache-control only.

Output is a task (COMFLY_VIDEO_FUTURE) → Concurrent Collect Videos (10) → VIDEO tensors + status.

Install

ComfyUI Manager → search "Comfyui-zhenzhen" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen

No model files. Needs an account/key on the overseas store (ai.t8star.org), which the README warns requires a proxy from most networks.

The Sora-specific survival guide

• 500 = re-run. The README says it about as directly as a README can: most Sora2 500 errors are OpenAI's problem, not yours. Re-run before you debug anything.
• 401 = new token. The author's note: repeated 500-with-401 usually means the API key itself is flagged - make a fresh token on the site.
• Which group? The README (20260131, 20251018) keeps landing on sora-vip being the stable group for the paid tier, with default groups rotating on and off. If your runs fail at submit, check your token's group on the site, not the node.
• Timeout ≠ failure. Sora clips are slow (10s HD ≈ 5–20 min in the README's own numbers). If the node times out, the site's async-task page may still have your MP4 - download it from there instead of re-billing.
• Duration vs HD warnings. The README warns repeatedly: old Sora 2 wouldn't do HD at certain lengths (15s + HD was the notorious breakage). The Plus node exists to fix that class of bug, but the underlying API still has moods.

Reach for the Plus node when you want Sora's HD/15s tier in a parallel batch. Just budget for retries, keep a fresh token, and treat the site's async list as your source of truth when the node gives up first.