> For the complete documentation index, see [llms.txt](https://kitchen-layer.gitbook.io/kitchen-layer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kitchen-layer.gitbook.io/kitchen-layer-docs/readme.md).

# Welcome

Welcome to the Kitchen Layer! A network at the frontier between HyperCore, HyperEVM, and OG DeFi chains.  

Kitchen Layer is a unique **Hyperliquid L2**, built to break technical barriers to entry on HyperEVM and expand access to HyperCore decentralized liquidity layer to a broader crypto ecosystem.

kitchen core component is a library of 100s audited precompile functions, simplifying the work for builders as well as reducing development costs, while protecting users with security labels and trusted features directly at the chain level.

By providing resources and customization to creators, yield and security to users, Kitchen Layer is designed to become the go to network for Memefi, NFTs and GameFi projects. 

<figure><img src="/files/VZN2ch6BrvASe59AGpeS" alt=""><figcaption></figcaption></figure>

Kitchen Layer transcends the typical "feature chase" approach by strategically integrating market-validated blockchain primitives directly at the chain level. Instead of repeatedly reimplementing standard functionalities across different applications, Kitchen Layer provides a robust, native infrastructure that allows builders to compose sophisticated protocols with pre-audited, standardized components.&#x20;

This approach substantially reduces development complexity, minimizes potential security vulnerabilities, ensures consistent performance, and accelerates time-to-market for blockchain applications.&#x20;

By embedding these proven primitives natively, Kitchen Layer empowers developers to innovate at the application layer while maintaining high standards of security, efficiency, and user experience.

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting Started</strong></td><td>First steps in the Kitchen</td><td></td><td></td><td><a href="/pages/CyH2xJQs9yWJ1S8BYNav">/pages/CyH2xJQs9yWJ1S8BYNav</a></td></tr><tr><td><strong>Cook Book</strong></td><td>Best tools and recipes </td><td></td><td></td><td><a href="/pages/7aUFmnCMx9m4smGncsXL">/pages/7aUFmnCMx9m4smGncsXL</a></td></tr></tbody></table>


---

# 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://kitchen-layer.gitbook.io/kitchen-layer-docs/readme.md?ask=<question>&goal=<endgoal>
```

`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.