Why one line becomes many
A pattern is one tile placed again and again, edge to edge. If the right edge of the tile does not run on into its left edge, the break shows at every join. On a mug that is a few lines; on a duvet cover or a wallpaper sample it is a grid across the whole surface. Most of these tiles look fine on their own, which is why the problem tends to be found on the finished mockup rather than in the design file. A check only matters when the copies touch, so it applies to a pattern with no gap between tiles. Withtile_spacing above 0, each copy stands on its own
and there is no join to check.
From the API
Send the tile to Check seams as a URL or as base64. If the render will usefit set to crop, add crop_aspect,
the tile’s width divided by its height, so the check looks at the same cut the
render makes.
cURL
data.status:
seamless: render as it is.faint_seam: a slight line. Fine for most products; fix it for a print seen up close.visible_seam: a line most people will notice. Fix it before you render.
From an agent
An agent connected over MCP has the same two steps as tools:check_seams,
which is free, and fix_seams, which spends credits. A good agent checks every
pattern before it renders one, and asks you before it starts a fix.
Connect an agent covers the connection.
When the answer is a seam
Fix seams repairs the tile as a job and gives you a new file to render with. Its credits come back if the fix fails, and a tile you have already fixed is returned by the next check rather than charged again. A tile with transparent edges cannot be fixed; fill the edges in the design file first. Check and fix pattern seams walks through the whole flow, the job and the webhook.Check and fix pattern seams
The check, the fix, the job and the webhook in one place.