remove.bg type parameter (car, product, person) vs Sume RMBG

Sume RMBG 1.0 has no foreground-type hint. If you set type=car on remove.bg, there is nothing to set on Sume: you send an image_url and Sume selects the model itself.

remove.bg's changelog lists type=car (2019-05-13) and the X-Type response header with values car, animal and other. Sume's side is from the API reference, read 2026-10-01.

What does remove.bg's type do?

The changelog says car support was added with a type=car parameter and an X-Type: car response header. Later, support for animals and other foregrounds added X-Type: animal and X-Type: other. The page also says images need a foreground such as people, products, animals or cars.

What does the Sume request look like?

The schema reads "Provide a public HTTPS image_url. Provider model ids are selected by Sume and are not accepted in this schema." The one tuning field is sync_mode, described as an optional provider passthrough that falls back to the provider default when omitted. There is no field for subject type.

Will cars still come out cleanly?

Sume's docs make no per-subject promise, so test your own images. For vehicles, see car background removal AI, and keep a small set of hard cases (glass, reflections, thin parts) as your acceptance check.

What do I do with code that reads X-Type?

Remove the branch, or replace it with your own classification step before the call if you route by subject. The Sume result carries the PNG artifact and no subject label in the documented contract.