> For the complete documentation index, see [llms.txt](https://docs-fusd.falcon.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-fusd.falcon.finance/introduction.md).

# Introduction

### Overview&#x20;

fUSD is a fully reserved stablecoin issued by Anchorage Digital Bank, National Association, and built in readiness for the federal stablecoin framework established by the GENIUS Act.

fUSD is designed for institutional use, mainly in treasury management, trading collateral, position coverage, and settlement among regulated counterparties. It is issued in partnership with Falcon Finance, which serves as a partner and primary distribution channel.

### Issuer&#x20;

fUSD is issued by Anchorage Digital Bank, N.A., a global crypto platform that enables institutions to participate in digital assets through trading, staking, custody, governance, settlement, stablecoin issuance, and the industry’s leading security infrastructure. As issuer, Anchorage Digital Bank is responsible for the custody and segregation of fUSD reserves, the minting and redemption of fUSD against U.S. dollar deposits, and the regulatory reporting required of a federally supervised stablecoin issuer.


---

# 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://docs-fusd.falcon.finance/introduction.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.
