<?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: 김다희</title>
    <description>The latest articles on DEV Community by 김다희 (@_28e4bcc1b34aa22bcdfcb).</description>
    <link>https://dev.to/_28e4bcc1b34aa22bcdfcb</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%2F3984046%2F536501f5-dd25-467b-88e0-8ec206afa67f.png</url>
      <title>DEV Community: 김다희</title>
      <link>https://dev.to/_28e4bcc1b34aa22bcdfcb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/_28e4bcc1b34aa22bcdfcb"/>
    <language>en</language>
    <item>
      <title>Added a Premium 'Compliance Bulk Report' to my K-Beauty API &amp; Shipped Tiered Pricing</title>
      <dc:creator>김다희</dc:creator>
      <pubDate>Mon, 15 Jun 2026 14:22:07 +0000</pubDate>
      <link>https://dev.to/_28e4bcc1b34aa22bcdfcb/added-a-premium-compliance-bulk-report-to-my-k-beauty-api-shipped-tiered-pricing-2fgm</link>
      <guid>https://dev.to/_28e4bcc1b34aa22bcdfcb/added-a-premium-compliance-bulk-report-to-my-k-beauty-api-shipped-tiered-pricing-2fgm</guid>
      <description>&lt;p&gt;Hey Indie Hackers,&lt;/p&gt;

&lt;p&gt;A while ago, I shared my API project here—a hallucination-free translator that converts Korean cosmetic ingredients into standard global INCI names to prevent customs rejections.&lt;/p&gt;

&lt;p&gt;Thanks to some amazing feedback and user requests, I realized that global cosmetics importers were suffering from a huge pain point: they hated doing compliance checks line-by-line.&lt;/p&gt;

&lt;p&gt;So today, I finally shipped a massive feature upgrade: The Compliance Bulk Report.&lt;/p&gt;

&lt;p&gt;🛠️ What's New?&lt;br&gt;
Bulk Upload: Users can now throw an entire product's ingredient list via a single API request instead of making dozens of separate calls.&lt;/p&gt;

&lt;p&gt;2026 Customs Cross-Check: The API automatically cross-checks the ingredients against the latest 2026 regulatory restrictions and flags banned or restricted chemicals instantly.&lt;/p&gt;

&lt;p&gt;Tiered Pricing Strategy: To monetize this high-value feature effectively without burning my own AI server costs, I moved away from flat pricing and introduced a tiered model on RapidAPI:&lt;/p&gt;

&lt;p&gt;Basic ($0): Free translation tests (500 requests limit, report feature locked).&lt;/p&gt;

&lt;p&gt;Pro ($19): Full access to the new Bulk Compliance Report (up to 100 times/mo) + 10,000 translation limits.&lt;/p&gt;

&lt;p&gt;Ultra ($49): Scale plan for bigger trading corps (1,000 reports / 50,000 translations).&lt;/p&gt;

&lt;p&gt;🔗 Live Store Link:&lt;br&gt;
You can check out the updated store and test the new endpoints here:&lt;br&gt;
&lt;a href="https://rapidapi.com/dahee8703dahee8703/api/legal-k-beauty-inci-translator" rel="noopener noreferrer"&gt;https://rapidapi.com/dahee8703dahee8703/api/legal-k-beauty-inci-translator&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For those who are running 1-man API SaaS businesses: how do you usually balance server token costs when offering heavy AI utility reports on low-tier plans? I went with a strict hard limit for now to keep things safe.&lt;/p&gt;

&lt;p&gt;Would love to get your thoughts on this pricing structure and the bulk update!&lt;/p&gt;

</description>
      <category>kbeauty</category>
      <category>cosmetics</category>
    </item>
    <item>
      <title>Built an API that translates Korean cosmetic ingredients into strict INCI standards (with AI hallucination control)</title>
      <dc:creator>김다희</dc:creator>
      <pubDate>Sun, 14 Jun 2026 14:51:58 +0000</pubDate>
      <link>https://dev.to/_28e4bcc1b34aa22bcdfcb/built-an-api-that-translates-korean-cosmetic-ingredients-into-strict-inci-standards-with-ai-46k2</link>
      <guid>https://dev.to/_28e4bcc1b34aa22bcdfcb/built-an-api-that-translates-korean-cosmetic-ingredients-into-strict-inci-standards-with-ai-46k2</guid>
      <description>&lt;p&gt;Hi everyone, I’ve noticed that many developers building Shopify apps or automated tools for K-Beauty dropshippers struggle heavily with ingredient translation.&lt;/p&gt;

&lt;p&gt;General translation tools (like DeepL or standard Google Translate) fail here because they don't provide regulatory-compliant INCI names, which can lead to strict customs rejections in the US or EU.&lt;/p&gt;

&lt;p&gt;To solve this specific bottleneck, I built the &lt;strong&gt;Legal K-Beauty INCI Translator API&lt;/strong&gt;. Instead of dealing with messy raw text, you just send the Korean ingredients via POST, and it returns a clean, structured JSON response.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key Features:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Strict INCI Output:&lt;/strong&gt; Returns an array of exact INCI standard names.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hallucination Control (Legal Safety):&lt;/strong&gt; If an ingredient is ambiguous or untranslatable, the API strictly refuses to guess and outputs "UNVERIFIED_MANUAL_CHECK_REQUIRED".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extra Data:&lt;/strong&gt; Automatically returns a Boolean for is_vegan_friendly and a general hazard_score.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's officially hosted on RapidAPI, so you can test the endpoint immediately without setting up a new billing account.&lt;/p&gt;

&lt;p&gt;🔗 &lt;strong&gt;Test the Endpoint here:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://rapidapi.com/dahee8703dahee8703/api/legal-k-beauty-inci-translator" rel="noopener noreferrer"&gt;https://rapidapi.com/dahee8703dahee8703/api/legal-k-beauty-inci-translator&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're building e-commerce software in the K-Beauty niche, I’d love to hear your feedback on the JSON structure or any additional data fields you might need!&lt;/p&gt;

</description>
      <category>api</category>
      <category>kbeauty</category>
      <category>saas</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
