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

# Contract overview

The architecture of Swaylend has been rewritten from the Ethereum lending protocol solution [Compound v3](https://compound.finance/) to the Sway programming language. This documentation will cover two topics related to the Swaylend contracts: contract methods and storage entities. The contract methods section will discuss the functions available to interact with the contracts. In the storage entities section, we will explore the data stored by the contracts and the relationships between different storage values.

In this chapter you can find:

* [Contract methods](/developers/contract-methods/contract-methods.md)
* [Contract storage](/developers/contract-methods/contract-storage.md)


---

# 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.swaylend.com/developers/contract-methods.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.