Runway Agent Brand Kits from a PDF vs Sume Format package files

Runway's Brand Kits with Agent is an Enterprise feature: Agent applies a kit to its work and can build one from PDF text, and the page says there is no website URL import. Sume has no Brand Kit object; the equivalent is a Format whose package files hold the rules, which you edit by the Contents API. That is a different shape, and it is the only brand-persistence route in Sume's docs.

Where the brand lives

Editing the package safely

Read the package first, then write with If-Match set to the revision you read. If someone else changed it, the write is refused instead of overwriting, so you never clobber a teammate's edit. A multi-file change is one commit.

Keep the run body small

Hold the stable rules in the package and send only the per-run variables as input: product, offer, audience. Anything in input is data rather than instructions, so do not put brand rules there.

{
  "instruction": "Make a 20-second ad for the product below.",
  "input": {"product": "Trail mug", "offer": "Free shipping"},
  "generation_spend_cap_usd": 15
}

Checklist before you rely on it

• Write colors, tone and banned phrases as plain files in the package.
• Run once with a low cap and read the receipt before a batch.
• Change a rule in one place and every later run follows it.