> For the complete documentation index, see [llms.txt](https://mtrsolution.gitbook.io/eventic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mtrsolution.gitbook.io/eventic/business-model.md).

# Business Model

Eventic offers you various ways to make money from the event tickets that are sold by the registered organizers. &#x20;

![](/files/-MJNGSOUiMWy9uPPdNtj)

## Fixed Fee

A fixed fee is an amount that is added on top of the ticket price. This fee is an additional fee that will be paid by the attendees for each ticket that they buy.

## Dynamic Fee

A dynamic fee is a percentage that you specify. This percentage will be deducted from the ticket sale price. Attendees will not pay any additional fees.

The fees above can be combined.

The business model that Eventic offers is highly profitable and gives you the ability to earn passive income right after setting up the platform.


---

# 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://mtrsolution.gitbook.io/eventic/business-model.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.
