> 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/ledger-enterprise-documentation-home/readme.md).
# Welcome
Welcome to the Ledger Enterprise documentation home! Ledger Enterprise is a custody platform that helps businesses and financial institutions safely store, manage, and transfer digital assets. We provide world leading secure hardware and software solutions to protect your crypto from hacks and unauthorized access, while enabling teams to operate efficiently at scale.
This site is designed for administrators, operators and developers who want to setup, use and integrate with Ledger Enterprises world leading products. Below, you'll find links to our Help Centre (for day to day users) and our API Tutorials and Documentation (for developers). Version 1 API Documentation is for our current API users who are looking to automate their custody and collateral management workflows. While these flows are incredibly robust, we have also begun to build out Version 2 API's and the associated documentation. This is in response to requests for more complex and performant automation requirements from some of our clients, while maintaining the highest level of security possible.
### Jump right in
---
# 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/ledger-enterprise-documentation-home/readme.md?ask=&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.
