> 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-es/api-rest/helpers.md).

# Ayudantes

Estos endpoints proporcionan una forma de recibir tokens a través de Trustline y enviar cualquier transacción a la blockchain de Stellar.

### Introducción

Los endpoints auxiliares están diseñados para proporcionar funcionalidades adicionales que complementan las características principales de una API. A menudo incluyen funciones utilitarias que agilizan solicitudes comunes, simplifican la manipulación de datos o mejoran la experiencia general del usuario.

#### Descripción general de los endpoints auxiliares

Los endpoints auxiliares ofrecen varios beneficios que mejoran tanto la eficiencia del desarrollo como la satisfacción del usuario. 

* **Establecer Trustline:** Permite al usuario interactuar con algunos tokens.
* **Enviar transacción:** Envía la transacción a la red Stellar con el hash firmado.
* **Obtener saldo de múltiples escrow:** Este endpoint permite a los usuarios recuperar los saldos de varias cuentas escrow simultáneamente. 

Estos endpoints garantizan transacciones seguras aprovechando la infraestructura de Stellar, asegurando transparencia y fiabilidad.


---

# 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-es/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.