<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CRJ</title>
    <description>The latest articles on DEV Community by CRJ (@crj_787403881c99662c653e8).</description>
    <link>https://dev.to/crj_787403881c99662c653e8</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4110602%2F1f71a147-d8e0-4a25-b475-df5a3ae8241e.png</url>
      <title>DEV Community: CRJ</title>
      <link>https://dev.to/crj_787403881c99662c653e8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/crj_787403881c99662c653e8"/>
    <language>en</language>
    <item>
      <title>I built an AI API that turns any online store URL into a structured product catalog</title>
      <dc:creator>CRJ</dc:creator>
      <pubDate>Sat, 05 Sep 2026 04:03:08 +0000</pubDate>
      <link>https://dev.to/crj_787403881c99662c653e8/i-built-an-ai-api-that-turns-any-online-store-url-into-a-structured-product-catalog-5775</link>
      <guid>https://dev.to/crj_787403881c99662c653e8/i-built-an-ai-api-that-turns-any-online-store-url-into-a-structured-product-catalog-5775</guid>
      <description>&lt;p&gt;I watched a store owner retype 600 products by hand while migrating platforms. It took her team two weeks. That pain became this API.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;You POST one URL — the homepage of any online store. The API crawls it the way a person would (categories, pagination, product pages) and returns the entire catalog as structured JSON: name, brand, category, price, SKU, photos, and an AI-written description for every product.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://.../v1/extract &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer KEY"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"url": "https://any-store.com"}'&lt;/span&gt;
&lt;span class="c"&gt;# → {"job_id": "...", "poll": "/v1/jobs/&amp;lt;id&amp;gt;"}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No CSS selectors to configure. No per-site templates to maintain. The LLM reads each page and understands it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The hard part was not the crawling
&lt;/h2&gt;

&lt;p&gt;Everyone assumes the crawler is the hard part. It isn't — &lt;code&gt;fetch&lt;/code&gt; plus a BFS queue gets you there in an afternoon.&lt;/p&gt;

&lt;p&gt;The hard part is that &lt;strong&gt;e-commerce pages lie to you&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A category page looks exactly like a product page ("Steel Drill 4-12mm — from $29").&lt;/li&gt;
&lt;li&gt;Listing cards carry a name, a price and a photo — everything a product has.&lt;/li&gt;
&lt;li&gt;The same product appears at &lt;code&gt;/drills/steel-drill&lt;/code&gt; and &lt;code&gt;/promo/steel-drill&lt;/code&gt; with different descriptions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We shipped three "cleanup guards" that only exist because each one fixed a real production incident: a listing-card detector (if a page links to N similar slugs, it's a category — return null), a dedup pass with slug-digit tie-breaking, and a parent-category pruner. The prompt itself instructs the model to answer &lt;em&gt;null&lt;/em&gt; when the page isn't a single product — teaching the AI to say "this isn't a product" mattered more than teaching it to extract.&lt;/p&gt;

&lt;h2&gt;
  
  
  Numbers from a real run
&lt;/h2&gt;

&lt;p&gt;A Brazilian industrial-tools store, cold start: &lt;strong&gt;160 pages crawled → 126 candidates → 50 clean products in 72 seconds&lt;/strong&gt;, ~113k input tokens. Zero duplicates, zero category pages leaking into the results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest limitations
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;JavaScript-rendered storefronts (SPA) aren't supported yet — that's the next tier.&lt;/li&gt;
&lt;li&gt;One page = one product is assumed; stores where SKUs only exist inside filterable listings won't extract.&lt;/li&gt;
&lt;li&gt;It respects robots.txt by default (there's an owner-override flag).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;There's a free tier (50 calls/month, no card): &lt;a href="https://rapidapi.com/felipelacerda/api/ai-product-catalog-extractor" rel="noopener noreferrer"&gt;AI Product Catalog Extractor on RapidAPI&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Live demo of a real extraction (50 products, with photos): &lt;a href="http://72.60.244.148:3024/robo/" rel="noopener noreferrer"&gt;demo page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'd genuinely love to hear about stores that break it — edge cases are the roadmap.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>llm</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
