AI agents inside an e-commerce brand, for sellers and shoppers
Agents that write product copy and images for sellers, a shopping assistant that answers by voice, and the architecture that ties them into a store already running.
Role
AI Product Engineer, LeanScale
Status
Client work
Period
to
Stack
TypeScript,Mastra
Source
Not public
Outcome
about 60% less manual setup time
about 60%
less manual setup time
At LeanScale I designed how AI agents fit into an established e-commerce brand, and the system architecture for the whole integration. It has two audiences. Sellers get agents that take over the slow parts of listing products. Shoppers get an assistant that helps them find what they came for, by voice if they want.
How the commerce agents fit together
can say no
the gate
Both sides run on one agent layer, and nothing reaches the store without passing validation.
Sellers: copy and images
A good listing needs a description that sells and pictures that show the product properly, for every product, and again whenever it changes. The seller agents rewrite descriptions automatically and generate new product images, so a seller reviews and approves instead of starting from a blank page.
Shoppers: finding it, out loud
On the other side, the discovery assistant helps shoppers find the product they actually want, not just the one that matches their keywords. It also listens: a voice pipeline with wake-word detection lets someone ask out loud, the way they would ask a person in a shop.
Every action checked first
This is a store that is already running, so agents act on real products, real orders and other companies' systems. The setup agent shows the rule everything follows. It works in stages, and each stage hands the next something concrete that can be checked on its own.
1
Parse the intent
What is being asked for, in a structured form.
2
Select a tool
Which operation can do it.
3
Validate the action
Check the action before it runs.
4
Execute
Run it against the store or the third-party API.
Each stage hands a checkable result to the next one. Nothing reaches a third-party API without passing validation.
A misunderstanding shows up as a wrong intent before any tool is chosen, and a right tool with wrong arguments is caught by validation. The model proposes and the code checks. With that in place, manual setup time for third-party integrations dropped by about 60%.
This was client work at LeanScale, so the code is not public.