Marketplace

Publishing

Register as a developer, then submit through createSubmission() — a DRAFT you can edit freely until you call submitForReview(). Validation rules (moduleKey format, description length, capability/permission/trigger-format checks, reserved prefixes) run automatically before a submission can enter the queue. Full manifest field reference is on the SDK page.

Review process

A submission enters the queue as PENDING. The review checks:

• Auto-validation — key format, capabilities, permissions, trigger/action format, screenshots, documentation URL
• Manual review — description quality, security scan results, no duplicate keys

DRAFT → submitForReview() → PENDING → (admin) APPROVED / NEEDS_CHANGES / REJECTED
                                              ↓
                                     ModuleDefinition auto-created
                                              ↓
                                     PUBLISHED in marketplace
                                              ↓
                                   [admin] SUSPENDED → UNLISTED

NEEDS_CHANGES returns reviewer notes for you to revise and resubmit; REJECTED is permanent, with an explanation. A PENDING submission can be withdrawn back to DRAFT to keep editing before review completes.

Versioning

Every manifest declares a semantic version (MAJOR.MINOR.PATCH). Each approval records a ModuleVersion row with releaseNotes — this is what powers the Changelog section on a module's marketplace detail page. Publishing a new version doesn't require a new submission — it flows through the same approval step.

Asset types

The catalog spans 13 module categories: Community · Marketing · E-Commerce · Customer Support · AI · CRM · Booking · Membership · Education · Analytics · Engagement · Finance · Utility. Beyond modules, the submission form's asset-type selector also publishes AGENT, PROMPT, KNOWLEDGE_PACK, TOOL, CONNECTOR and INDUSTRY_TEMPLATE — see AI Marketplace for the full breakdown. Every asset type publishes through the identical ModuleDefinition upsert, review queue and versioning.

Revenue share

A 70/30 split applies to all paid modules and AI assets (MONTHLY, ONE_TIME and REVENUE_SHARE pricing types): 70% to the developer, 30% to BotForge as platform commission. Earnings are tracked per-sale in ModulePurchase and shown in your Developer Portal's Revenue tab.

model ModulePurchase {
  developerId     String?
  grossCents      Int
  commissionCents Int          // 30% to BotForge
  netCents        Int          // 70% to developer
  payoutStatus    PayoutStatus // PENDING → APPROVED → PAID
}

Payout processing (Stripe Connect / bank transfer) is currently tracked and manually processed — full automation is a future phase.