> For the complete documentation index, see [llms.txt](https://docs.takapu.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takapu.org/discover/built-for/execution-routers.md).

# Execution Routers

Connect aggregators, solvers, wallets, and applications to Takapu liquidity.

An Execution Router brings user order flow to Takapu Protocol. It subscribes to quotes from multiple independent PropAMMs, evaluates the available options, and submits the trade it chooses.

## Who can be an Execution Router?

An Execution Router can be an aggregator, solver, wallet, trading application, or any routing system that needs access to Takapu liquidity. The role is defined by the integration: if your system needs to source, compare, and execute quotes from connected Market Makers, it can integrate as an Execution Router.

## One integration, multiple PropAMMs

Execution Routers use a common Market Frame and execution model instead of building a separate quote and settlement integration for every Market Maker.

1. Subscribe to Market Frames and Market Streams.
2. Select a quote and simulate the intended execution.
3. Submit the selected Frame with the required execution limits.
4. Observe fills and settlement events.

Takapu Protocol verifies the submitted state, matches executable depth, and completes direct atomic settlement.


---

# 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://docs.takapu.org/discover/built-for/execution-routers.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.