List MaaS Models
Lists available large language models in OpenAI-compatible format. Incoming HTTP headers on this request are forwarded to the upstream MaaS API unchanged (aside from Content-Type and Authorization, which the BFF sets for the outbound call). Callers may send headers understood by maas-api (for example X-MaaS-Return-All-Models).
Response
List of models
Example response
{
"data": {
"object": "list",
"data": [
{
"created": 1672531200,
"id": "llama-2-7b-chat",
"object": "model",
"owned_by": "model-namespace/llama-2-7b-chat",
"ready": true,
"url": "https://api.example.com/v1/models/llama-2-7b-chat",
"modelDetails": {
"displayName": "Llama 2 7B Chat",
"description": "A large language model optimized for chat use cases",
"genaiUseCase": "chat",
"contextWindow": "4096"
},
"kind": "LLMInferenceService",
"subscriptions": [
{
"name": "premium-subscription",
"displayName": "Premium Subscription",
"description": "Premium subscription with higher rate limits"
}
]
}
]
}
}Changes
Changed in 5 of the 31 revisions of this API.711
- ○
added the optional property
data/data/items/modelDetails/modelCapabilitiesto the response with the200statusresponse-optional-property-added
- ○
- ▲
the
dataresponse's property type/format changed fromarray/toobject/for status200response-property-type-changed
- ▲
removed the required property
objectfrom the response with the200statusresponse-required-property-removed
- ○
added the required property
data/datato the response with the200statusresponse-required-property-added
- ○
added the required property
data/objectto the response with the200statusresponse-required-property-added
- ▲
- ○
added the optional property
data/items/kindto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/items/modelDetailsto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/items/subscriptionsto the response with the200statusresponse-optional-property-added
- ○
- ○
api tag
modelsaddedapi-tag-added
- ○
added the media type
application/jsonfor the response with the status500response-media-type-added
- ○
the response property
databecame required for the status200response-property-became-required
- ○
added the required property
objectto the response with the200statusresponse-required-property-added
This revision also has 7 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
removed the media type
application/jsonfor the response with the status500response-media-type-removed
- ▲
the response property
databecame optional for the status200response-property-became-optional
- ▲
the
dataresponse's property type/format changed fromobject/toarray/for status200response-property-type-changed
- ▲
removed the required property
data/datafrom the response with the200statusresponse-required-property-removed
- ▲
removed the required property
data/objectfrom the response with the200statusresponse-required-property-removed
- ○
api tag
modelsremovedapi-tag-removed
This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲