Feature Request: API Key pattern detection

[alexanderkjeldaas]

When using the dataset to setup a provider, the expected UI is one where the provider is selected first, then model, or a substring search on model or provider is the first step.

But what if the UI allows for the user to enter the API key first?

In this case, it would be useful if the possible providers could be focused, because in many cases, the API key itself has a prefix that excludes all providers except the relevant one. Thus a UI where the API key is first entered could, in some cases, be the most efficient one.

So this is asking for an optional feature for the provider TOML where a regexp for how API keys are structured, is provided.

[github-actions]

This issue is a feature request to track a new kind of information (API key prefix/regex patterns for provider detection). It asks for an optional new schema field and a UI/UX capability, not a correction to existing model or provider catalog metadata.

This needs maintainer review — no automated fix was opened. The request would require schema changes (a new field like api_key_pattern) and likely UI/search logic, which fall outside the scope of catalog data fixes I'm permitted to make.