Docs

Selling packages

You spent weeks distilling what your agents know about a framework, a domain, a regulation. That knowledge saves other teams the same weeks — and they'll happily pay for the shortcut. Here is the complete flow.

01

Publish your package

Selling starts with a published package — signed, scanned, verified. Follow the publishing guide first; everything there applies unchanged.

Publishing guide →
02

Set a price

In your account dashboard, every package has a price field: type an amount in euros, save, done (up to €500 per package in v1). Clear the field and it’s free again — existing buyers keep access either way. Scripts can use the API directly:

PUT /api/v1/account/price        # session-authenticated
{ "name": "my-package", "price_cents": 1900 }   # €19.00
Open your dashboard →
03

Buyers check out via Stripe

On a paid package, the download responds with the price and a checkout link. Buyers pay once through Stripe — cards, Apple Pay, the usual — and the purchase is tied permanently to their account.

04

Buyers install like any package

After purchase, installs work exactly like free packages: full verification, lockfile pinning, CI access via read tokens. No license keys, no friction.

lean-ctx pack install @you/my-package   # just works after purchase

The rules, upfront

One-time purchase v1 sells perpetual access per account: buy once, install forever, including all future versions of the package.
You keep 85% The platform fee is 15% of each sale, Stripe processing included. Payouts run monthly from 50 € accumulated — SEPA transfer or invoice, full terms on the pricing page.
Free to list No listing fees, on every plan. Selling does not require Pro.
Price changes Raise or lower any time — it affects new buyers only. Existing purchases are never invalidated.
Refunds & abuse Handled case by case via Stripe. Packages that violate the secret-scanning or content rules are yanked regardless of price.
Your keys, your content Selling changes distribution, not ownership. The package stays signed with your key and exportable by every buyer.

Buyers see exactly what they pay for before checkout: the package page shows the quality score, token ROI, layer stats and full version history — evidence, not promises. That transparency is why paid packages sell. Questions? The trust model covers what the registry guarantees on your behalf.