> 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/v2-en/community-and-contribution/ecosystem.md).

# Ecosystem

Discover projects building with Trustless Work, and submit yours to be listed.

Find projects building with Trustless Work.

<a href="https://www.trustlesswork.com/ecosystem" class="button primary">Open the Ecosystem</a>

### What you’ll find there

* Production apps and demos using Trustless Work escrows.
* Developer tooling and integration libraries.
* Partners and community projects.

### Get your project listed

{% stepper %}
{% step %}

### Prepare your project details

Send these basics:

* Project name + one-liner.
* Category (dApp, tooling, integration, wallet, explorer, …).
* Primary link (website or repo).
* Short description of what Trustless Work powers in your product.
  {% endstep %}

{% step %}

### Add assets (recommended)

* Logo (SVG preferred).
* 1–2 screenshots (optional).
* Links: docs, demo, X/GitHub, etc.
  {% endstep %}

{% step %}

### Contact us

Reach out through any official Trustless Work channel (site footer / socials).

We’ll confirm details and publish the listing.
{% endstep %}
{% endstepper %}

### Update an existing listing

Send the project link plus the changes you want (text, links, assets).

{% hint style="info" %}
If you’re unsure which category fits, send the details anyway.\
We’ll place it in the right section.
{% endhint %}


---

# 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/v2-en/community-and-contribution/ecosystem.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.