> 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/introduccion/readme.md).

# Bienvenido

Esta es la documentación para desarrolladores de Trustless Work.

Trustless Work es **Escrow-as-a-Service (EaaS)** para **escrow de stablecoin**. Construye **no custodial** flujos con **hitos**, aprobaciones y disputas. Los contratos se ejecutan en **Stellar (Soroban)**. Tu aplicación los controla vía API o SDK.

{% embed url="<https://youtu.be/AZHv48hYxNg>" %}

### Comienza aquí

<table data-view="cards"><thead><tr><th>Tema</th><th data-card-target data-type="content-ref">Enlace</th></tr></thead><tbody><tr><td>Inicio rápido para desarrolladores</td><td><a href="/trustless-work/v1-es/introduccion/developer-resources.md">Guía para desarrolladores</a></td></tr><tr><td>Solicitar una clave API</td><td><a href="/trustless-work/v1-es/introduccion/developer-resources/request-api-key.md">Solicitar clave de API</a></td></tr><tr><td>Conceptos básicos de la API REST (URLs base, límites, Swagger)</td><td><a href="/trustless-work/v1-es/api-rest/introduction.md">Introducción</a></td></tr><tr><td>SDK de React (hooks)</td><td><a href="/trustless-work/v1-es/escrow-react-sdk/primeros-pasos.md">Primeros pasos</a></td></tr><tr><td>Escrow Blocks SDK (bloques de UI)</td><td><a href="/trustless-work/v1-es/escrow-blocks-sdk/primeros-pasos.md">Primeros pasos</a></td></tr><tr><td>Conceptos de escrow (roles, ciclo de vida, tipos)</td><td><a href="/trustless-work/v1-es/introduccion/technology-overview.md">Diseño de escrow</a></td></tr><tr><td>Rails de Stellar (trustlines, wallets)</td><td><a href="/trustless-work/v1-es/introduccion/stellar-and-soroban-the-backbone-of-trustless-work.md">Red Stellar</a></td></tr><tr><td>Casos de uso por industria</td><td><a href="/trustless-work/v1-es/casos-de-uso-por-industria/introduccion.md">Introducción</a></td></tr><tr><td>Todos los enlaces (docs, herramientas, externos)</td><td><a href="/trustless-work/v1-es/introduccion/readme/links.md">Enlaces</a></td></tr></tbody></table>

### Lo que puedes construir

* Mantén fondos en escrow usando **contratos inteligentes no custodiales**.
* Agrega **lógica de liberación programable** a tu aplicación o marketplace.
* Soporte **hitos**, aprobaciones, liberaciones parciales y disputas.
* Configura **roles y permisos** por firmante.
* Lanza más rápido sin escribir contratos de escrow desde cero.

### Casos de uso comunes de escrow

* Escrow para marketplaces de comercio electrónico y servicios.
* Escrow para freelancers y contratos con pagos por hitos.
* Depósitos de seguridad para alquileres y reservas.
* Crowdfunding y pre-pedidos con pagos condicionales.
* Subvenciones y desembolsos programáticos.

### Pruébalo en minutos

<a href="https://dapp.trustlesswork.com/" class="button primary">Abrir Backoffice dApp</a>

<a href="https://demo.trustlesswork.com/" class="button secondary">Abrir dApp demo</a>

<a href="https://api.trustlesswork.com/docs" class="button secondary">Abrir Swagger (Mainnet)</a>

<a href="https://github.com/Trustless-Work" class="button secondary">Ver GitHub</a>


---

# 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/introduccion/readme.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.