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

# Meet the Growth Engine

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

The goal of Entity is to accelerate growth in the cross-chain universe. Our innovative cross-chain growth engine will streamline the token go-to-market and interoperability of Web3 projects across multiple ecosystems.&#x20;

Addressing the challenges of liquidity fragmentation and cross-platform compatibility, Entity offers a comprehensive solution with its fully-compliant **Surge**, **Terminal**, **Bridge Aggregator**, and **Swap** modules.&#x20;

These tools work in harmony to deliver a seamless experience for users and projects alike, ensuring effortless token swaps, efficient asset bridging, and enhanced liquidity flows across different blockchains.

{% hint style="info" %}
For more info, check out the [Official Entity Litepaper](https://en.entity.global/litepaper).&#x20;
{% endhint %}


---

# 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://entity.gitbook.io/entity/what-is-entity/meet-the-growth-engine.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.