> For the complete documentation index, see [llms.txt](https://docs.eniac.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eniac.network/reference/overview.md). # Overview **Reference Overview** Welcome to the Reference section of the ENI documentation. This section provides key technical resources for interacting with the ENI network. **enid** **enid** is a command-line tool for interacting with the ENI network. It allows you to manage nodes, query blockchain data, and process transactions, providing the essential tools needed to operate within the network. **API Reference** The API Reference contains detailed documentation for programmatically interacting with the ENI network via REST and gRPC APIs. You will find endpoints for querying data, submitting transactions, and interacting with both the Cosmos and EVM layers. * **Cosmos Endpoints**: APIs that provide core Cosmos functionality, such as staking, governance, and chain queries. * **EVM Endpoints**: Detailed APIs for interacting with Ethereum-compatible smart contracts deployed on the ENI network. **EVM Precompiled Contracts** EVM Precompiled Contracts are built-in contracts on the ENI EVM, offering optimized functionality for specific operations. --- # 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.eniac.network/reference/overview.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.