> For the complete documentation index, see [llms.txt](https://selenium-4.gitbook.io/nexus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://selenium-4.gitbook.io/nexus-docs/docs/corporate-trust-services/overview.md).

# Corporate Trust Services

Domínio de serviço BIAN que fornece serviços de trust corporativo centrados na gestão de instrumentos de dívida e no suporte a contas de escrow.

## Serviços disponíveis

* [Create Captive Account](/nexus-docs/docs/corporate-trust-services/create-captive-account/main.md)
* [Release Captive Account](/nexus-docs/docs/corporate-trust-services/release-captive-account/main.md)

## Exemplo de uso

No âmbito da emissão de um instrumento de dívida, o banco cria uma conta captive para reter fundos em garantia, libertando-a posteriormente quando as condições contratuais associadas são cumpridas.

## Definição do papel

O domínio de Corporate Trust Services presta serviços de trust corporativo, com particular enfoque na gestão de instrumentos de dívida e no suporte a contas de escrow, incluindo a criação e a libertação de contas captive associadas a essas operações.

## Características principais

* Criar contas captive associadas a instrumentos de dívida
* Libertar contas captive quando as condições contratuais são cumpridas
* Suportar operações de escrow no contexto de trust corporativo


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://selenium-4.gitbook.io/nexus-docs/docs/corporate-trust-services/overview.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 `build a script that syncs our docs to a CMS` 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.