> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/cloudeka-api-list/command-reference/cldkctl-llm/delete-keys.md).
# delete-keys
The llm delete-keys command removes an existing LLM (Large Language Model) key from your project. This command allows you to delete specific keys by providing their token.
## Usage
```
cldkctl llm delete-keys [flags]
```
## Aliases
```
delete-keys, rm-keys
```
## Steps
Follow the steps below to run and view the result of this command:
1. Run the following command in your terminal:
```
cldkctl llm delete-keys --token [token]
```
2. Replace \[token] with the unique identifier of the key you want to remove. You can find this token by running the command in the LLM List Keys section.
3. Once the command executes successfully, a message “✓ LLM Key deleted successfully!“ will appear in your terminal.
## Flags
{% hint style="info" %}
This command supports [global flags](/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details.
{% endhint %}
| Flag | Description |
| ---------- | ------------------------------------- |
| -h, --help | Help for the llm delete-keys command. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cloudeka.ai/cloudeka-api-list/command-reference/cldkctl-llm/delete-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.