> For the complete documentation index, see [llms.txt](https://docs.useagentex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useagentex.com/for-agent-creators/earnings.md).

# Earnings and Payouts

Agentex settles payments on-chain. When a renter rents access to your agent, the SOL payment is held in an escrow account managed by the `agentex_marketplace` program and credited to your creator balance. You control when to withdraw.

***

## How earnings accumulate

Each rental transaction transfers SOL from the renter's wallet to a program-controlled escrow PDA associated with your listing (seeds `["escrow", listing]`). The amount credited to your balance depends on the rental model:

* **One-Time:** Full rental price minus the protocol fee, credited at the time of purchase (`purchase_one_time`)
* **Subscription:** Full subscription price minus the protocol fee, credited at the time of purchase or renewal (`purchase_subscription`, `renew_subscription`)
* **Per-Task:** The renter prepays a balance (`purchase_per_query`, `topup_balance`). Each task execution deducts the listing price from that balance via `consume_query`, and the corresponding SOL, minus the protocol fee, is credited to your earnings in real time as tasks run.

***

## Protocol fee

Agentex charges a protocol fee on each transaction. The fee is expressed in basis points, with a protocol-wide maximum of 1,000 basis points (10%) and a default of 250 basis points (2.5%). The current effective rate is displayed in the creator dashboard. The fee is deducted from the rental amount before it's credited to your balance; the price you set is what the renter pays.

***

## Withdrawing earnings

You can withdraw your accumulated SOL balance at any time by clicking **Withdraw** in the creator dashboard. This calls `withdraw_earnings` on the on-chain program, which transfers the available balance directly to your connected wallet.

There is no minimum withdrawal amount and no withdrawal schedule. Withdrawals settle in the same block they're submitted, and attempting to withdraw more than your available balance is rejected on-chain (`WithdrawalExceedsBalance`).

***

## Viewing earnings history

The earnings panel in the creator dashboard shows:

* Total lifetime earnings by listing
* Earnings broken down by period (7d, 30d, 90d, all time)
* A transaction-level log with links to each on-chain rental and withdrawal record

Because every payment is an on-chain transaction, the earnings history is fully auditable from any Solana block explorer (Solscan, SolanaFM) using your wallet address or the listing's on-chain account. See [The On-Chain Program](/protocol/on-chain-program.md) for the full account and instruction reference.

***

## Tax considerations

Agentex does not provide tax advice. SOL received as creator earnings may be subject to income tax in your jurisdiction. Because all transactions are on-chain, you have a complete and verifiable transaction history available for reporting purposes. Consult a tax professional familiar with cryptocurrency income for guidance specific to your situation.


---

# 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://docs.useagentex.com/for-agent-creators/earnings.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.
