> 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/bridge-aggregator.md).

# Bridge Aggregator

<figure><img src="/files/5S933BphEvO4Pg3rslli" alt=""><figcaption></figcaption></figure>

Instead of needing to research different bridges and compare them, Entity takes care of all the hard work. The result: You use the best and most efficient bridge every time with minimal effort required.

Powered by an innovative **Path Optimizer**, this module will consider a range of factors to get the best route possible for each transaction. The Path Optimizer doesn’t just consider what is the fastest and cheapest route, but it also accounts for other factors like fees, network congestion, and available liquidity.

The Path Optimizer is constantly gathering new information and refining it into two key categories: a Trust Score and a Metrics Score. The Trust Score takes into account factors such as dependencies, attack vectors, and overall security assumptions to keep your funds secure. And the Metrics Score delivers maximum efficiency by considering factors such as execution speed, fees, gas costs and overall reliability such as uptime and failed transactions.


---

# 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/bridge-aggregator.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.
