Runway workspace workflows vs Sume Format grants for partners

Runway Agent can run a workflow that is shared with your workspace or a Project, but it will not edit a workflow someone else owns; you ask it to make a copy instead. Sume shares a Format with another workspace through a grant: the partner calls the owner's address with its own team key, and the run, spend and media belong to the partner. Access is to a workspace, never to a single user.

Access rules side by side

The Sume handshake

The owner adds your team handle on the Format's Access tab, which is live immediately, or invites it with POST /v1/formats/{handle}/{slug}/grants. Your admin accepts with POST /v1/format-grants/{grant_id}/accept using a key created in your workspace. There is no workspace field on the run request because the key is the actor.

curl -sS -X POST "https://api.sume.com/v1/formats/{owner-handle}/{slug}/runs" \
  -H "Authorization: Bearer $YOUR_TEAM_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: partner-order-5521-v1" \
  -d '{"instruction": "Vertical 9:16 teaser."}'

What can go wrong

A personal key on a team Format is 403 workspace_key_required. A pending or removed grant is 404 format_not_found, the same answer as a Format that does not exist. The owner also controls whether the Format takes API calls at all, and that setting applies to every caller.

Pick by relationship

• Colleagues in one workspace working in chat: Runway's workspace and Project sharing is the shorter path.
• A partner or agency that must call your recipe from its own backend and pay for its own runs: a Sume grant.