Marketplace App Pricing

Load this reference when helping a creator price a paid public app, paid
marketplace flow, app-owned plan catalog, prepaid run pack, subscription,
subscription usage plan, trial runs, or public app cost model.

Default Stance

Prefer prepaid usage packs and subscriptions. Do not recommend tiny payments or
per-run microtransactions as the default Breyta marketplace model.

Breyta paid apps can have low operational overhead. The main variable costs are
payment fees, Breyta platform fees, run costs, external API or LLM costs, and
creator support burden. Use those actual costs to check viability, but price
from buyer value first.

Use pricing guidance as advisory. Do not block publishing unless product policy
or release checks already enforce a hard rule.

Pricing Model Choice

Pick the pricing model from the buyer's usage pattern:

Do not describe :usage as postpaid pay-as-you-go. In Breyta it is a prepaid
run pack: the buyer pays once for a fixed number of successful runs. Do not
describe :subscription-usage as having paid overages; included runs reset on
renewal and exhaustion blocks more runs until renewal or a future product
change.

Cost Floor

Estimate the cost floor before recommending a price:

1. Get completed-run cost data when available.
2. Include configured :metering costs for paid API, enrichment, tool, search,
   or provider steps.
3. Include LLM token estimates when Breyta has provider/model pricing.
4. Add external API or LLM costs the creator pays outside Breyta.
5. Add payment fee and Breyta platform fee assumptions.
6. Add a support burden assumption when the app requires setup help, judgment,
   or ongoing customer handling.
7. Flag any unknown-cost line items.

Use :metering and run cost estimates for creator cost visibility. Do not
imply step metering is buyer billing.

Recommendation Heuristics

• Price from buyer value first, then verify the cost floor.
• Treat Breyta operational overhead as low by default.
• Prefer packs and subscriptions over small one-time charges.
• If transaction fee drag is meaningful, bundle more runs or switch to a
  subscription.
• If per-run cost is unknown, recommend a smaller trial cap, smaller included
  run quantity, or prepaid pack until real runs are measured.
• If support burden is high, favor a subscription.
• If usage is frequent and predictable, favor subscription usage.
• If usage is irregular but repeatable, favor prepaid usage packs.
• If the app is mostly a demo or lead magnet, use free or trial runs instead of
  tiny paid checkout.

Starting Package Examples

Use concrete packages when the creator has no pricing anchor:

If the creator suggests a tiny per-run checkout, bundle it into a prepaid pack
or subscription. Example: replace $1/run with $49 for 100 runs, $99 for
500 runs, or $49/mo with included runs.

Margin Worksheet

For each recommendation, estimate:

1. Buyer price
2. Breyta platform fees and payment fees
3. Run cost at full included usage
4. External API, search, enrichment, or LLM costs
5. Support allowance
6. Remaining gross margin

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

Agent Output

When advising on a paid marketplace app, include:

• recommended pricing type and rationale
• suggested price, currency, included runs, and trial runs
• estimated cost per successful run
• estimated gross margin at expected usage levels
• fee-drag warning when the proposed price is too small
• one recommended package and, when useful, one alternative package
• risks: unknown step costs, AI-heavy costs, external API costs, support burden
• source-authored plan shape when needed, using app-owned monetization:

:marketplace
{:visible true
 :app
 {:app-id "example-app"
  :app-name "Example App"
  :app-primary-flow-slug "example-app"
  :app-flow-slugs ["example-app"]
  :monetization
  {:plans
   [{:plan-id "starter"
     :name "Starter"
     :default true
     :pricing {:type "subscription-usage"
               :amount 49
               :currency "usd"
               :interval "month"
               :unit "run"
               :included-quantity 100}
     :trial {:runs 5}}
    {:plan-id "run-pack"
     :name "Run Pack"
     :pricing {:type "usage"
               :amount 99
               :currency "usd"
               :unit "run"
               :included-quantity 500}}]}}}

Publishing paid settings, Discover visibility, marketplace visibility, release,
and public install-facing claims still require explicit flow-author approval.