> For the complete documentation index, see [llms.txt](https://brd-digital.gitbook.io/brd-digital-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brd-digital.gitbook.io/brd-digital-docs/resources/contact.md). # Contact Open sign-up for individual accounts, the institutional desk for KYB, and the compliance team for eligibility. ## Getting an account You do not need to contact anyone. Sign up at [brd.digital](https://brd.digital/login) and verify your identity in the browser — see Create an Account. ## Institutional onboarding Organizations that need higher limits, multiple authorized users, or a corporate account structure onboard through KYB. Tell us about your organization, jurisdiction, and intended use case, and you will receive the requirements and a timeline in response. * **Email:** * **Contact form:** [brd.digital/contact](https://brd.digital/contact) ## Existing accounts Operational questions — a deposit, a redemption, a corridor payment, a destination approval — go to support with the operation's reference from your activity history. Institutional accounts have a dedicated desk contact. Support channels are listed in the dashboard. ## Security Suspected account compromise or a security vulnerability: , marked urgent. See Data Security. ## Eligibility and compliance Questions about eligibility, jurisdictions, or the compliance framework are answered on KYC — anything not covered there goes to the contact points above. --- # 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://brd-digital.gitbook.io/brd-digital-docs/resources/contact.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.