RL Environments
Environments built by the people who use them.
Reviewed once. Approved once. Available to every team that needs them. Connects to Evaluation Studio, Training, and Domain Labs.
Unapproved community environments are stopped before they reach deployment.
The default revenue split starts from a clear, deterministic policy.
Smaller settlements accrue until they are ready to be paid out.
Community uploads enter review before they appear in the marketplace.
Community environments cannot be deployed until they are approved.
Creators can see review status, deployments, and payout readiness in one overview.
Uploading a community environment creates a pending review record before it can be commercialized. The browse flow only shows approved community items.
Deploying a community environment before approval returns a conflict instead of quietly queueing work. That keeps creator monetization aligned with review outcomes.
Paid community deploys can create settlement audit events and payout rows. The creator overview reports realized revenue plus payable, accruing, and processed payout states.
- The public marketing page does not pretend the marketplace is anonymous or public; the shipped routes are authenticated and org-scoped.
- Approval is not optional for community environments. Browse and deploy flows filter or block until approval exists.
- Leaderboard entries do not appear automatically from page views. They only show up after explicit submissions to the leaderboard endpoint.
- Marketplace commercialization code records settlement and payout state, but it does not promise instant cash-out from this page alone.
Buyer paths
Two sides. One controlled marketplace.
Creators need a clean path to publish and earn. Operators need review gates and proof. AuraOne keeps both in one workflow.
Need a clear way to submit environments, understand review status, and see when revenue is ready to pay out.
Need review gates, deployment controls, and proof before exposing anything to an organization.
Review the proof
How the marketplace runs.
Submit, review, deploy, measure, and report payouts in one flow.
Submit a new environment
POST /api/v1/marketplace/environments/uploadThe upload route validates JSON, runs static security checks, creates a community marketplace environment, and opens a pending coordination marketplace submission for review.
Review it once
GET /api/v1/coordination/marketplace/submissions + PATCH /api/v1/coordination/marketplace/submissions/[submissionId]Admins can filter submissions, add review notes, and approve or reject. Approval publishes or updates the marketplace item record and version metadata.
Show only approved items
GET /api/v1/marketplace/environmentsCatalog environments are always available, but community environments only appear in the marketplace list after approval. Pending uploads stay out of the browse flow.
Deploy after approval
POST /api/v1/marketplace/environments/deployDeploy requests require an Idempotency-Key, resolve the environment, auto-provision the RL Environments Harness template when needed, and queue an evaluation run for the authenticated org.
Measure results
GET/POST /api/v1/marketplace/environments/[environmentKey]/leaderboardLeaderboard data is empty until entries are submitted. Community environments must already be approved before leaderboard reads or writes succeed.
Track revenue and payout status
GET /api/v1/marketplace/environments/creatorEach paid deployment of an approved community environment increments downloads, records a creator settlement, and surfaces realized, payable, accruing, and processed payout totals in the creator overview.
Creator view
- Pending, approved, and rejected submission states come from coordination marketplace submissions tied to the creator and org.
- Per-environment rows include review notes, deployment count, realized creator revenue, gross revenue, and latest payout state.
- Recent payouts are organization-scoped, while creator profile earnings remain visible as a global lifetime total for the same creator record.
Admin view
- Admins can list submissions by status, vendor, category, or search term before taking action.
- Approving a submission updates submission status, stamps review time, and publishes a marketplace item plus item version metadata.
- Rejecting or resetting a submission keeps it out of the approved marketplace list and preserves review notes for follow-up.
Deployment view
- Deploys create an evaluation plus an evaluation run with marketplace metadata attached to the org.
- Community environments are blocked from deploy until approval exists; catalog items skip that community-specific gate.
- Deployment actions emit audit events and can produce creator settlement records when the community environment is monetized.
Creator economics
Creator economics stay explicit.
The marketplace uses a defined revenue-sharing policy for approved community environments. Settlements are recorded when monetized deploys succeed, and the creator overview rolls them into simple payout totals.
Base creator share from the revenue-sharing policy module.
Verified environments receive a higher creator share.
Another increase applies after 10,000 monthly downloads, capped at an 85% creator share.
Creator settlements below the threshold accrue until they are large enough to move into a payable state.
Accruing until the minimum payout is met
When creator payout on a settlement is below the minimum, the marketplace code records the amount as accruing rather than payable.
Payable
When a settlement clears the minimum threshold, the platform creates a payout row with pending status and the creator overview reports it as payable.
Processed
Processed, paid, completed, and succeeded payout statuses are rolled up as processed revenue in the creator dashboard summary.
Workflow checks
Five checks that prove it is real.
These checks line up with the current authenticated routes in the platform app. They are the fastest way to prove the loop locally.
Request
POST /api/v1/marketplace/environments/uploadExpect
Expect accepted=true, a community-* environment key, submission.status=pending, and a reviewPath pointing at the admin review route.
Request
PATCH /api/v1/coordination/marketplace/submissions/[submissionId]Expect
Set status=approved to receive a publishedMarketplaceItemId and reviewedAt timestamp; rejected items keep notes without entering the marketplace catalog.
Request
GET /api/v1/marketplace/environmentsExpect
Approved community environments appear beside the catalog. Pending submissions stay absent from the listing.
Request
POST /api/v1/marketplace/environments/deployExpect
Deploying a pending community environment returns environment_not_approved. Deploying an approved environment returns 202 with deploymentId, evaluationId, queue metadata, and possibly creatorSettlement.
Request
GET /api/v1/marketplace/environments/creatorExpect
Expect summary totals for payable, accruing, and processed payouts plus per-environment commercialization metrics for the authenticated creator.