> For the complete documentation index, see [llms.txt](https://docs.tradecraft.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradecraft.fi/integrations/integrate-tradecraft/readme.md).

# Integration

Build apps that surface trading and LP features, or use Tradecraft liquidity as a building block for more complex products.

Tradecraft is a permissionless decentralized exchange, open for integration by wallets and other dApps.

{% hint style="warning" %}

## Dependencies

Both of the integration options below require the DA Utility package version 0.14.4. If you do not have it installed when making trades you will be unable to receive the incoming tokens. Additionally you may be automatically put on a temporary blacklist to prevent further trades from being initiated. If you think you may have been blacklisted, [contact us](https://docs.tradecraft.fi/support/get-help).
{% endhint %}

We offer two integration options, with the tradeoffs shown below:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><h3>Pool Addresses</h3></td><td>Interact using standard Daml <em>TransferOffers</em> and <em>Preapprovals</em>.</td><td><p><i class="fa-check" style="color:$warning;">:check:</i> Trade.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Deposit and withdraw liquidity.</p><p><i class="fa-x" style="color:$danger;">:x:</i> More expensive.</p><p><i class="fa-x" style="color:$danger;">:x:</i> Slower transactions.</p><p><i class="fa-x" style="color:$danger;">:x:</i> Lower TPS capacity.</p><p><i class="fa-x" style="color:$danger;">:x:</i> No flash accounting features.</p><p><i class="fa-x" style="color:$danger;">:x:</i> No built-in leg matching.</p><p><i class="fa-x" style="color:$danger;">:x:</i> No transaction failure insight.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Usable with basic transfer API access (no validator node required).</p></td><td><a href="https://docs.tradecraft.fi/using-tradecraft/">Documentation</a></td></tr><tr><td><h3>Daml Package</h3></td><td>Interact using custom choices from our Tradecraft Daml package.</td><td><p><i class="fa-check" style="color:$warning;">:check:</i> Trade.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Deposit and withdraw liquidity.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Cheaper transactions.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Faster transactions.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Higher TPS capacity.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Flexible flash accounting features.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Leg matching built in.</p><p><i class="fa-check" style="color:$warning;">:check:</i> Transaction failure insight.</p><p><i class="fa-x" style="color:$danger;">:x:</i> Requires a validator node to use.</p></td><td><a href="/integrations/integrate-tradecraft/guide-dar-integration.md">Documentation</a></td></tr></tbody></table>

Aside from the above documentation, other helpful documentation includes:

[Guide: Building a Trading Interface](/integrations/integrate-tradecraft/guide-building-a-trading-interface.md)

[HTTP API Docs](https://docs.tradecraft.fi/api/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tradecraft.fi/integrations/integrate-tradecraft/readme.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 `automate deployments from our CI pipeline` 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.