Pricing story

Price the application clearly on the website, then enforce usage inside the app itself.

The site should explain plans, limits, and why stronger models cost more. The ClastX application should actually track usage, switch models, and stop people before margins disappear.

available now

Preview

Use the ClastX application in preview mode while the public site explains the offer, the workflows, and the paid path.

ClastX application in preview mode

Local chat history and saved snapshots

Model switch UI and credit simulation

Project brief, pricing, and billing scaffolding

Best first paid plan

Starter

$19

For lighter coding sessions and a careful first paid tier.

500 included credits per month

Hard stop at 100% unless user upgrades or tops up

250 extra credits for $7

All models available, but better models burn more credits

Best balance

Pro

$39

For regular developers who want more room before a hard stop.

1250 included credits per month

Hard stop at 100% unless user upgrades or tops up

500 extra credits for $12

All models available, but better models burn more credits

Highest allowance

Max

$79

For heavier usage, faster model switching, and more GPT-5.5 room.

3000 included credits per month

Hard stop at 100% unless user upgrades or tops up

1000 extra credits for $20

All models available, but better models burn more credits

Model burn rates

Let users switch models, but make the burn rate obvious so stronger models feel premium and the margins stay intact.

Test it in the app

mini

GPT-5.4 mini

1x credit burn

Best default for most coding sessions and the safest way to preserve margin.

Input: $0.75/1M

Output: $4.5/1M

5.4

GPT-5.4

3.3x credit burn

Stronger reasoning for harder implementation work, but it burns credits much faster.

Input: $2.5/1M

Output: $15/1M

5.5

GPT-5.5

6.7x credit burn

Premium model for the hardest requests. Keep this behind higher-value usage.

Input: $5/1M

Output: $30/1M

What your first dollars should buy

Spend on response quality, usage protection, and the ability to get paid back.

OpenAI credits so coding quality stays high

Hosting and support only after live usage starts

Usage metering and stop behavior before broad access

Billing infrastructure only when the paid story is sharp

Before checkout exists

The job right now is to make the paid future feel safe and easy to understand.

If the hard-stop rule is clear, the included credits are obvious, and model switching feels fair, adding Stripe later becomes an implementation task instead of a pricing panic.

Open the app Open billing preview

Before payments go live

Make sure the product is ready to protect profit from day one.

The homepage promise is clearly about coding value, not generic AI.

The first paid plan can be explained in one sentence.

Credit burn is visible and heavy usage stops before margin disappears.

Users can switch models, but stronger models drain credits faster.

Pricing FAQ

Why not offer unlimited usage right away?

Because unlimited usage can destroy margin fast when developers lean on stronger models. ClastX should meter by usage cost and stop at the plan limit unless the user upgrades or buys a top-up.

How should model switching work?

All models can stay available, but they should burn credits at different rates. That gives developers choice while protecting the business from expensive heavy users.

What should happen at 100% usage?

ClastX should stop, show the remaining choices clearly, and push the user to upgrade or buy more credits. Silent overages are the easiest way to lose money.