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

# Account

This c**omponent** holds the base implementation for a tokenbound account. All functions contained within it is compulsory to maintain compatibility with SNIP-14.

The full contract code of the `AccountComponent` can be found [**here**](https://github.com/horuslabsio/TBA/blob/v3/src/components/account/account.cairo)**.**

## Functions

### `owner`

```rust
fn owner(self: @ComponentState<TContractState>) -> ContractAddress
```

This function retrieves the owner of the associated NFT.

### `token`

```rust
fn token(self: @ComponentState<TContractState>) -> (ContractAddress, u256, felt252);
```

This function returns the contract address and token ID of the associated NFT.

### `state`

```rust
fn state(self: @ComponentState<TContractState>) -> u256
```

This function retrieves the current state of the account.

### `supports_interface`

```rust
fn supports_interface( self: @ComponentState<TContractState>, interface_id: felt252) -> bool
```

This function checks if the account supports the tokenbound interface.

#### **Parameters**

| Name      | Type           | Description                             |
| --------- | -------------- | --------------------------------------- |
| `felt252` | `interface_id` | The interface ID to be checked against. |

#### **Returns**

`bool`:  Returns `true` If the interface is supported, otherwise false.


---

# 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.tbaexplorer.com/contracts/components/account.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.