Marketplace Seller Guide: Publish Recipes & Feature Packs

The Alchemist Marketplace is open to third-party sellers. If you have built a reusable capability — a Feature Pack, a full Recipe, or a thematic bundle — you can publish it, set your price, and get paid directly to your own Stripe account on each purchase.

Getting Started: Seller Onboarding

To sell on the Marketplace:

1. Open the seller page — click Sell Recipes in the Alchemist sidebar, or Sell a Recipe on the Recipes & Marketplace page.
2. Create your seller profile — under Become a creator, enter a Display name and an optional Bio, then click Create seller profile. Each organization can have one seller profile.
3. You can now create draft listings. The verified badge is set by Chipp; it is not part of self-serve onboarding.
4. Connect your Stripe account. Before you publish any paid listing, you must connect a Stripe account that can accept charges. Buyers pay you directly on that account. A paid listing cannot be published (or bought) until the account is connected and can accept charges.

Packaging a Recipe or Feature Pack

Pack manifest

Every Feature Pack is defined by a manifest that declares:

• packId — unique identifier (e.g. supply-chain-visibility)
• name — human-readable display name
• description — what the pack does and what it provides
• version — semantic version of this pack release
• dependencies — other pack IDs (and version ranges) this pack requires
• configSchema — the configuration knobs buyers can set at install time
• files — the source files the pack contributes
• migrations — database migration scripts (if any)
• agentGuidance — notes the Alchemist agent uses when working inside a project that has this pack installed

Recipe manifest

A Recipe manifest wraps one or more Feature Packs into a cohesive composition:

• recipeKey — unique key (e.g. supply-chain-ops)
• name and description — what the recipe builds
• version — semantic version
• packs — ordered list of pack IDs this recipe composes
• configSchema — top-level knobs promoted from underlying packs
• defaults — default values for knobs
• workflows — named workflow templates bundled with this recipe
• prompts — agent-prompt templates
• assets — screenshots, demo links, and branding for the listing

Dependencies and version ranges

Declare dependencies conservatively. If your pack only works with specific versions of another pack, express that as a version range (e.g. >=1.0.0 <2.0.0). Overly narrow ranges block buyers from using your pack alongside newer dependencies; overly broad ranges may expose your pack to breaking changes.

Writing the Listing

In the seller dashboard, a listing and each of its versions take these fields:

Setting Prices

One-time license price

This is what buyers pay at purchase to receive the source code and perpetual use rights. You set this in your seller dashboard when you create a draft version. Once you have recorded a price recommendation for the listing, the price must fall within 50%-200% of the recommended one-time price, or the server rejects the version.

Maintenance subscription price

Maintenance is priced annually by the seller. You may include first-year Maintenance in the one-time price (common for premium listings) or price it separately. Buyers who cancel Maintenance keep their source and license.

Pricing recommendations

Under Price recommendation, enter Estimated effort (hours), Complexity, Dependencies, Included workflows, and Support level, then click Compute recommendation. The result is a recommended one-time price and annual Maintenance price, with the reasoning shown. When comparable listing prices are supplied, they are blended in at 30%.

You set your own price, within the 50%-200% band described above.

Marketplace Economics

Platform fee

Chipp charges a platform fee on each transaction. The fee is configurable and currently set at 30% of the gross purchase price (3000 basis points).

The fee is:

• Applied at transaction time and snapshotted to the transaction record. A later fee change never retroactively alters a historical transaction.
• Deducted at charge time: Chipp’s fee is taken out of the charge on your Stripe account as an application fee, so it never reaches your balance.
• Visible: the Sales ledger on your seller dashboard lists each sale with your net amount, its status, and the date.
• Per-listing overridable: Chipp may negotiate a different fee rate for specific listings or programs (e.g. launch promotions, verified publisher programs). Any override is applied per-listing and documented on the transaction record.

How you get paid

Your net = gross purchase price - platform fee

At the default 30% fee: a $100 listing purchase results in a$30 platform fee and $70 for you.

Every pack, recipe, bundle, and Maintenance sale is charged on your own Stripe account (a Stripe Connect direct charge):

• Stripe pays you directly. The charge lands in your Stripe balance, and Stripe pays it out to your bank on your normal Stripe payout schedule. Chipp never holds your money and never runs a transfer to you.
• You are the merchant of record for your sales. The buyer’s card statement and receipt show your Stripe account.
• Chipp’s fee is deducted at charge time as an application fee on the charge. Your Stripe dashboard shows the gross charge and the fee.
• Refunds and disputes are handled on your Stripe account. A refund comes out of your Stripe balance. When a sale is refunded, Chipp returns its fee in proportion to the amount refunded, whether the refund was made by Chipp support or by you from your Stripe dashboard. On a dispute, Stripe’s normal dispute process and fees apply to your account.

Each sale appears in your Sales ledger as paid by Stripe, with any refund shown on the same row.

Maintenance revenue

Maintenance subscription renewals follow the same fee structure as the initial purchase. Auto-renew charges the card the buyer saved on your Stripe account at purchase, on the renewal date; buyers get a reminder email about 7 days before. A buyer who cancelled auto-renew can still renew by hand, and each renewal is its own sale on your Stripe account. If your Stripe account cannot accept charges on the renewal date, the renewal does not go through.

Coupons and grants

Coupons are issued by Chipp. A coupon must cover the full price: a redemption charges nothing, so neither Chipp nor you receives payment, and the buyer receives a full license and the included Maintenance year. Chipp may separately compensate sellers for grant-covered sales under program agreements.

Versioning and Updates

Releasing a new version

To release a new version of an existing listing:

1. Select the listing and, under New draft version, enter the new Version, prices, and a Changelog describing what changed. Click Create draft version.
2. Click Publish (freezes forever) on the draft. A published version can never be edited; ship another version to change anything.

Existing buyers see the new version in their project’s Marketplace tab only if they have an active Maintenance subscription (or if the update is a free patch within their licensed version range, as declared in your compatibility notes).

Deprecating a listing

The seller dashboard has no deprecate or unlist control today. Contact Chipp support to take a listing off sale. Removing a listing from sale never revokes existing licenses: buyers keep their perpetual rights and installed source.

Version branching and forks

If you need to maintain an older major version alongside a newer one (e.g. for buyers who cannot migrate), you can publish parallel listings at different version branches. Label them clearly in the display name and changelog.

Review and Security Requirements

Submission review

A draft listing has a Submit for review button, which moves it to the in_review status. Publishing a version is done by you, from the seller dashboard, and is not blocked on a Chipp review step for pack, recipe, or bundle listings. Full-project listings must pass automatic checks before they publish (source ownership, payout readiness, no committed credentials, no untransferable add-on licenses).

You are responsible for the security and correctness of what you publish.

Security disclosures

If a vulnerability is discovered in your published pack:

1. You will be notified by Chipp’s security team.
2. You are expected to issue a patched version within a reasonable timeframe (severity-dependent; critical issues may require a faster response).
3. Chipp may temporarily delist the affected version while the patch is in review.
4. Buyers with active Maintenance are notified of the security issue and the availability of the patched version.

Content and licensing compliance

You may only publish packs you have the right to distribute. Your listing must not include:

• Code from open-source projects whose licenses are incompatible with commercial redistribution (check your dependencies carefully).
• Hardcoded secrets, API keys, or customer data of any kind.
• Content that violates Chipp’s acceptable-use policy.

Worked Example: Supply-Chain Visibility Pack

The following is a representative example of how a seller might structure a domain-specific Feature Pack. All details are illustrative and contain no private customer data.

Pack: supply-chain-visibility

Imagine you have built an inventory-tracking and supplier-status dashboard used in your own projects. To turn it into a sellable pack:

Manifest excerpt:

{
  "packId": "supply-chain-visibility",
  "name": "Supply-Chain Visibility Dashboard",
  "version": "1.0.0",
  "description": "Real-time supplier status, inventory levels, and shipment tracking for e-commerce and manufacturing projects.",
  "dependencies": [
    { "packId": "commerce-catalog", "versionRange": ">=1.0.0 <2.0.0" },
    { "packId": "core-platform", "versionRange": ">=1.0.0" }
  ],
  "configSchema": [
    { "key": "defaultCurrency", "type": "string", "default": "USD", "label": "Default currency" },
    { "key": "lowStockThreshold", "type": "number", "default": 10, "label": "Low-stock alert threshold (units)" }
  ]
}

What the pack contributes:

• A /admin/supply-chain route with a real-time dashboard (WebSocket-fed inventory updates, supplier status tiles, shipment ETA table).
• A supply_chain_events Postgres table and a migration script to create it.
• A Deno API route at /api/supply-chain/events (stream endpoint).
• Agent guidance notes explaining the data model so the Alchemist agent can write queries and modifications correctly.

Pricing:

• One-time license: $149
• First-year Maintenance included, annual renewal: $49/year
• At 30% platform fee: you receive $104.30 on the first purchase and$34.30 on each annual renewal, paid by Stripe to your Stripe account.

What sellers must NOT include in the manifest or source files:

• Real supplier names, purchase orders, customer data, or any non-synthetic test fixtures.
• Hardcoded API keys or credentials.
• References to internal proprietary systems by their real names.

This supply-chain example is structural only — distinct supplier status entities, inventory tracking, shipment ETA — and exposes no private details from any real customer’s data.

Related guides

• Recipes, Feature Packs & the Marketplace — the vocabulary and mental model every seller should share with buyers.
• Marketplace: Browse, Purchase & Create a Project — the buyer-side experience your listing will appear in.
• Marketplace: Maintenance Subscriptions, Updates & Perpetual Rights — what buyers get from the Maintenance price you set.
• Marketplace FAQ — common seller and licensing questions answered concretely.