> For the complete documentation index, see [llms.txt](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi.md).

# Contract Integration with NAVI

To interact with the **NAVI Protocol**, external contracts must use a specific mechanism called the **Account Cap**. This mechanism allows contracts to seamlessly integrate with NAVI’s ecosystem, enabling operations such as supplying and borrowing assets, checking rewards, and more.

#### Key Interaction Components:

* **Account Cap**:\
  The Account Cap is a **non-fungible token (NFT)** that serves as a key, granting external contracts the ability to interact with NAVI’s smart contracts. It must be stored within the external contract as a wrapped object and passed into relevant functions (e.g., supplying tokens) for transactions to occur.
* **Oracle Update**:\
  Oracle data ensures that NAVI maintains accurate and up-to-date asset prices, which are critical for external contracts to perform correct valuations and liquidations.

By using the Account Cap, external contracts can fully access and interact with NAVI’s core functionalities, allowing them to participate in and benefit from NAVI's lending, borrowing, and reward systems. The **contract integration** page provides detailed guidance for writing logic in smart contracts.

{% content-ref url="/pages/W0UubpcVwCTOLnX9naIT" %}
[Retrieve Pools Info inside Contract](/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract.md)
{% endcontent-ref %}

{% content-ref url="/pages/sHpzIJYU57hulZjFQjzq" %}
[Integration with Account Cap](/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap.md)
{% endcontent-ref %}

{% content-ref url="/pages/A5s55lgDCLPWJDYifsJF" %}
[Demo](/navi-protocol-developer-docs/contract-integration-with-navi/demo.md)
{% endcontent-ref %}


---

# 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://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi.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.