Runway Workflow as an endpoint vs a Sume Format over the API

Runway publishes a Workflow as an API endpoint from the Web App; Sume serves a saved Format at /v1/formats/{handle}/{slug}/runs. Setup and billing differ.

6 min readSume
All posts

Runway lets an admin or editor publish a Workflow as an API endpoint with one click from the Web App, then a developer runs it from the Developer Portal or copies code with Get Code. Sume's equivalent is a Format: a saved recipe you call with POST /v1/formats/{handle}/{slug}/runs using an API key. The big differences are that Runway links two accounts and bills the Developer balance, while Sume uses one key with scopes and returns a typed result you define.

Setup and billing

Published Workflow vs Format run (read 2026-10-04)
QuestionRunway Workflow endpointSume Format
Where you build itVisually in the Web App, as nodesSKILL.md and reference files, in the dashboard or Contents API
Who can publishAdmins and editorsThe owning workspace; scopes formats:write
Account setupDeveloper Portal and Web App accounts must be linkedOne API key with formats:read and formats:write
Inputs and outputsLabelled when publishing; an eye icon shows or hides eachinput is free-form JSON; output_schema binds the result
Credits usedDeveloper account creditsWorkspace wallet, capped per run in USD
EditsEach change deploys immediatelyversion bumps per edit; the receipt shows which ran

What comes back

A Format run returns a receipt with status_url, result_url, events_url and cancel_url. Statuses are queued, processing, then completed, failed, canceled or skipped. With an output_schema, output comes back in your shape and primary_output_url points at the headline file.

curl -sS -X POST "https://api.sume.com/v1/formats/acme/live-commerce/runs" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-8823-v1" \
  -d '{
    "instruction": "Vertical 9:16, no BGM.",
    "input": { "product_url": "https://shop.example.com/p/8823" },
    "output_schema": {
      "name": "acme/live-commerce/v1",
      "strict": true,
      "schema": {
        "type": "object",
        "additionalProperties": false,
        "required": ["full_video"],
        "properties": { "full_video": { "$ref": "SumeMediaFile#" } }
      }
    },
    "primary_output_key": "full_video",
    "generation_spend_cap_usd": 120
  }'

Edits do not touch a run in flight

Runway says each change to a published endpoint deploys immediately. On Sume, editing a Format's package never touches a run that is already in flight, because each run reads the package it started with. The version on the receipt is the proof of which recipe ran.

Pick by who builds

  • Visual nodes built by a creative team, called by a developer: Runway's published Workflow.
  • A recipe an agent follows, with a schema you own and webhooks or polling: a Sume Format.
  • Whichever you choose, read how credits or dollars are charged before the first call.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume