What changed

image-inpaint now has a public update note, not just a registry row.

The endpoint is the mask-based edit lane in Synthforge. Send an original image, a mask image, and a prompt. White pixels in the mask are the area to replace; black pixels stay fixed. The response returns a permanent hosted PNG URL plus the model and provider fields.

That sounds small, but it matters for agents. Text-to-image and image editing are different jobs. If a buyer already has the base image and only wants one region changed, routing to image-generate wastes context and usually changes too much. image-inpaint keeps the edit bounded.

Request shape

The request needs three fields: 

{
  "image_url": "https://example.com/product-photo.png",
  "mask_url": "https://example.com/product-photo-mask.png",
  "prompt": "Replace the damaged label with a clean blank white label"
}

model is optional. The catalog default is gpt-image-2; callers can override it when they need a specific upstream model.

The response includes: 

{
  "image_url": "https://v3.fal.media/files/abc/xyz/inpainted.png",
  "model": "gpt-image-2",
  "provider": "fal"
}

When to call it

Use image-inpaint when the desired change is local: remove an object, repair a damaged patch, swap a logo area, clean a background behind a subject, or fill a masked region without rebuilding the whole image.

Don't use it for a fresh image from scratch. Use image-generate for drafts, image-generate-pro for higher-quality generation, and image-generate-ultra for flagship models. Inpainting is for controlled edits where the existing pixels still matter.

Why this note exists

The artifact audit caught the gap: the endpoint existed in the registry and deployer, but no /updates article named it. That leaves crawlers and routing agents with less text to learn from, and it makes it harder to tell why an image-editing call should go to image-inpaint instead of a generic generator.

Now the endpoint has a specific public reference. The registry still carries the exact schema and price; this article explains the job boundary.