> 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/saga-web-app/working-with-chainlet.md). # Working with Chainlet The Pegasus Incentivized Testnet is the developer’s portal into the Saga ecosystem. Like most smart contracting platforms, the developer deploys their compiled smart contract binary onto the Saga testnet. Once initialized, the Saga validators automatically provision a Saga dedicated chain, or `chainlet`, containing the smart contract. A `chainlet` is literally where the rubber meets the road! It is your own dedicated blockchain with its own validator set secured by the SAGA platform main validator set. It provides dedicated blockspace for your `web3` application. {% hint style="info" %} There can be several different *types* of chainlets i.e. a pre-packaged blockchain encapsulating some custom functionality on top of an EVM. In the near future SAGA Platform will support many different *types* of chainlets that would deploy other execution environments like CosmWasm, Solana, Javascript, etc {% endhint %} Pegasus makes its own chainlet type available to developers called `SagaOS`. It runs an EVM compatible blockchain leveraging [Cosmos SDK](https://v1.cosmos.network/sdk). With **Saga Web App** you can view the types of chainlets that can be launched, launch chainlets, view all of the chainlets you have launched as well as get detailed information on each chainlet. Additionally, each chainlet comes equipped with its own RPC endpoints to integrate with your wallet or web3 application, and a block explorer that you can use in a web browser and search for transactions, view contents of blocks and other details pertaining to the activity and state of your chainlet. --- # 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/saga-web-app/working-with-chainlet.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.