> For the complete documentation index, see [llms.txt](https://docs.yad.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yad.finance/architecture/smart-contracts.md).

# Smart contracts

Our smart contracts are designed with a strong emphasis on interoperability, enabling seamless integration into diverse solutions. Accessible via our API, these contracts have been widely adopted by numerous parties to power their unique solutions and business operations, underlining the flexibility and utility of our design. <br>

Our smart contracts offer two distinct usage methods:

1. You can directly utilize our API to acquire calldata and transmit it to our proxy address.
2. Alternatively, developers can construct their own custom smart contract on top of our existing smart contracts. By invoking our API, you can interact with our proxy smart contract and carry out the transaction using the call data you received from our API.

This documentation is an evolving resource and will be updated as YAD's system continues to grow and improve.


---

# 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.yad.finance/architecture/smart-contracts.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.