Draft — this document has not been reviewed by Sushibelt's operator and should not be treated as final legal terms.

Seller agreement

For teams that sell on Sushibelt — models, workflows or their own provider API. It adds to the Terms of Service; where the two differ on selling, this agreement applies.

1. Who this is for

A team sells on Sushibelt through a storefront. Sushibelt approves each storefront before it opens and may decline or close one. Everything a storefront lists is sold under its name ("Sold by …"). What Sushibelt resells itself is sold by Sushibelt.

2. What you list

You may list only what you have the right to sell: models you run or are licensed to resell, workflows you made, and outputs you own. Each listing states the licence its outputs carry. A listing is reviewed before it goes live, and Sushibelt may remove a listing, or an item on Discover, that breaks this agreement, the law or a third party's rights — including after a report from anyone.

3. Your price

You set the price of what you sell. A price increase takes effect no sooner than seven days after you declare it, so a customer is never charged a new price without notice; a decrease takes effect at once. A run is charged the price in effect when it was dispatched.

Customers pay your price plus Sushibelt's markup, which is shown in your storefront's pricing view. You earn your price — the true cost of the run — and Sushibelt keeps the markup.

4. Payouts

Your earnings accrue in credits (1 credit = US$0.01) in your storefront's balance. You may request a payout once the balance reaches 1,000 credits (US$10.00), in whole credits. Payouts are made in US dollars by transfer to your Stripe Connect account, after Sushibelt approves the request; you must complete Stripe's onboarding to be paid. If Stripe reverses a transfer, the reversed amount returns to your balance.

Earnings on a run that is refunded to the customer because it failed are not earned. Sushibelt may hold a payout while it investigates fraud, abuse or a dispute.

5. Running your own provider API

A provider may claim the listing Sushibelt already runs for its API. A claim requires proving control of the provider's domain, Sushibelt's approval and a passing test of your endpoint. After the handover, runs go to your API on your key, and you are paid for them.

For a trial period after the handover, your API must succeed on at least 95% of runs; if it falls below that, or a check of your endpoint fails, the listing returns to Sushibelt automatically. After the trial, Sushibelt may still return the listing to itself if your API stops serving, you stop trading, or you break this agreement. You keep your API key current and may replace it at any time; a new key is tested before it is used.

You are paid on what Sushibelt meters for each run: one unit per run or per step, or — for the providers Sushibelt prices itself — the usage it measures, bounded by what the run asked for. Reporting usage that did not happen is a breach of this agreement.

6. Customers' data

Runs of your listing send customers' prompts and inputs to you. You use them only to serve that run, keep them no longer than the run needs, and do not train on them without the customer's consent. A customer's own provider key, when used, is theirs: you may use it only to serve that run.

7. Ending

You may close your storefront. Its listings go off sale; earnings already made are still paid out. Sushibelt may close a storefront that breaks this agreement, after telling you why.

8. Changes

Sushibelt may change this agreement. Material changes are announced to sellers before they take effect; continuing to sell after that is acceptance.