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

# Welcome

This is the developer documentation for Trustless Work.

Trustless Work is **Escrow-as-a-Service (EaaS)** for **stablecoin escrow**. Build **non-custodial** flows with **milestones**, approvals, and disputes. Contracts run on **Stellar (Soroban)**. Your app drives them via API or SDK.

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

### Start here

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Developer Quickstart</td><td><a href="/trustless-work/introduction/developer-resources.md">Developer Guide</a></td></tr><tr><td>Request an API key</td><td><a href="/trustless-work/introduction/developer-resources/request-api-key.md">Request API Key</a></td></tr><tr><td>REST API basics (base URLs, limits, Swagger)</td><td><a href="/trustless-work/api-rest/introduction.md">Introduction</a></td></tr><tr><td>React SDK (hooks)</td><td><a href="/trustless-work/escrow-react-sdk/getting-started.md">Getting Started</a></td></tr><tr><td>Escrow Blocks SDK (UI blocks)</td><td><a href="/trustless-work/escrow-blocks-sdk/getting-started.md">Getting Started</a></td></tr><tr><td>Escrow concepts (roles, lifecycle, types)</td><td><a href="/trustless-work/introduction/technology-overview.md">Escrow Design</a></td></tr><tr><td>Stellar rails (trustlines, wallets)</td><td><a href="/trustless-work/introduction/stellar-and-soroban-the-backbone-of-trustless-work.md">Stellar Network</a></td></tr><tr><td>Use cases by industry</td><td><a href="/trustless-work/use-cases-by-indutry/introduction.md">Introduction</a></td></tr><tr><td>All links (docs, tools, external)</td><td><a href="/trustless-work/introduction/readme/links.md">Links</a></td></tr></tbody></table>

### What you can build

* Hold funds in escrow using **non-custodial smart contracts**.
* Add **programmable release logic** to your app or marketplace.
* Support **milestones**, approvals, partial releases, and disputes.
* Configure **roles and permissions** per signer.
* Launch faster without writing escrow contracts from scratch.

### Common escrow use cases

* Marketplace escrow for e-commerce and services.
* Freelance and contract escrow with milestone payouts.
* Security deposits for rentals and reservations.
* Crowdfunding and pre-orders with conditional payouts.
* Grants and programmatic disbursements.

### Try it in minutes

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

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

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

<a href="https://github.com/Trustless-Work" class="button secondary">View 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 dynamically 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/introduction/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 `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.