Publishing turns a private workflow into a versioned listing on Discover (/platform/discover). Anyone entitled can Try it; Remix makes an editable copy.
What publishing does
- Freezes a version. Runners get the version you published. Keep editing your draft; publish again to ship an update.
- Requires a verified run. A succeeded run on that version stamps
verified_run_id. Unverified stays private / Runnable · unverified. Verified badge is never claimed without a receipt. - Sets how others use it:
- Try — run the recipe in their session (bind only).
- Remix — private child with lineage. Public remix trees count public+published children only.
- Flow — they pin inputs for org re-runs (
POST /runsagainst the version).
- Moderation. Public listings pass content review. NSFW stays entitlement-gated.
Earnings
Paid marketplace (credits debit → run access + accrued payout) is implemented and stays off in production until Stripe content-platform pre-approval. Open Try/Remix does not charge a creator premium today.
When paid listings are enabled: royalties accrue on other people’s successful runs, never your own; failed/cancelled runs do not pay.
Every output from a published workflow can carry a Made with credit and a Remix control.
Good listings
- Name the outcome, not the wiring — “UGC product ad from a URL” beats “scrape + script + map”.
- Promote few inputs. Every input is a decision you are delegating.
- Set a real cover. Discover thumbs come from a verified preview (or the style thumbnail), not a placeholder.