> 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/dapps-oss/offerhub-marketplace/componentes-do-sistema.md).
# Componentes do sistema
### OfferHub Frontend
* Interface do Marketplace (navegar, comprar, vender)
* Interface de Saldo (recarregar, sacar)
* Interface da linha do tempo do pedido (fundado, em andamento, em disputa, liberado)
### Orquestrador OfferHub (API Backend)
* Cria e gerencia pedidos
* Coordena chamadas Airtm e Trustless Work
* Gerencia webhooks e eventos de escrow
* Mantém log de auditoria e estado interno
### Módulo de Integração Airtm
* Criar intenções de pagamento
* Receber webhooks de pagamento
* Iniciar pagamentos / retiradas
* Recuperar status da transação
### Módulo de Integração Trustless Work
* Criar escrow por pedido
* Atualizar estados de marcos
* Abrir disputas
* Executar transações de liberação/reembolso
### Backoffice
Para este protótipo espera-se que a resolução de disputas e liberações manuais através do nosso [dApp Bakcoffice](/trustless-work/v1-pt/dapps-oss/backoffice.md). Também aproveitaremos o [visualizador de escrow](/trustless-work/v1-pt/dapps-oss/visualizador-de-escrow.md).
* Gestão de casos de disputa
* Substituições manuais e tentativas de nova execução
* Monitoramento e exportação de auditoria
---
# 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/dapps-oss/offerhub-marketplace/componentes-do-sistema.md?ask=&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.
