delete-key

Delete API keys from a live LiteLLM proxy via POST /key/delete.

77|12|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BerriAI/litellm-skills --skill delete-key
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delete-key
Source: https://github.com/BerriAI/litellm-skills/tree/main/delete-key
Command: npx skills add https://github.com/BerriAI/litellm-skills --skill delete-key

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delete API keys from a live LiteLLM proxy to revoke access and reduce risk.

Core Features & Use Cases

  • List existing keys and identify ones to revoke
  • Delete by value or by key alias with explicit confirmation
  • Guarantee post-action visibility by returning deleted keys

Quick Start

Provide the key(s) or alias to delete and confirm before the POST /key/delete request is issued.

Frequently Asked Questions about delete-key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I revoke API keys on a LiteLLM proxy?

To revoke API keys on a LiteLLM proxy, you issue a POST /key/delete request with a payload of specific keys or key aliases. The workflow requires explicit confirmation before deletion to ensure access is safely removed.

Can I delete multiple API keys at the same time using a key alias?

Yes, you can delete multiple API keys at the same time by providing a list of keys or key_aliases in the deletion payload. This allows you to revoke access across teams or organizations efficiently.

What is the best way to ensure a deleted API key is actually revoked?

The best way to ensure an API key is revoked is to use a workflow that includes a confirmation step before issuing the POST /key/delete request and returns the deleted keys afterwards for post-action visibility.

Do I need admin credentials to delete keys from a live LiteLLM proxy?

Yes, deleting keys from a live LiteLLM proxy requires admin credentials. The process uses a curl-based admin workflow to securely execute the POST /key/delete request and manage access across the proxy.

Why use key aliases instead of raw key values when revoking proxy access?

Using key aliases instead of raw key values when revoking proxy access allows you to manage and identify keys by their organizational role rather than their sensitive string value, simplifying batch deletion across teams.