Higgsfield's six launches in three days: what to re-test

Re-test one thing per Higgsfield launch, not all six: a text-in-image prompt, a batch of ad stills, a restyle clip, and the agent hand-off. The Higgsfield changelog (read 2026-10-02) lists six entries between 2026-09-29 and 2026-10-01, and each maps to a check you can run against whatever tool you already use.

This post does not rank anything. It lists what the changelog says, then points to the Sume page that tells you whether the same job is possible there.

What did Higgsfield list, and what should I check?

The table keeps each claim to the changelog wording. The last column is a check, not a verdict.

How do I check a model id on Sume?

Do not guess ids. The Image API docs say each model publishes typed capability descriptors, and a request that sets a parameter the model does not list returns 400 unsupported_parameter. So list the catalog first, then read the endpoint record for the model you care about. If the id is not there, Sume does not serve it today.

Can Sume batch 20 ad stills like Ads Studio?

Two documented routes exist. The Image API takes n from 1 to 10 per call, with lower per-model ceilings, so 20 stills is at least two calls. Bulk runs queue up to 100 Format runs with a concurrency window. Neither one reads a website link and builds a brand setup for you; you pass the prompt and product image yourself.

What about the restyle and agent entries?

The video docs describe higgsfield-genjutsu as Motion Transfer: one source video plus 1 to 8 reference images, 480p or 720p, 4 to 30 seconds, listed only when its provider is configured. There is no list of named styles. For agent hosts, the MCP quickstart shows how to add the hosted server.

Run each check once, save the job ids and costs, and repeat in a month. A changelog line is a claim until your own call confirms it.