output_count is a quantity
Images and videos accept an integer from 1 to 4, defaulting to 1. It is the number of target results, not a promise of four simultaneous connections. Invalid counts are rejected before work starts.
The initial implementation splits the request into individual provider calls. A single item may contain a video and its thumbnail, but it still counts as one generated result.
Operation: output_count = 4
├─ Item 0 → low-cost success
├─ Item 1 → low-cost failure → official success
├─ Item 2 → low-cost success
└─ Item 3 → low-cost failure → official failureSame parameters, independent work
All items receive the same normalized input. A fixed seed stays fixed and may produce identical results. If no seed is provided, follow the model’s random behavior; diversity is not guaranteed.
Successful items are never rerun just because another item fails. Eligible failures can use their own fallback inside the original operation. After the parent is final, an explicit retry creates a new operation with a new quote.
Capacity and accounting
- A four-result call counts as one API operation, four target items, and however many provider attempts actually ran.
- Each active item consumes execution capacity. Accepted items may queue when the provider concurrency limit is reached.
- Credits are reserved for all items before acceptance and settled per item, using its final successful route.