When AI Generates Art: The Hidden Challenge of OCR and Transparency

Today we launched a new autonomous agent on Shilpiworks: the Minnesota Wildlife Agent. The goal was simple—take a dataset of 712 Minnesota wildlife species from the Department of Natural Resources, and have an AI automatically generate one beautiful, dreamy watercolor sticker every single day.

We mapped out the workflow using our Mastra-based pipeline:

1. 1Pick the next ungenerated species from the dataset.
2. 2Use Gemini to research and write factual marketing copy about the animal.
3. 3Use OpenAI's `gpt-image-1.5` to generate the watercolor illustration bounded by the silhouette of the Minnesota state map.
4. 4Auto-publish the result to our store.

Our first test subject was the "Western Meadowlark." It worked perfectly. But when we flipped the switch to live production and the agent attempted its first automated run for the "Ross's Goose," the pipeline ground to a halt.

Here is what we learned from our AI sticker agent today, and why building autonomous creative pipelines requires more than just a good prompt.

1. The Typography vs. Art Conflict

To make sure our customers know what species they are looking at, we asked the AI to subtly incorporate the species name into the watercolor design.

Our prompt: *"Subtly incorporate the text 'Ross's Goose' into the design."*

The AI did exactly what we asked. It painted the text. Literally. It rendered the letters as beautiful, sweeping, abstract watercolor brushstrokes.

The problem? Our pipeline includes a strict OCR (Optical Character Recognition) validation step to prevent misspelled or hallucinated text from making it to production. When the OCR scanner looked at the AI's abstract brushstrokes, it read *"Rossa Coosa"* instead of "Ross's Goose." The validation failed, and the agent blocked the publication.

When building AI image pipelines that require text, you cannot leave typography up to the model's artistic interpretation. You have to dictate the font style.

2. The Alpha Channel Assumption

Our stickers require a pure transparent background around the white die-cut border so they look correct on the website.

In our prompt, we asked for a *"Solid pure white background."* In older iterations of image models, we would run a background removal script to key out the white pixels. But with the newer OpenAI Responses API (`gpt-image-1.5`), the model has the native capability to generate transparent backgrounds.

However, we forgot to pass the correct API parameter. The AI generated the white die-cut border perfectly, but filled the rest of the square canvas with a flat gray color because we didn't explicitly ask the API for an alpha channel. Our automated transparency checker caught the gray pixels and failed the run.

The Takeaway

Building autonomous agents is an exercise in edge cases. The "happy path" (like our Western Meadowlark test) often hides the fragility of AI generation.

By building strict validation checks—like OCR text matching and alpha channel transparency verification—directly into the Mastra workflow, we prevented broken products from reaching the live store. It forced us to refine our prompts and API calls until the agent could truly run unsupervised.

Tomorrow morning at 8 AM, the Minnesota Wildlife Agent will wake up and paint another species. And this time, we know the text will be legible and the background will be transparent. Browse the growing collection at shilpiworks.com →