> 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/integration-with-account-cap.md).

# Integration with Account Cap

If an external contract wants to interact with the NAVI protocol, an account cap is required for the interaction. The account cap must be stored within the contract as a wrapped object. When calling functions—such as the supply token function—the account cap object must be passed as a parameter to enable the transaction.

### Code Snippet: Account Cap Integration

```rust
public struct Vault has key, store {
    id: UID,
    account_cap: AccountCap,
    sui_index: u8,
    usdc_index: u8
}

lending_core::incentive_v2::deposit_with_account_cap(
    clock, 
    storage, 
    pool_a, 
    vault.sui_index, 
    deposit_coin, 
    inc_v1, 
    inc_v2, 
    &vault.account_cap
)
```

In this example, the `Vault` struct includes an `account_cap` field that is passed into the `deposit_with_account_cap` function to enable token deposits.


---

# 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/integration-with-account-cap.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.