> For the complete documentation index, see [llms.txt](https://legacy-docs.aragon.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.aragon.org/developers/tools/aragon-connect/api-reference/app.md).

# App

{% hint style="info" %}
An Aragon app in an organization from an [aragonPM repository](/developers/tools/aragonpm.md).
{% endhint %}

## Properties

| Name                | Type                                 | Description                                                                                                                                   |
| ------------------- | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| `abi`               | `Abi`                                | The Ethereum contract ABI of the app contract.                                                                                                |
| `address`           | `String`                             | The address of the app proxy contract (never changes).                                                                                        |
| `appId`             | `String`                             | The `appName` encoded via [namehash](https://eips.ethereum.org/EIPS/eip-137).                                                                 |
| `appName`           | `String`                             | The app’s ENS identifier. E.g. `"token-manager.aragonpm.eth"`                                                                                 |
| `artifact`          | `AragonArtifact`                     | Metadata for the smart contract of the app, generated at publish.                                                                             |
| `codeAddress`       | `String`                             | The address of the app’s implementation contract (changes with every major version).                                                          |
| `contentUri`        | `String`                             | The location of the metadata content published with each version of the app. Empty for special apps like the kernel. E.g. `"ipfs:QmdLEDDfi…"` |
| `deprecatedIntents` | `{ [version]: TransactionIntent[] }` | Deprecated transaction intents, grouped by version.                                                                                           |
| `intents`           | `TransactionIntent[]`                | An array of transaction intents. It contains the Ethereum ABI, roles, and radspec notice attached to an intent.                               |
| `isForwarder`       | `Boolean`                            | Whether the app can act as a forwarder.                                                                                                       |
| `isUpgradeable`     | `Boolean`                            | Whether the app can be upgraded.                                                                                                              |
| `kernelAddress`     | `String`                             | The address of the kernel this app is installed on.                                                                                           |
| `manifest`          | `AragonManifest`                     | Publisher-specific metada.                                                                                                                    |
| `name`              | `String`                             | Name of the app, from the repository. E.g. `"Tokens"`.                                                                                        |
| `registryAddress`   | `String`                             | Address of the aragonPM registry this app’s repo is published to.                                                                             |
| `registry`          | `String`                             | Name of the aragonPM registry this app’s repo is published to. E.g. `"aragonpm.eth"`                                                          |
| `repoAddress`       | `String`                             | Address of the aragonPM repository the app was installed from.                                                                                |
| `version`           | `String`                             | The current version of the app.                                                                                                               |

## Methods

### App#repo()

Fetch the app’s aragonPM repository.

| Name    | Type            | Description                                           |
| ------- | --------------- | ----------------------------------------------------- |
| returns | `Promise<Repo>` | A promise resolving to the app’s aragonPM repository. |

### App#roles()

Fetch the app’s roles.

| Name    | Type              | Description                             |
| ------- | ----------------- | --------------------------------------- |
| returns | `Promise<Role[]>` | A promise resolving to the app’s roles. |


---

# 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://legacy-docs.aragon.org/developers/tools/aragon-connect/api-reference/app.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.