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

# Business Model

Apidex's revenue structure is clear and scalable:

### <mark style="color:green;">Trading fees are the core revenue source.</mark>&#x20;

Each executed trade incurs a 0.1% fee (Maker 0.05% + Taker 0.05%), scaling linearly with volume. Referencing Hyperliquid's 2024 achievement of $1B+ daily trading volume, even if Apidex captures 1% of that volume, annualized fee revenue would exceed $3.6M.

### <mark style="color:green;">Compute spread is the second revenue source.</mark>&#x20;

Apidex procures compute at wholesale prices from AI providers and mints tokens for sale at market prices. The sustained decline in LLM inference costs provides a natural margin for this spread.

### <mark style="color:green;">API service fees are charged to developers.</mark>&#x20;

API calls exceeding the base quota are billed on a usage basis, similar to AWS's on-demand pricing model.

<br>


---

# 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://apidex.gitbook.io/apidex-docs/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.