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

# Integrations (APIs)

OpenTrade provides a protocol and REST APIs for seamless integrations and reporting.

There are three primary means of integrating,  white-labelling, and/or embedding the stablecoin yield vaults into your existing applications. You can use one, some, or all of them depending on your desired experience and operating model. 

<table><thead><tr><th width="214">Integration Path</th><th width="177">Function</th><th>Use</th></tr></thead><tbody><tr><td>Protocol</td><td>Read / Write</td><td>Integrating to the protocol enables you to automate deposits, withdrawals, and read contract and account data. See which networks we support <a href="/welcome-to-opentrade/supported-blockchain-networks.md">here</a> and the vault contract addresses <a href="/developers/contract-addresses.md">here</a>. </td></tr><tr><td>REST API</td><td>Read Only</td><td>The REST API enables you to query any data on the platform, vaults, accounts, and transactions. You can use the API query the latest data or historical information. This API can be used to build UIs, reporting functionality, integrate to middle and back office systems for reconcilliation, and more. </td></tr></tbody></table>

{% hint style="info" %}
For detailed documentation on all integration paths, please contact your account manager.&#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 by asking a question.

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

```
GET https://docs.opentrade.io/developers/integrations-apis.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.