> For the complete documentation index, see [llms.txt](https://docs.kardiachain.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kardiachain.io/docs/archived-docs/technology/kardia-smart-contract-markup-language.md). # Kardia Smart Contract Markup Language **What is Kardia Smart contract Markup Language (KSML)?** The KSML is designed to be the ultimate tool for developers to develop Smart Contracts on KardiChain platform without requiring significant learning curves or prior experience. **How KSML benefits the developers?** By introducing a huge set of instruction codes in human readable format (JSON or YAML format), developers can easily work on their popular logics without having to write a single line of code for the targeted blockchain (eg. Solidity for Ethereum, C#, Java, Python for NEO and others).Along with KSML is the syntax checkers, which the developers can use to quickly verify whether KSML contracts are correct and can be parse on KadiaChain platform. KSML and the tool will be packaged into the SDK to provide developers with an unified toolkit for implementing their own solutions on KardiChain platform. --- # 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.kardiachain.io/docs/archived-docs/technology/kardia-smart-contract-markup-language.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.