> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/sagacli/key-management/listing-keys.md).

# Listing Keys

## List All Keys

To list all keys stored in `sagacli`, type

```
sagacli keys list
```

This will produce an output that displays all the keys stored in the default keyring (`os`).

```
$ sagacli keys list
- address: saga14hyhswxf0shnpzup406yvjejmfsrjnvzq897re
  name: metamask
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A4lAzjJ4bZnZIEhYQvW+qsgg9SzwQOkOgFG+q5enEv4l"}'
  type: local
- address: saga1tkax73wxs047nc8kaalhfc4ar6gay2sde28crx
  name: mykey1
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A1YCpZPIzs6MXTiMAOnlEK6Cq8+JQMii9a4vUnyQ0qGs"}'
  type: local
- address: saga1z0uscdcprxcun2mlnyrz5kelemmjw768sdrgz5
  name: test1
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A+u4iLJZWZHHcRIEbme8ppbmk1jYTpZVio8anPqAIQ31"}'
  type: local

```

## Different Keyring

To list keys held in a different keyring (not the default `os`), simply pass the `--keyring-backend <backend name>` to the list command:

```
$ sagacli keys list --keyring-backend test
- address: saga170ap6wma3vy6v6yjdwhq402hkccxmenng4g0rh
  name: test2
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AjO7X3g+CFcSAhfd77Rnf5KTBSS9pTG7BFn2jBVU1GdI"}'
  type: local
```

## Further Details

For a full list of options associated with listing keys, type

```
sagacli keys list --help
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saga.xyz/sagacli/key-management/listing-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.