Publish what you make. Earn from results.
Put your benchmarks and environments in the hub under your own name, and take on bounties: rewards people post for a score, a new environment or a fix.
Your work, credited and used.
Your name on it
Every listing carries its author and organization, wherever it is used.
Measured, so it counts
Published environments pass the same audit as everything else in the hub.
Rewards for results
Bounties put a stated reward on the work people want done.
Someone wants it done. You do it.
Anyone with an account, or an organization, can post a bounty on the hub with a reward in US dollars and an optional deadline.
- ScoreBeat a target score on an environment. You submit a finished run; it must reach the target to be accepted.
- BuildPublish the environment someone asked for, and submit the listing.
- FixFix a reported advisory, such as a reward hack, and submit a link to the fix.
Three kinds of bountyreward in US dollars
From posted to awarded.
Posted
A reward, a target and a deadline, on an environment in the hub.
Submitted
You submit a run, a published environment or a fix.
Checked
A score submission is measured by the environment's own verifier and must reach the target.
Awarded
The poster accepts the winning submission and settles the reward with you.
The scorer decides whether a score counts.
A score bounty can't be awarded to a run that misses its target. The number comes from the environment's own verifier on a runner, not from a screenshot or a claim.
- Runs, not claimsA score submission is a finished run on Nenyax, with its model and its score.
- One run, one submissionThe same run can't be submitted twice to the same bounty.
- You can't claim your ownPosters and their organizations can't submit to their own bounties.
Score bountyreward stated by the poster
Honest about what you can earn from.
Nenyax doesn't handle payments. Bounty rewards are stated by the poster and settled between you.
| Today | |
|---|---|
| Bountiesscore, build and fix, with a USD reward | |
| Attributionyour name and organization on every listing | |
| Leaderboards on your environmentshow each model does on what you made | |
| Private listingsfor you or your organization | |
| Paid listingscharging for access to an environment |
Private until you say so.
Everything you push starts private. When it's audited and ready, make it public in the hub under your name or your organization's.
- Make it from your traces or codeYour coding agent builds it; ArkenOS, Claude Code, Codex or Cursor.
- Audited before it countsIt loads, completes an episode, reproduces, and its verifier tells good answers from bad.
- Then publicOthers can evaluate and train on it, and its leaderboard fills up.
Your listingmaya / support-inbox
Audit, push, publish.
Push always runs the audit first. Essential checks can't be skipped. New listings are private.
Good to know.
Publish your first environment.
Make it from your traces or your codebase, then share it.