Exchange — Submitter guide — bRRAIn Docs

How to submit a skill, plan, standard, or installable bundle to the bRRAIn Exchange.

Exchange — Submitter guide

Submit a skill, plan, standard, or installable bundle to the bRRAIn Exchange so other users can buy it.

Eligibility

Submitters must pass either track:

  • Active subscription on any paid bRRAIn plan, OR
  • Certified in any bRRAIn discipline and completed Stripe Identity verification.

See the Exchange page for the full eligibility ladder.

Submission types

| Type | What it is | |------|------------| | Skill | A single reusable skill — a well-scoped capability with its own README, KPI, and success criteria. | | Plan | A multi-step playbook that orchestrates skills to reach a goal. | | Standard | A policy / compliance / governance document. | | Project | An entire, fully AI-run company in a box. Buyers can download and start a business with it immediately. |

Submit form fields

  • Title — short, descriptive
  • Slug — URL-safe, lowercase, hyphenated
  • Short description — one-line pitch for the card
  • Long description — full detail shown on the listing detail page
  • Category — maps to browse filters
  • Target use — who the listing is for
  • Version — semver (e.g. 1.0.0)
  • Tags — comma-separated keywords
  • Price (USD) — zero for free, otherwise a price in cents
  • File upload — zip archive; file inventory (counts + folder counts + distinct file types) is auto-computed. Filenames are never shown to buyers.

Review + approval

Every submission lands in state='review' and waits for admin sign-off before it appears in /browse. You can preview your own listing anytime at exchange.brrain.io/listing/{slug}.

Versioning

New versions go through the same review pipeline. On approval, you can pick whether existing owners get the new version free, at a discount, or at full price; you can also set a cut-off version so pre-cut-off buyers keep the old release.

Archiving + deleting

Sellers can archive their own listings (/listing/{slug}/archive); archived listings stay in the DB but disappear from /browse. Only admins can permanently delete a submission.

Where to next