> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/web3-defi-and-nft/defi/ledger-enterprise-dapps.md).

# Ledger Enterprise DApps

{% hint style="info" %}
Interacting with smart contracts can put funds at risk. We advise Users to educate themselves about smart contract risks before activating smart contract interactions.
{% endhint %}

Ledger Enterprise DApps is your safe and trusted place to explore and unlock the full potential of decentralized applications (DApps) on Ethereum. Using DApps within Ledger Enterprise offers you the highest possible smart contract interaction security level.

<figure><img src="https://3559080615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FapjLO0A6xJKWicwzV6aG%2Fuploads%2FzeCbCrr7rK3YRD6dhPBM%2Fimage.png?alt=media&amp;token=45c03ed3-eafd-4d56-932b-159b513c1ed8" alt=""><figcaption></figcaption></figure>

Note that Ledger doesn’t operate the DApps available in the Ledger Enterprise DApps Catalog but only provides an intuitive and secure interface to access them.

#### See also

* Enable Smart Contract Interactions on Ethereum accounts
* Smart Contract Interactions on Ledger Enterprise
* Customize DApps catalog on EVM accounts


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.enterprise.ledger.com/web3-defi-and-nft/defi/ledger-enterprise-dapps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.