> 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/view-listing-of-chainlet-types.md). # View Listing of Chainlet Types ## Command You can view the chainlet types by using the following command: ``` sagacli chainlet list-types ``` ## View Listing Example ``` $ sagacli chainlet list-types DisplayName Description Creator Version SetupCost EpochCost ----------- ----------- ------- ------- --------- --------- SagaOS SagaOS Chainlet Stack saga1yuvju0cztlahsf6f37z9j83vwyzgj6pzhx090f 0.5.17 10000000upsaga 10000000upsaga/day ``` ## Chainlet Type Versions Every chainlet type also has an associated version. A version ultimately points to a different image of the chainlet type and encapsulates a set of features available to a launched chainlet. Creating a different version of the chainlet type can be necessitated by many reasons, such as security patching, adding new functionality, removing redundant functionality etc. ## Further Details For additional details and options to list chainlet types, please refer to ``` sagacli chainlet list-types --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/view-listing-of-chainlet-types.md?ask=&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.