> 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/resources/faq.md).

# FAQ

Common questions about Takapu Protocol.

## Who is Takapu Protocol for?

Professional Market Makers connecting their existing engines to PropAMM execution, and Execution Routers integrating the resulting liquidity.

## Who controls the Maker's pricing and inventory?

The Market Maker controls its pricing, inventory, risk, hedging, and settlement capital. Takapu Protocol standardizes quote distribution, validation, matching, and settlement.

## Does every quote update require an on-chain transaction?

No. Market Frames are generated and signed off-chain, then distributed through Market Streams. Executing a trade still requires on-chain execution and settlement.

## Where do I find API and SDK documentation?

In [Build](https://docs.takapu.org/build). The initial documentation framework has separate API Reference and Official SDK sections, with detailed content being added progressively.

## How do I discuss an integration?

[Contact the team](broken://pages/5qYaEVk1kQHpHxBL9rVu) with your Market Maker or Execution Router use case.


---

# 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/resources/faq.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.