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

# What We Do

Redefining Interoperability with iLayer.

iLayer provides an intuitive, one-stop solution enabling developers and decentralized protocols to effortlessly execute arbitrarily complex cross-chain Web3 actions through a flexible, intent-based protocol. At its core, iLayer simplifies cross-chain interoperability, allowing developers to specify their desired outcomes without needing deep technical expertise in bridge technology or chain-specific protocols.

This significantly reduces the typical complexity associated with cross-chain integrations, cutting implementation times from days or weeks to less than one hour.

With iLayer, protocols instantly gain access to interoperability across major EVM-compatible and non-EVM blockchains, unlocking new liquidity channels, accelerating time-to-market, and enhancing user experiences. By abstracting away the technical overhead, iLayer enables Web3 builders to focus on innovation, product growth, and delivering exceptional cross-chain functionality to users.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilayer.io/introduction/what-we-do.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 `build a script that syncs our docs to a CMS` 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.