Seed parameter and n completions parameter

Using both the seed parameter and the n (multiple completions) parameter results in n completions using the same seed parameter. Not saying that’s unexpected, but wondering if there’s a way around that, or if my only option is to have my code make n parallel (single-completion) calls to the API w/ diff seeds?

That feels dumb. Maybe it should add “i” to the seed for each additional completion?

1 Like