> For the complete documentation index, see [llms.txt](https://help.imagine.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.imagine.art/workflows/app-builder/app-marketplace.md).

# App Marketplace

## App Marketplace

The Marketplace is where community-published apps live. Users discover, search, use, and remix apps built by other creators. As a publisher, you earn credits every time someone uses or clones your app - turning your workflows into a source of ongoing income.

***

### How the Marketplace Works

When you publish an app with Community visibility, it goes through moderation review. Once approved, it appears in the Community tab of Imagine Apps - searchable, categorized, and available to every ImagineArt user.

Community users can:

* Use your app: Enter inputs and generate assets. Credits are deducted from their account.
* Like your app: Help surface popular apps in the Marketplace.
* Remix your app: Clone it to create their own independent version (if you enabled Remix Access).

***

### How You Earn Credits

You earn credits in two ways:

#### From app usage

Every time someone runs your app, the credit cost breaks down like this:

Total cost to user = Base cost + Your earning tier

<table><thead><tr><th width="205.66015625">Component</th><th>How It Works</th></tr></thead><tbody><tr><td>Base cost</td><td>The sum of all generation nodes in your workflow, calculated automatically (e.g., 73.5 credits). This covers the AI model usage.</td></tr><tr><td>Your earning tier</td><td>The additional amount you set during publishing — None (0), Low (10), Medium (20), or High (30) credits. This goes directly to your account.</td></tr></tbody></table>

Example: Your app has a base cost of 100 credits, and you set the earning tier to High (30). When a user runs it, they pay 130 credits total - 100 covers generation, and 30 are transferred to you.

#### From app cloning

When someone clones your app, a fixed credit amount is deducted from them and transferred to your account. This applies every time, regardless of the earning tier you've set.

***

### Tracking Your Earnings

All credit activity is tracked in the My Apps view. Each app card shows:

<table><thead><tr><th width="205.9453125">Metric</th><th>What It Tracks</th></tr></thead><tbody><tr><td>Credits Earned</td><td>Total credits from usage and cloning combined</td></tr><tr><td>Runs</td><td>Number of times the app has been used</td></tr><tr><td>Clones</td><td>Number of times the app has been remixed</td></tr><tr><td>Likes</td><td>Total likes from community users</td></tr></tbody></table>

Your full credit history including individual transactions is accessible from your account.

***

### Maximizing Your App's Reach

Your app competes with every other app in the Marketplace. Here's what separates the apps that get used from the ones that don't:

* *Choose a clear, specific name. Users search by keywords. "Product Photo Background Remover" will outperform "My Cool App" every time.*
* *Upload a strong thumbnail. The thumbnail is the first thing users see when browsing. Use a compelling output image or a custom cover that shows what your app creates.*
* *Add presets. Apps with presets convert better. A new user can generate a result in one click — no prompt writing required.*
* *Set a fair earning tier. Higher tiers earn more per use but increase the cost for users. Start with Low or Medium and adjust based on demand.*
* *Enable Remix Access. Allowing clones increases your app's visibility and earns you credits from every clone, while building your reputation as a creator.*
* *Write a clear description. Tell users what your app does, what inputs it needs, and what kind of results it produces. Don't make them guess.*

***

### Moderation

All Community apps go through a review before going live. The moderation team checks for quality, safety, and adherence to community guidelines.

Private and Team apps are published instantly without review.


---

# 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://help.imagine.art/workflows/app-builder/app-marketplace.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.