Why check a tile before it prints?
A tile can look finished on its own and still show a line where its copies meet: a faint white line, a grid of pixel lines, edges a few pixels off. The line often appears only once the pattern repeats at print size, on the proof or on the product, after the sample or the order is paid for. Fixing it by hand is trial and error, and the same steps do not promise the same result. Why tiles show a line explains where seams come from and what a verified result means.What does the API do?
Send a tile and learn, for each repeat type (straight, half-drop and half-brick), whether it tiles without a seam and where its edges break. When it does not, start a fix and get the same tile back at the exact same pixel size, repeating cleanly for the repeat type you chose. The result carries the seam report before and after and a mask of what changed; outside that area, every pixel is your original.What do I need to start?
- A tile: a PNG, JPEG or WebP image
- For a fix, an API key from your account
Where does the check fit in my workflow?
Check each tile where a seam usually slips in, before any money is spent: after you make or generate it, after you resize or export it for print, and before you upload it to a print-on-demand shop or order a sample. Fix only the repeat types you sell in that fail. An agent can run the same check on every tile it makes; Connect an agent shows how.Explore
Check a tile
A verdict per repeat type, free and at once.
Fix a tile
A job that returns the tile repeating cleanly.
What a fix costs
Credits, the free fix of the day, plans.
Connect an agent
A prompt, a skill file and the machine files.
Reference
API introduction
Base URL, authentication, answers, versioning.
Errors
Every stable code and when a retry helps.