Before you list. The seller FAQ.

The seller deal makes the argument in six clauses. This page answers the questions sellers actually type before listing — including the uncomfortable ones — and where an answer has a contractual home, it links the clause it comes from. Nothing here softens what the deal page says. Where you find a hedge, it is because the honest answer has one. One more thing worth saying up front: the catalog today is fifteen skills built and run by Sealed itself, while the first outside sellers are recruited. These answers describe the terms you would be early to, not a settled market.

Can buyers copy my skill?

They never receive it. Your skill runs on Sealed's infrastructure: the buyer's agent sends inputs, the skill executes server-side, and only the output comes back. No endpoint, log, or error message returns skill source, the body sits encrypted at rest, and every output is leak-scanned before it leaves — the machinery behind clause S3 of the seller deal. The honest boundary: sealing stops your file from being copied. It cannot stop a buyer studying twenty outputs and approximating your method. If your skill's whole value is the text it hands back, the output is the IP, and no marketplace can protect that. Skills whose value is the doing — a process, a judgement, data the buyer can't reach — hold up. What you can and can't protect walks through the distinction.

What cut do I keep?

80% of every successfully settled call. The 20% platform fee is published, applied uniformly — not negotiated per seller, not tiered opaquely — and any change is prospective only, with advance notice to active sellers, per clause S1 of the seller deal. The split is also exact: the ledger splits on an integer micro-dollar grid, so 80% is exact at every price, never rounded against you. A $0.10 call pays you $0.08; a $0.14 call pays $0.112, to the micro-dollar. Price floors are model-aware — $0.10 on Haiku, $0.14 on Sonnet, $0.19 on Opus, per call — and you can price above the floor, never below, so a call can never run at a loss. Buyers cover the payment-processing fee when they top up, so it never comes out of your share.

When and how do I get paid?

Earnings accrue to your Sealed balance from the first settled call. Eligible cash-outs run through a Stripe-hosted Connect account in your name; Stripe does the identity checks and moves funds. Payout timing, fees, and availability are Stripe's plus any published Sealed limits — not undisclosed platform discretion — and Sealed can apply payout holds only for security, fraud, legal, payment-network, or dispute obligations. That is clause S2 of the seller deal, in full. What you will not find on this page is a promised cadence: we are early, and we would rather show you the path — balance, Stripe Connect, your bank — and the short list of reasons a hold can exist than advertise a schedule the operation has not earned yet.

Does my skill ever leave Sealed's infrastructure?

Once, in one direction, and never to the buyer. To run at all, your skill is sent to our model provider (Anthropic) as that run's system prompt — the one place outside Sealed it goes. The seal is buyer-scoped, not sole custody: "sealed" means the body never reaches the buyer, not that no third party ever processes it. That disclosure is printed in clause S3 of the seller deal, detailed on the privacy page, and will not be quietly narrowed. If your threat model cannot tolerate the model provider seeing the skill at run time, do not list it — that is the honest advice.

Will my skill train a model?

Sealed never uses your skill to train a model, never resells it, and never repackages it — clause S3 of the seller deal. Our license is a narrow operational one: host and execute your skill to fulfill paid calls, nothing more. The one processing step outside Sealed is the model-provider run described above; how that traffic is handled is documented on the privacy page rather than glossed here.

Can I get my work back?

Any time. You can export your complete uploaded skill content whenever you want, there is no exclusivity, and nothing stops you selling the same thing elsewhere. If Sealed ever winds down or exits the business, clause S4 of the seller deal defines the exit: advance notice where reasonably possible, a full export of your skills made available, and eligible earned balances paid out through Stripe Connect subject to fraud, legal, tax, payment-network, and dispute requirements. No surviving license, no hostage-taking, no quiet deletion.

What's the difference between Hosted and Connected?

Hosted: the buyer sends inputs, your skill runs on our cloud, and the output comes back. You can publish a Hosted skill yourself today from the publisher console — magic-link sign-in, no password. Connected: the skill works on files in the buyer's own project, under a scope the buyer approves — often the more defensible shape, since the value is the doing rather than a block of text a buyer could keep. A Connected listing needs a seller-authored scope contract that will run commands on a stranger's machine, so every one is hand-reviewed — email support@sealed.run to put one up. In both shapes the skill body never reaches the buyer's machine.

What am I liable for?

Your own skill and content — that part is fair, and it is yours to stand behind. You are not on the hook for failures of Sealed's infrastructure, our security, or our business. There is no blanket "indemnify the platform for everything" clause as the price of listing, and liability is balanced in posture — we do not cap our side at a token figure while leaving you fully exposed. That is clause S6 of the seller deal.

Are these the final legal terms?

Not yet, and pretending otherwise would undercut everything above. The marketplace is live, but S1–S6 are still the terms skeleton — the commitments the contract is being built around, not the final legal text reviewed by counsel. The finalized terms, reviewed by counsel, ship at launch; where the two could differ, the seller deal is the intended direction and this FAQ follows it. If that changes, you will hear it from us first.