Plans & Credits

Plans live in one org-level catalog, on Deploy > Storefronts below the Storefront list. Define a plan once; it is offered on Storefronts and assigned to assets on their Assignments tab. A subscriber keeps one subscription and one credit pool per plan no matter how many Storefronts offer it or how many Portals admit it.

Plan fields

• Name and description - what end users see on the pricing screen.
• Price and billing frequency - monthly or yearly; a price of 0 makes a free plan (no Stripe involved).
• Trial days - optional free trial on paid plans.
• Credits per period - the usage allowance each subscriber gets, refreshed every billing cycle. Changing it later applies to existing subscribers from their next cycle. On a paid plan the field gains a slider from zero to break-even (the allowance at which a subscriber who uses every credit leaves no profit) and a receipt showing price, minus Stripe and platform fees, minus the credits at the on-demand rate, equals the gross profit if every credit is used. Drag or type and both update. The editor warns before you save a plan that could lose money.
• Allow own OpenAI API key (BYOK) - subscribers can add their own key; runs on it don't consume their credits.
• Offered in - read-only: the Storefronts that carry this plan.

Creating a plan creates its group. Renaming the plan renames the group.

What a plan unlocks

Nothing on the plan itself. Open the asset - a Flow, Agent, App, or Suite - and add the plan on its Assignments tab. The plan editor shows a read-only summary of what subscribers can reach. Free plans work exactly the same way: a $0 plan assigned to an asset is a self-serve library anyone who signs in can join.

Want everything paywalled? Assign assets only to plans. Want a free sample? Assign it to a $0 plan and make that plan the default on the Storefront. Visitors sign in with their email first, then start on it.

Plan contents

Below the plan catalog, Plan contents shows every asset in your library against every live plan in one grid, cheapest plan first. Tick a cell to assign the asset to that plan, untick to remove it - the same assignments the asset's Assignments tab shows. When a pricier plan lacks something a cheaper plan includes, the cell is highlighted and a notice at the top offers to add the missing items in one click, so a Pro tier never ships with less than Basic.

How credits work

• Each subscription has its own pool: the plan's allowance, refreshed each period.
• Groups never carry credits - only plans do. A run by a user who has no live plan but reaches the asset through an Assigned Group is funded by your organization's credits.
• A user with several live plans has one aggregate pool: a run draws from the best plan first (live status, then highest price, then oldest), and moves to the next plan when that pool is empty. The user is only refused when every pool is spent, and the message names the plan that ran out.
• At around 70% consumption the end user sees a warning; at exhaustion they're blocked with an upgrade/top-up prompt.
• Credit packs are one-time top-ups you can offer alongside plans. Pack credits sit in a bonus pool that survives the period reset and is consumed only after the monthly allowance runs out.

Pricing changes

Editing a paid plan's price creates a new price in Stripe - existing subscribers keep their current price (grandfathered); new subscribers pay the new one. Archiving a plan hides it from Storefronts; it can't be archived while it has active subscribers.

Giving access without payment

• Comp a plan from Users & Groups - full plan benefits, no Stripe subscription.
• Provision via the API - your system takes payment, then creates the account with plans attached.
• An Assigned Group - for people you never bill: add them to a group, assign the group to the asset, and the runs come out of your organization's credits.