The Token
An economy
that runs on use.
The native token is not a side bet layered onto the platform. It is the circulatory system, and its model is deliberately unfashionable.
On this page
- Why an economy at all
- The four flows
- Usage instead of emissions
- Where the token is actually used
- What this is not
Why an economy at all
Reuse needs
a way to pay.
Usage in, rewards out. An economy with a center of gravity, and the center is real work.
Open source solved distribution and never solved compensation. A maintainer whose work runs inside a thousand products still has to find a job somewhere else, which is why so much shared infrastructure is held up by people doing it in the evenings. In robotics the gap is wider still, because the work is expensive to produce and easy to copy.
The token exists to close that gap inside the platform. Royalties, contributor rewards and challenge prizes need a unit that moves automatically at the moment of use, in amounts too small to invoice and too frequent to administer by hand. Settling in the platform's own token is what makes paying per reuse practical rather than aspirational.
The design constraint we set ourselves is the unglamorous one: weight that comes from real usage, not from inflationary emissions. A system that pays contributors by printing claims against a future it has not earned is a system that eventually stops paying anyone.
The four flows
Where value enters,
and where it lands.
Four movements make up the whole economy. Each one starts with somebody paying for something they wanted, the only durable source of funding there is.
Flow one
Manufacturers fund the challenges
Manufacturers put up the prizes for problems they need solved. Their challenges pull the whole field toward models that are both better and cheaper, and the progress they pay for is shared by everyone who builds here rather than locked to one buyer. Money enters the economy as a purchase of research, not as a subsidy.
Flow two
Revenue returns to makers
Marketplace revenue is shared with the creators and contributors whose work made it worth paying for. The people who built the value are the people who receive it, automatically, every time it is used. Reuse three layers deep in someone else's behavior still pays the author at the bottom of the chain.
Flow three
Fees become fuel
Fees paid in conventional currency are converted into the token, so ordinary payments feed the system from within instead of leaking back out of it. A customer who has no interest in tokens never has to hold one, and their payment still funds the makers underneath their deployment.
Flow four
Incentives come from real usage
Developer incentives are paid out of actual usage, not printed on a schedule. The token's gravity comes from work genuinely done, which is why it pulls value inward over time instead of diluting it away from the contributors it is supposed to reward.
Usage instead of emissions
The unfashionable model,
and why we chose it.
| The question | Emission driven | Usage driven |
|---|---|---|
| Where rewards come from | New supply, issued on a schedule set in advance. | Fees and marketplace revenue from work that someone chose to pay for. |
| What early activity optimizes for | Collecting emissions, whether or not the activity was wanted. | Being used, because that is the only thing that pays. |
| What happens when growth slows | Rewards keep printing, and dilution does the rest. | Rewards contract with usage, and the economy stays solvent. |
| Who is rewarded for maintenance | Nobody. Emissions reward presence, not upkeep. | The authors of assets still being used, for as long as they are used. |
| What a customer has to believe | That the token will appreciate enough to justify the cost. | That the platform is worth paying for, in the currency they already hold. |
Usage driven economies grow more slowly at the start. That is the trade we accepted. The alternative buys early numbers by borrowing from the contributors it exists to pay, and in robotics the contributors are the scarcest resource on the platform.
Where the token is used
Inside the platform,
at the moment of use.
The token has a job, and the job is settlement between the people who make robotics work and the people who use it. Everything below happens inside the platform, triggered by something a maker or a team actually did.
- Royalties on reuse. Paid to the authors of skills, behaviors, policies, models, templates, evaluation packs and datasets, metered where the use happens.
- Contributor rewards. Paid for work that improves the platform itself, and that is how the talent pool widens without a hiring budget.
- Challenge prizes. Funded by manufacturers, judged on shared evaluation packs, and paid out to the makers who solved the problem.
- Marketplace settlement. Purchases and usage fees settle in the token, including fees that arrived as conventional currency and were converted inward.
- Platform usage. Metered platform services are paid for in the same unit the rest of the economy settles in, so one ledger explains the whole system.
Said plainly
What this is not.
A utility inside a platform, nothing more
The token exists so that reuse can be paid for automatically. It is not an investment product, and nothing on this site is an offer, a solicitation, or financial advice. We make no claims about price, appreciation or yield, and we would be suspicious of anyone who did.
If you are here to build robots, you can use the Studio and the Hub without taking a position on anything. Fees can be paid in conventional currency, and conversion happens on the platform side.
Not a prerequisite
You do not need to hold the token to develop, deploy or operate a robot on the platform. Makers who earn royalties receive them in it, and that is the extent of the requirement.
Not a governance theatre
We would rather be judged on shipped software and public repositories than on a voting mechanism that decorates decisions already made. Where the community genuinely decides something, we will say exactly what was decided and by whom.
Questions we get
The economy,
asked directly.
Why does an open platform need a token at all?
Because the payments it has to make are small, frequent and automatic. Paying a royalty to the author of a skill each time it is trained against or deployed is not a billing problem you want to solve with invoices. A native unit makes per use settlement practical, and it lets contributor rewards, challenge prizes and marketplace revenue share live on one ledger.
Can my company pay in ordinary currency?
Yes. Fees paid conventionally are converted into the token on the platform side, so the economy is funded from within while your finance team deals only in the currency it already uses.
What stops reward farming?
Rewards are funded by usage, not by issuance, so manufacturing activity costs more than it pays. Metering is tied to real events in a project, and challenge prizes are judged on shared evaluation packs with stated conditions rather than on self reported results.
How do I know what I earned, and why?
Earnings are attributable to the usage that produced them: which asset, which version, which kind of use. The point of metering at the event instead of the download is that the explanation exists even when the money is small.
Does this mean the platform is a blockchain project?
No. It is a robotics platform with an economy attached. The engineering that matters here is simulation, training, deployment and a real-time runtime. The token is infrastructure for paying the people who build those things, and we are deliberately boring about it.
Earn from what you build
Ask us the awkward
questions first.
Royalty terms, conversion, enterprise billing, or how a challenge gets funded and judged. Tell us what you need to know and we will answer specifically.