Skip to content
SBDocs

Get started

Sushibelt docs

Run Sushibelt workflows from your own code, or sell your model API through Sushibelt. Pick your path.

Sushibelt runs workflows that turn a brief into game assets — images, audio, 3D models, text. You wire a workflow on the canvas; each run is estimated before it starts, charged per step as each step finishes, and its outputs are stored in your team's library.

Pick your path#

I want to generate assets#

Run your team's workflows from your own code, pipeline or agent — no browser needed. You will use the API to find a workflow, start a run, and read its output.

  • Quickstart — from an API key to a downloaded output in five minutes.
  • Concepts — workflows, runs, credits, outputs and licences, in one page.
  • Agents — let your own AI agent drive Sushibelt, within a spending limit.
  • API overview — authentication, scopes, rate limits and errors.
  • Runs — start a run, pass it inputs, poll it or get a webhook when it finishes.
  • Workflows — list the workflows a key can run, or create one from a list of steps.

I sell a model API#

Sell your model API to Sushibelt's customers from a storefront: your team's shop, where you list models, set their prices and get paid.

Read the seller agreement before you list: it covers what you may list, how you price, and how payouts work.

Your first request#

  1. In the app, open Team settings → API keys and create a key. Copy it now — the full key is shown once.
  2. Put it in an environment variable: export SUSHIBELT_API_KEY=sk_live_…
  3. List the workflows the key can run:
List workflows
curl "https://app.sushibelt.ai/api/v1/workflows" \
  -H "Authorization: Bearer $SUSHIBELT_API_KEY"

The answer lists each workflow with its id. Pass an id to Run a workflow, then read the run with Get a run until it completes.

What these docs cover#

  • For customers: a quickstart, the concepts, guides from running a workflow to handling errors and licences, the workflow format, and using Sushibelt from an agent.
  • For providers: a quickstart, guides to pricing, payouts, claiming your provider and running your own endpoint, and the reference for what you declare.
  • For both: the API reference, generated from the same OpenAPI document the API is tested against; the policies; and a changelog.

Next steps