> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v1-pt/api-rest/helpers.md).

# Ajudantes

Esses endpoints fornecem uma forma de receber tokens por meio de Trustline e enviar quaisquer transações para a blockchain Stellar.

### Introdução

Os endpoints auxiliares são projetados para fornecer funcionalidades adicionais que complementam os recursos principais de uma API. Eles frequentemente incluem funções utilitárias que agilizam solicitações comuns, simplificam a manipulação de dados ou melhoram a experiência geral do usuário.

#### Visão geral dos endpoints auxiliares

Os endpoints auxiliares oferecem vários benefícios que aumentam tanto a eficiência do desenvolvimento quanto a satisfação do usuário. 

* **Definir Trustline:** Permite ao usuário interagir com alguns tokens.
* **Enviar Transação:** Envia a transação para a Rede Stellar com o hash assinado.
* **Obter Saldo de Múltiplos Escrows:** Este endpoint permite que os usuários recuperem os saldos de várias contas escrow simultaneamente. 

Esses endpoints garantem transações seguras aproveitando a infraestrutura da Stellar, garantindo transparência e confiabilidade.


---

# 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.trustlesswork.com/trustless-work/v1-pt/api-rest/helpers.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.