Ideogram enable_copyright_detection: no such flag on Sume, what to do

Ideogram's Precise Edit reference (read 2026-10-06) lists enable_copyright_detection as an optional request parameter that is a copyright-detection toggle, beside quality, seed, num_images, async, webhook_url and dry_run. Sume's Image API request table has no field with that name or purpose.

Do not send it. Sume's own rule is that the catalog is the parameter allowlist, and a parameter the selected model does not list is rejected with 400 unsupported_parameter rather than dropped. That is better than silent loss, because your port fails on the first test call.

What a port should do

A review gate that fits a Sume job

• Store the prompt, the source URL and the job id with the output, so a reviewer can see what produced it.
• Hold anything that contains a logo, a character or a recognizable product look for a person to approve before it ships.
• Keep rejected outputs. They are your evidence if a brand team asks what was generated and why it was not used.
• If a job fails with generation_rejected, correct the input; the docs say failed generations are not charged.

Why a rejection beats a silent drop

A port that quietly ignores a safety flag looks like it works and then ships unchecked images. A hard 400 on the first call tells you the control is gone and sends you to build it on purpose.

Write that decision down in the ticket for the migration. Name who reviews outputs, what they look for, and where the approval is stored.

Keep the check proportionate. A product photo with a neutral background needs a quick look. An image that carries a brand mark, a face or a character needs a named approver, and the approval should be saved with the job id so you can find it again later.