Delete a model from a live LiteLLM proxy via POST to /model/delete.
npx skills add https://github.com/BerriAI/litellm-skills --skill delete-model
Please help me install this Agent Skill. Skill: delete-model Source: https://github.com/BerriAI/litellm-skills/tree/main/delete-model Command: npx skills add https://github.com/BerriAI/litellm-skills --skill delete-model
Removing a model from a live LiteLLM proxy can be risky if done manually; this skill provides a safe, guided workflow to identify and delete a target model.
Provide the model name or ID, then confirm the prompt to delete it.
High-intent search queries and answers about installing and using this skill.
You can delete a model by providing its name or ID to initiate a workflow that retrieves the model ID and prompts for explicit confirmation before removal. This prevents accidental deletions on a live proxy.
When removing a model from a LiteLLM proxy, the workflow warns about existing API keys and references tied to that specific model. It provides guidance on how to properly rotate or clean up those dependent keys before finalizing the deletion.
Yes, you can remove a model using its name. The workflow handles model name-based lookups to automatically retrieve the required model ID before proceeding to the confirmation step for final deletion from the proxy.
You need the proxy base URL and a valid API key to remove a model from a live LiteLLM proxy. The tool validates this input before using curl to POST the deletion request to the /model/delete endpoint.
Removing a model from a live LiteLLM proxy manually is risky and can cause accidental removals. A guided workflow validates input, handles name-based lookups, and enforces a confirmation step to ensure safe execution.
BerriAICreate a new user on the LiteLLM proxy via its API.
DevMHOneCreate, list, rotate, and revoke NextRoute API keys with scopes, limits, and expiration.
maruakshayAudits LiteLLM proxy deployments for API key leakage and implements hardening steps.
BerriAIUpdate existing LiteLLM proxy users via the POST /user/update endpoint.
