Skip to content
SBDocs

Customers

Changelog

Every change to the API and these docs that affects your code, newest first.

Changes to the API and to these docs that affect your code. Newest first. Dates are in Copenhagen time.

11 October 2026 — A webhook for cancelled runs#

  • A run someone cancels in the app now sends its webhook, with the new event run.cancelled. It used to send nothing.

3 October 2026 — Connect your AI agent over MCP#

  • Sushibelt is an MCP server at /api/mcp. Connect Claude Code, Cursor or another MCP client with a team API key, and it can search your library and Discover, list models, price and start runs, and read what they made. See Connect your AI agent (MCP).
  • Every MCP tool call is logged and charged like the API, and the key's scopes, workflow list and monthly cap apply to it.
  • The app has a Connect an agent page under your team settings, with the snippets for your endpoint.

2 October 2026 — Claim DNS record on a subdomain#

  • Providers: a claim's DNS TXT record may now go on _sushibelt. on your domain (for www.example.com, _sushibelt.example.com) as well as on the website host itself, so your domain's own records can stay as they are. A failed check names what was found at each.
  • Providers: every provider Sushibelt runs now has the website its claim proves recorded.

30 September 2026 — llms.txt, waiting price rises, and the claim read#

  • An /llms.txt lists every endpoint and guide for agents, built from the OpenAPI document.
  • A price rise a provider has declared, still inside its seven days' notice, now shows with its date where you see the price: on Discover and on a node in the canvas.
  • Providers: GET /api/providers/{key}/claim now returns progress — domain proof, the staged declaration, the last probe — and, while the claim waits for its DNS record, domainToken again, to a member who may act on the claim.
  • Providers: declaring a claim now needs a team owner, since the price declared is the one customers pay after the handover. A price, unit or key error names its field.
  • Providers: a claim probe that stops because no key was declared is now recorded on the claim as a failed probe.

29 September 2026 — Developer docs, the OpenAPI document, and runs that end#

  • These docs are published at /docs, with an API reference for every endpoint.
  • Guides for customers — a quickstart, concepts, eight guides, the workflow format and agents — and for providers, from the provider quickstart to the reference for what you declare.
  • A run someone stops in the app now reads stopped, and its webhook is sent with the new event run.stopped. It used to keep reading processing.
  • A run whose Branch step sent nothing down a path now reads completed when it ends; the steps not taken are skipped.
  • Run results and webhooks no longer carry a step's internal configuration.
  • A deferred run (defer: true) now waits until the load multiplier is at or below your maxMultiplier.
  • Some providers are not available through the API yet, while their terms are confirmed. A run whose step can only use one is refused with 422, naming the provider in providers; the same workflow still runs from the app.
  • Each run output now says whether it was made by an AI model — ai_generated, and generated_by naming the models. Images and audio are also marked inside the file.
  • Fal image models run with the provider's safety filter on. A blocked image is dropped; if every image was blocked, the step fails and says why.
  • The API is described as OpenAPI 3.1 at /api/v1/openapi.json. No key is needed to fetch it.
  • A deferred run can be followed: Get a deferred run returns its status and, once it starts, the jobId it became. A callbackUrl sent with it is now kept, so its webhook arrives.
  • API keys can be given an expiry and limited to some workflows in the app, when created and later; an expired key is refused like a revoked one.
  • Providers: requestPath and submitPath are no longer part of a transport declaration — a run always went to its model's descriptor endpoint. A declaration that still carries them is accepted and the fields ignored.
  • Providers: the claim has screens in the app, under your storefront's APIs. A provider Sushibelt reaches through its own code rather than an endpoint (Fal, Replicate) can no longer be claimed.
  • The reference lists every status code each endpoint answers with, including 409 when a workflow already has a run in progress, and the 402 answers for a project's hard cap and your team's per-step credit limit.

Next steps