Update an LLM
PATCH/llms/:llm_id
Changes the fields of an LLM registration that the request names, and keeps the stored value of every omitted field. A null value clears description or api_key, and a new api_key value replaces the stored key. A new endpoint is checked with the rules of registration. Foundation4 does not contact the model server during the update.
Permissions. Write on the LLM.
LLMs describes the fields of a registration.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
The LLM was updated. The body is the updated LLM registration, without the API key.
The request is invalid (Invalid parameter), and details.error names the cause: an empty api_key (api_key cannot be empty; leave it out to keep the stored key, or send null to remove it), or a new endpoint that is not permitted, with the messages of registration. The same status reports a body that is not valid JSON.
The authentication headers are missing or invalid, or the API key is inactive or expired. Errors lists the messages.
The license is not valid (Invalid license: <reason>).
No LLM with this identifier exists, or the key lacks write permission on the LLM (LLM not found, with the identifier in details.id).
Another LLM already has the requested name (Conflict unique error).
The body does not match the request schema, for example a value of the wrong type or an unknown field.