(M) “Marketplace”Requests · Bounties · DatasetsPlanned

Back a request.Buy a dataset.

Teams that need robot data will fund it up front or license what’s already been played. Pilots are paid for every accepted episode, and every sale is shared with the people who built the world and played it.

Requests →DatasetsRevenue share
The request board, listing funded tasks with their reward per accepted episode.The request board, listing funded tasks with their reward per accepted episode.
A dataset listing for Lift with a Panda, with a replay preview, license and format options and a price.A dataset listing for Lift with a Panda, with a replay preview, license and format options and a price.
A funded request: $1,488 paid to pilots from a $2,500 budget, 372 of 625 episodes accepted and $4.00 per accepted episode.A funded request: $1,488 paid to pilots from a $2,500 budget, 372 of 625 episodes accepted and $4.00 per accepted episode.
01 “Board”02 “Request”03 “Dataset”
None of this is available yet, and nobody is paid today. In the first release, developers invite their own pilots. Amounts, fees and eligibility will be published before the marketplace opens. Screens show examples.

Supply meets demand.

Creators build worlds, robots and tasks, and pilots play them. Funders and buyers pay for the episodes that come out. Ballot sits in the middle: it hosts every session, checks every episode and runs the store.

Fund the data you need.

Like backing a project, a request puts money behind something that doesn’t exist yet. You pick a task, set a reward for each accepted episode and pay the budget up front. Pilots find it on the request board, and you watch the count climb.

Team requests

For a co-op scenario, a request pays per accepted team run and says how the reward is split across seats. Teams form on the request page, and every pilot sees their share before the mission starts.

Rules, reviews and refunds, in detail.Requests and bounties →

Buy what’s been played.

Episodes don’t stop being useful when a request closes. Datasets let other teams license them: replay any episode first, choose which to include, then pick a license and a format.

What a dataset contains, and what you can choose when you buy.Buying data →

Every sale is shared.

A bounty pays pilots once. When their episodes sell again as part of a dataset, the sale is split between the creators, the pilots and Ballot, and everyone sees where each payment came from.

Payments will run through Stripe, with a connected payout account for each pilot and creator.Revenue share →

Built on four rules.

CreditCredit travels with the data

Every episode records the simulation, robot and task it came from. Pilot attribution is added for paid work.

AcceptancePay for accepted episodes

Bounties pay for episodes that meet the request’s published rules, not for time spent in a headset.

TermsTerms come first

Pilots see the reward and the rules before they join. Funders see fees before they pay.

ChoiceNo agency in the middle

Funders describe what they need, and pilots choose what to play.

Need data?

Tell us what you’d fund first. Design partners help shape the marketplace.

Join the waitlist →Requests