Vector Store ID Array Limit on File Search Tool

I love the new Responses API and am in the process of migrating from Assistants API. However, my use case demands that I assign more than one vector store ID to the File Search tool in a request. I was getting around this previously because I could assign one store to the Assistant and the other store to the Thread. With the Assistant removal, I am down to one call, and it seems that the array is still limited to one element. I’m sure I can engineer solution, e.g., two concurrent calls, but I’d hate to do that if this limitation is removed soon. It seems that multiple vector store assignments will be coming since it was not changed to a single value in the most recent API and remains an array.

1 Like

Same here. The name "vector_store_ids" and the fact that it is an array suggests the search will be done over several vector stores. Moreover, the documentation seems to say so:

vector_store_ids array Required
The IDs of the vector stores to search.

It isn’t very pleasant since I based my whole application around this assumption.
@sclayturner did you manage to solve it? Concurrent calls may not work for me

@dpiret1 I’m proxying through my own API via a function call. In the local function that gets invoked by the model, I pass the multiple vector store IDs to my own API. My API then parallel processes the file search and returns unified results.

I ended up unifying vector stores into one and filtering files by attributes in the responses API call. It’s not ideal, but it’s simple.