> For the complete documentation index, see [llms.txt](https://sbsweb3hubs-organization.gitbook.io/angelforge-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sbsweb3hubs-organization.gitbook.io/angelforge-white-paper/project-revenue.md).

# PROJECT REVENUE

**Project Revenue**

**Project Revenue** is generated through:

* a commission collected from startups at the moment they receive a tranche of funding;
* a commission from the revenue generated by native staking of frozen assets;
* fees for additional services and offerings provided by the platform;
* revenue from the operation of the lending protocol.

**Platform fee**

        A commission fee is established for using the AngelForge tools. The fee is charged to the startup and is incurred only when funds are actually disbursed to the startup for its financing. The fee is determined using a progressive scale based on the total amount of funds received from Participants during the funding phase, but in any case, it cannot exceed 5%. This model does not imply additional costs for the startup that would increase the cost of work, and no commission is charged to Participants.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sbsweb3hubs-organization.gitbook.io/angelforge-white-paper/project-revenue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.