> 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/working-with-chainlet/get-chainlet-information.md).

# Get Chainlet Information

You can get detailed information about a specific chainlet using the `chainlet get` command:

```
sagacli chainlet get <chain-id>
```

### Get Chainlet Information Example

<pre><code><strong>sagacli chainlet get jargames_1679785243507504-1
</strong><strong>ChainId                           Name           StackName     StackVersion     Launcher                                        Mantainers                                        CurrencySymbol     Status            
</strong>-------                           ----           ---------     ------------     --------                                        ----------                                        --------------     ------            
jargames_1679785243507504-1       jargames       SagaOS        0.5.17           saga1rdssl22ysxyendrkh2exw9zm7hvj8d2ju346g3     [saga1rdssl22ysxyendrkh2exw9zm7hvj8d2ju346g3]     jar                STATUS_ONLINE     
</code></pre>

In the above output, you can see details like

* Chain ID of the chainlet
* Name of the chainlet
* The chainlet type aka `StackName`
* The version of the chainlet type aka `StackVersion`
* The launcher (owner) of the chainlet
* The currency symbol i.e. token symbol aka `denom` associated with the chainlet
* The status of the chainlet. Possible values are `STATUS_ONLINE` (chainlet is up and running) and `STATUS_OFFLINE` (chainlet has been stopped)

### Further Details

For further details on using the `chainlet get` command, refer to

```
sagacli chainlet get --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/working-with-chainlet/get-chainlet-information.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.
