Feature Request: Support for listing avaiable models

[raffits]

As the title states - Adding the ability to list available models.

[richarddas]

Do you mean turning the model values into enums, instead of having to refer to them by strings?

I'd be up for that, as long as we can still pass string overrides so that adopting a new model (eg. 5.x) doesn't require an SDK update if there are no other changes.

[lzell]

so that adopting a new model (eg. 5.x) doesn't require an SDK update if there are no other changes.

@richarddas that's one of the reasons I didn't go with models as enums in the first place. But perhaps we could make the call site snippets look something like:

model: OpenAIModel.gpt5.rawValue

and OpenAIModel would be an enum OpenAIModel: String

Then you are free to pass a string, but can also use autocomplete to see possibilities

[richarddas]

You could define the enum as a String:

enum OpenAIModel: String {
    case gpt4_1 = "gpt-4.1"
    case gpt5 = "gpt-5"
    // ...add known models here
}

Then the call site could accept:

model: .gpt5 // enum
model: "gpt-4o-nano" // freeform string

However, given how many models (and variants!) there are, I'd suggest keeping it as-is — a string for now and just adding a link pointing to the OAI model list is a reasonable compromise (otherwise you're inviting maintenance)

[raffits]

Apologies for the slow response. I was referring to adding support for listing available models from the providers (ie: retrieving the list of available models and returning a "XXXProviderModelsResponse" with list of Models containing model name, id, owner, created date, etc..). This would let the implementer determine what model to use based on their own use case and logic. I agree with keeping things as is in regards to your enum suggestion.