Marketplace App Pricing

Quick Answer

For paid Breyta marketplace apps, start with subscriptions or prepaid usage
packs. Avoid tiny payments and per-run microtransactions.

Breyta apps can have very little operational overhead, so the price floor can be
low. The recommended price should still reflect buyer value, payment fees,
Breyta platform fees, run costs, external API or LLM costs, and support burden.

Choose A Pricing Model

Use case	Recommended model
Recurring outcome, such as weekly reports or ongoing monitoring	Subscription
Recurring app with included successful runs each month	Subscription usage
Repeat use with uneven timing	Prepaid usage pack
Fixed utility with enough value to justify checkout	One-time purchase
Demo, lead magnet, or sampling	Free app or trial runs

Usage pricing in Breyta means prepaid run packs. The buyer pays once for a
fixed number of successful completed runs. Subscription usage includes a fixed
number of successful runs per billing period. It does not bill paid overages
today; when included runs are exhausted, the buyer is blocked until renewal.

Estimate The Cost Floor

Use run cost estimates before finalizing app pricing:

Avg Estimated Run Cost on the flow page
data.run.costEstimate from breyta runs show
step-level :metering for fixed API, enrichment, or tool request costs
LLM token estimates when model pricing is known
external provider costs paid outside Breyta
expected creator support burden

Run cost estimates are advisory. They help creators understand margins, but
they are not the buyer billing ledger.

Pricing Rules Of Thumb

Price from buyer value first, then verify margin.
Use prepaid packs or subscriptions to avoid fixed-fee drag from tiny charges.
If per-run cost is unknown, start with a smaller trial or included-run limit.
If support burden is high, prefer subscription pricing.
If usage is predictable, use subscription usage.
If usage is repeatable but uneven, use prepaid packs.
If the app is mostly a demo, offer trial runs instead of a tiny paid checkout.

Good Starting Shapes

Use these as starting points, then adjust for buyer value, costs, and support:

App pattern	Better starting shape
Weekly report, monitor, or alert	`$49/mo` with 100 included runs and five trial runs
High-value AI review or enrichment	`$99/mo` with 50 included runs and a smaller trial cap
Irregular batch utility	`$99` prepaid pack with 500 successful runs
Fixed diagnostic or setup utility	`$199` one-time purchase when the result is valuable enough to justify checkout
Demo or lead magnet	Free access or five trial runs

If the first instinct is $1/run, bundle it. Use a $49 or $99 prepaid
pack, a subscription, or a trial instead.

Margin Worksheet

Use this quick worksheet before recommending a price:

Start with the buyer price.
Subtract Breyta platform fees and payment fees.
Subtract expected run costs at full included usage.
Subtract external API, search, enrichment, or LLM costs.
Subtract a support allowance when the creator expects setup help or manual
follow-up.
Check whether the remaining margin is worth selling and supporting.

Example: a $99 prepaid pack with 500 runs gives the creator $0.198/run
before fees. If estimated run and external costs are $0.04/run, full usage
costs about $20. The remaining $79 before fees and support is the margin
pool. If that is too thin, reduce included runs, raise the pack price, or move
to a subscription.