delete-agent

To delete an AI agent from a live LiteLLM proxy, you use curl to send a DELETE request to the /v1/agents/{agent_id} endpoint via the proxy admin API, providing the specific agent_id and confirming the action beforehand.

You should remove an AI agent from an active proxy pool when decommissioning outdated configurations or reassigning responsibilities, ensuring the agent no longer appears or responds to incoming requests within the live environment.

Yes, you need access to the proxy admin API and curl installed to decommission an agent on a LiteLLM proxy, as the deletion process requires sending an authenticated DELETE request to the /v1/agents/{agent_id} endpoint.

User confirmation is required to remove an agent from the proxy to prevent accidental deletions of active configurations, ensuring that outdated agents are intentionally decommissioned without disrupting downstream components or integrations.

When you delete an agent from the proxy, the process informs dependent downstream components, such as keys or integrations, about the removal so they can adjust to the agent no longer being available in the active pool.

Yes, you can reassign responsibilities by deleting an agent from the LiteLLM proxy, which removes the specific agent identified by its agent_id from the active pool and ensures it stops responding to requests.