The outcome

Create a reliable visual-editing service whose requests can be reproduced, investigated, and safely withheld from publication.

Step by step

A workflow you can repeat.

  1. 01

    Define allowed users, endpoints, regions, inputs, output sizes, moderation, retention, cost, latency, failure handling, disclosure, and prohibited identity or evidence use.

  2. 02

    Store the API token server-side, bind jobs to authenticated owners, validate URLs or Base64 payloads, minimize metadata, and record explicit rights and privacy approval.

  3. 03

    Generate or validate a structured instruction, constrain masks to the intended region, submit asynchronously with an idempotency record, and store the request ID and status URL.

  4. 04

    Poll with exponential backoff or verify signed webhooks, handle 429, timeout, duplicate, error, and deletion states, then quarantine output for automated and human comparison.

  5. 05

    Test unchanged-region fidelity, prompt and visual moderation, cost exhaustion, credential rotation, audit export, provider outage, rollback, and a human-controlled release gate.

Working standard

What good use looks like.

  • Keep tokens server-side.
  • Retain request IDs and instructions.
  • Never auto-publish edited output.

Official references

Check the current product documentation.