# Revenue & Sustainability

Our business model is built on small, transactional fees charged at points of high value. This creates a sustainable, self-funding ecosystem where the platform's success is directly aligned with the success of its users.

#### Core Revenue Streams (via x402pay)

* **🤖 AI-Assisted Project Creation Fee**
  * **Who Pays:** Project Creator
  * **Action:** When using our Amazon Bedrock-powered AI Agent to draft a complete project scope and smart contract from a simple chat command.
  * **Rationale:** This monetizes a powerful convenience feature, covering LLM operational costs and establishing a "pay-for-value" model.
* **✅ Verified Application "Signal" Fee**
  * **Who Pays:** Freelancer (Worker)
  * **Action:** When applying to a public project listing.
  * **Rationale:** This small fee prevents spam and ensures creators receive serious applications, allowing dedicated freelancers to stand out.
* **🏆 Final Payout & Reputation Fee**
  * **Who Pays:** Project Creator
  * **Action:** Upon approval of the final project milestone.
  * **Rationale:** This is our core success-based fee. It's charged only when a project is successfully completed, covering the cost of the on-chain payout and the minting of reputation SBTs.
* **⚖️ Dispute Resolution Bond**
  * **Who Pays:** The party initiating a formal dispute.
  * **Action:** To engage a human arbiter.
  * **Rationale:** This bond prevents frivolous disputes and ensures both parties are committed to the resolution process. The funds are used to compensate the arbiter.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://collabrachain.gitbook.io/docs/getting-started/revenue-and-sustainability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.