Skip to content
SBDocs

Providers · Guides

Price a listing

Pricing units, declaring a price, the notice a rise needs, and what customers pay.

Before you start
  • A provider your team operates, after a claim is handed over.
  • The team owner role.
You'll end with
A price on each of your listings, and a clear date for when each change reaches customers.

Every listing has a price in credits per unit. A credit is $0.01. This guide covers the units, how to declare a price, and when a new price reaches customers.

Who can set a price#

You declare prices for the providers your team operates — one you have claimed and been handed over. Until then Sushibelt prices the listing, and the Pricing page says None of your providers has a listing yet, so there is nothing to price. Only a team owner can change a price.

Pricing units#

Each listing is priced in one unit. The unit is fixed per listing: a price change keeps it. To move a listing to another unit, contact Sushibelt — it is a separate change, not a new price.

Pricing units
UnitDescription
runOne call to your API.
tokenOne token of text in or out, for language models.
characterOne character of input text, for speech.
secondOne second of generated audio or video.
megapixelOne million pixels of generated image.
stepOne step of a customer's run — one node that ran.
usd_microOne millionth of a US dollar of the provider's own cost — a pass-through of what each run really cost.

Warning: price per run or per step on your own endpoint

When runs go to an endpoint you run, Sushibelt counts one unit per call: it does not read a token, character or second count from your response. So a provider you operate is priced per run or per step. The one exception is a provider Sushibelt already prices from its own published rates; its listings stay in usd_micro. Sushibelt checks this before a handover, and will not hand over a provider whose unit it cannot count.

Declare a price#

  • Open your storefront and select Pricing.
  • Under Your prices, each listing shows its Current price. Enter the new price in credits per unit. It must be more than 0, with at most 6 decimal places.
  • Before you commit, the form tells you when the price takes effect: Takes effect immediately, or a date 7 days out for a rise.
  • Confirm. The answer is Price updated for an immediate change, or Rise scheduled for and the date.

Rises and cuts#

  • A rise takes effect 7 days after you declare it. Until then customers pay the current price, and the Pricing table shows the waiting rise (for example rises to 9 cr / run on 2026-10-07). Customers see it too, with its date, where they see your price: on Discover and on a node in the canvas.
  • A cut, or the same price again, takes effect at once.
  • The first price you declare on a listing is compared with the price customers pay today — Sushibelt's rate. If yours is higher, it is a rise and waits out the notice. A listing that is free today counts as priced at 0.
  • You can change a listing's price once in any 7 days, up or down. The price you declared with your claim counts as your first change.

Which price a run pays#

A step is charged the price in effect when it was sent to your API. A price that changes while the step runs does not change what that step costs.

What customers pay#

  • Your price plus Sushibelt's markup. The Pricing table shows, per listing, what a step costs now and Sushibelt's cut. You earn your price; Sushibelt keeps the markup.
  • A per-run minimum, on some listings. Where one applies to Sushibelt's rate, the table notes it, for example at least 2 cr per run.
  • Their own key. A customer who brings their own key for your provider pays you directly, through your own billing; Sushibelt then charges them only a small fee for running the step, and you earn nothing on it from Sushibelt.

Customers are charged per step, as each step finishes. A step that fails is not charged, and earns you nothing.

If a price is refused#

  • creditsPerUnit must be a number greater than 0 — enter a positive number.
  • creditsPerUnit must have at most 6 decimal places — round it.
  • … already changed price within the last 7 days — wait until 7 days have passed since the last change.
  • Integration not found — your team does not operate the provider of that listing.
  • This integration's price history is in … — the listing's unit changed under it; contact Sushibelt before declaring a new price.

Next steps