Repository navigation
Conversation
Signed-off-by: Adrien Gallouët <angt@huggingface.co>
9cfc222 to
3253f96
Compare
ngxson
left a comment
There was a problem hiding this comment.
UX-wise, I think having a single type is not very future-proof
In the past, we had the same story with models capable of doing infill/embeddings/reranking and combination of them. The verdict was to have an array of tags to indicate model's capability.
Maybe we can do the same here? Models capable of both clasification+chat are totally possible and high chance we will see some popping up soon
|
Does it make sense this to be input or output modality, similar to |
|
Something like that ? see openrouter: https://openrouter.ai/docs/guides/overview/models |
|
This makes sense to me, but would defer to @ngxson for the final say. |
|
openrouter skips decision models in the list unless explicitly asked for, not sure if we want to to do the same. There's also a proposal to add |
|
Given that OpenRouter does it like this, I think it's one more reason to follow that - better than adding our alternative at this point? @mitsuhiko Would it work for you if the decision type is announced in the output modalities?
Hm, don't see what is the reason to do that. Returning everything by default should be OK. |
|
Yes, both make sense to me (use the output modalities, return everything). |
|
yeah I think the |
|
Superseded by #29987 |
Overview
Add a
typefield toGET /v1/modelsandGET /models.The field gives the kind of the model:
classifier: a native decision model. Use/v1/systemonefor it.model: a normal model. Its metadata has no decision type.unknown: the metadata is missing or not valid.Additional information
earendil-works/pi#10382
Requirements