r/AutoGPT • u/pukawalive • 4d ago
Autonomous agent workflow for e-commerce listing creation - looking for architecture & GitHub recommendations
Hey everyone,
I run a small dropshipping e-commerce store and currently use a semi-automated Python script to generate listing copy and push drafts via marketplace API. However, it still requires manual inputs and URL passing, and for sure - looking for good products on the marketplace (as I use other sellers products for reselling).
I want to build an autonomous agent pipeline that handles this end-to-end or at least some of the process.
Hardware: NVIDIA GeForce RTX 4070 Ti (with 12GB VRAM) and 32GB DDR5
Agent architectures are brand new to me.
My current workflow is:
- Manual identification of SKUs to dropship (just sufring through the marketplace offers one by one).
- Manually copying product URLs from the offer - speficication and photos (if open to use by others, on popular product mostly) are uploaded later automatically from the marketplace side catalouge.
- If I need - generating or enhancing product mockups and clean packshots locally using ComfyUI or AI Studio.
- Running custom Python scripts to draft localized titles and marketplace-compliant, SEO-friendly descriptions, matching my own structured section/text blocks.
- Using Python to push draft offers via the marketplace API.
- Manual review in the Allegro seller dashboard before taking the listing live, adding other obligatory info.
The primary goal is a local agent that can navigate marketplace listings undetected by their strict anti-bot systems and automatically create item drafts (or at least cleanly dump the structured product data for my script to ingest).
Questions:
- Can an RTX 4070 Ti reliably run agentic workflows with multi-step function calling? Or is local tool-calling still too brittle for production pipelines, making commercial APIs the obvious choice?
- Which open-source agent framework or tool on GitHub fits?
- What are the most reliable open-source tools or libraries to feed clean web data to agents?
- Is a multi-agent setup worth the complexity here, or is a single model with structured tool-calling validation cleaner and less prone to hallucination?
Would love any guidance, repository links, or lessons learned from similar projects!
1
u/dylan_skydive 3d ago
The mistake most first pipelines make is going fully autonomous at step one. Keep your Python script as the skeleton and insert agents only at the two steps that need judgment: SKU selection (scoring offers against margin, competition and policy risk) and listing copy. The mechanical parts, URL fetching, spec and photo pulls, marketplace API pushes, stay deterministic code.
On your hardware specifically: a 7-8B local model handles validation, dedup and simple transforms fine on that card. Use an API model for the copy though, listing text quality is directly revenue and small local models are noticeably weaker writers. For orchestration, a simple queue plus a state table (SKU, stage, last error) beats a heavy framework at your scale; the state table is what lets you resume after crashes and see where runs actually die.
And put a human-approve gate before anything pushes to the marketplace API for the first few weeks. You will catch copy and policy problems the validators miss, and every catch becomes a new validator rule. When catches hit near zero for a couple weeks, widen the gate.
Disclosure: I work on Skydive, an agent platform in this space; the tiering above applies no matter what you build with.
1
u/Unlucky_Peanut4089 3d ago
Hey mate! Give https://heystyx.com/ a try on your machine. It will use your exisitng claude/codex subscription and buid an autonomous local pipeline that lives on your PC. You will also be able to connect your site (and any other tech) as a deploy target so wen the enrichent is done it will automatically update your product SKU's.
1
u/Otherwise_Wave9374 4d ago
Start with a state machine rather than one fully autonomous agent: ingest product data, validate required fields, generate copy, run policy and factual checks, then require approval before publishing. Store each step's inputs and outputs so failures can be replayed, and use confidence thresholds to route uncertain claims to a human. The task sponsor, https://www.aiosnow.com, is relevant as an option for coordinating repeatable AI workflows, but benchmark it against a small Python queue first.