Deploy and get paid

1. Build in the public lab

Open the Prompt Lab, choose a geometry model or a web app, describe what you want, and build. Everything made there is public the moment it is made: the prompts, the model and its source are in the archive for anyone to read and reuse. Builds draw on a shared pot of rivets that Genworks keeps filled; nothing is sold in the public lab.

2. Keep an author key

Under the rivets meter, press Keep my work under an author key. The key is kept in your browser and sent with every build, so your sessions add up to one public record. The lab shows a link that carries the key to another browser; keep that link to yourself, since the key is how your work is recognized.

3. Earn a private lab

Each day a reviewer reads the new public work under each author key and recommends who climbs: real models or apps that do something useful, improved over more than one session, with nothing in them that reaches for the lab's machinery or other people's sessions. Promotion is confirmed by a person. Trusted authors receive a maker grant of rivets and a private lab at lab.gen.works: open it with your author key, and your sessions there run in a machine of their own, with nothing public.

4. Say what is paid for

A deployment needs something to sell. In the prompt, say which function of the app charges, and how much: a pass that unlocks a result, a file that costs something, a balance a user can top up and draw on. The agent writes the tollbooth into the page. For a model, the downloads can carry a price. Prices are in your currency; the page of a deployed app shows money, never the lab's units. Until that story exists the Monetize tile stays grayed out.

5. Set up payouts, then deploy

1. In the Monetize tile, type the email address your payouts should go to and press Set up payouts with Stripe. Stripe's own onboarding opens; it verifies the mailbox and asks what a payout needs. Back in the lab the tile says payouts are set up.
2. Give the deployment a name and a title, choose open or closed source, and press Deploy. A closed-source deployment is decided before the first prompt of its session, and reverts to open if the session ends without one.
3. Your app answers at https://<name>.gen.works/, on a machine of its own. Deploying again under the same name replaces it; Undeploy takes it down.

Users pay by card on Stripe's page, with your name on the statement. A pass is granted the moment Stripe reports the payment; nothing is granted on a user's word.

6. What you keep

• The card cost comes off the top of each payment. Of what is left, the monetization fee is 10% for an open-source deployment and 15% for a closed one on the Gendl engine; 15% and 20% on the solids engine. The rest is yours.
• Your share is transferred to your Stripe account as each payment settles and paid out by Stripe on its schedule. The lab's Earnings view shows every payment, refund and dispute by quarter.
• A refund or a chargeback reverses the payment's share; a dispute's processor fee is carried by Genworks, not by you.
• Hosting is metered: each deployment has a monthly allowance of compute, and past it the page pauses and offers a pack of hosting credits that anyone may buy for it. A deployment paused for thirty days has its machine retired; its record stays, and hosting bought for it brings it back.

7. Reach us

A problem with the lab, a deployment or a payment: [email protected]. A fault in the lab's code: its issue tracker. Every deployed page carries a Report a problem link at its foot that reaches the same mailbox.