> For the complete documentation index, see [llms.txt](https://docs.amis13.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amis13.tech/archive/web3crypt-rpcs/initia.md).

# Initia

Introduction to Initia: A Network for Interwoven Rollups

In the dynamic realm of blockchain technology, Initia emerges as a leader in innovation and simplicity. Our mission is to revolutionize the multi-chain network experience by integrating architecture, product, and economic systems into a seamless whole. Initia addresses the complexities of the current multi-chain environment, simplifying user and developer interactions with an intuitive and interconnected platform, much like Apple's design philosophy. By reconstructing the technological stack with a foundational Layer 1 blockchain and a bespoke Layer 2 infrastructure, Initia fosters a cohesive ecosystem of modular networks. This document unveils Initia's transformative approach to blockchain technology, setting new standards for the future.

Docs: <https://docs.initia.xyz/>

<figure><img src="https://351002237-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRYlrkXQToqhM1nUWqBTA%2Fuploads%2FuacqCuwhPy6uwVM215h4%2Finitia.png?alt=media&amp;token=afc4f73f-39ed-468c-86a0-abf464c8acb8" alt="" width="375"><figcaption></figcaption></figure>


---

# 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.amis13.tech/archive/web3crypt-rpcs/initia.md?ask=<question>&goal=<user_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.