<?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 หนึ่งฤทัย ธรรมศิริ (@__cb0eca).</description>
    <link>https://dev.to/__cb0eca</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%2F4061841%2F139681b5-756d-4a84-9acc-c5d1adea5b9b.png</url>
      <title>DEV Community: หนึ่งฤทัย ธรรมศิริ</title>
      <link>https://dev.to/__cb0eca</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__cb0eca"/>
    <language>en</language>
    <item>
      <title>Why AI API workflows become messy as projects grow</title>
      <dc:creator>หนึ่งฤทัย ธรรมศิริ</dc:creator>
      <pubDate>Thu, 13 Aug 2026 02:26:03 +0000</pubDate>
      <link>https://dev.to/__cb0eca/why-ai-api-workflows-become-messy-as-projects-grow-28ab</link>
      <guid>https://dev.to/__cb0eca/why-ai-api-workflows-become-messy-as-projects-grow-28ab</guid>
      <description>&lt;p&gt;When building a small AI demo, working with APIs usually feels simple.&lt;/p&gt;

&lt;p&gt;You choose a model, send a request, test the response, and move on.&lt;/p&gt;

&lt;p&gt;But once the project grows, the workflow becomes more complicated. The hard part is often not the model itself, but everything around it.&lt;/p&gt;

&lt;p&gt;Developers may need to answer questions like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where do we compare available models?&lt;/li&gt;
&lt;li&gt;How do we track usage across projects?&lt;/li&gt;
&lt;li&gt;Where do we find integration docs?&lt;/li&gt;
&lt;li&gt;How do we keep API access organized?&lt;/li&gt;
&lt;li&gt;How do we avoid switching between too many dashboards?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the operational layer of AI development, and it is easy to underestimate.&lt;/p&gt;

&lt;p&gt;A better AI API workflow usually needs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A clear place to explore models&lt;/li&gt;
&lt;li&gt;A simple way to manage API access&lt;/li&gt;
&lt;li&gt;Usage visibility&lt;/li&gt;
&lt;li&gt;Easy-to-find integration documentation&lt;/li&gt;
&lt;li&gt;A dashboard that connects these pieces together&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the reason I started working on ChinaRouter.&lt;/p&gt;

&lt;p&gt;ChinaRouter is a unified AI API gateway and admin dashboard. It focuses on model marketplace access, API gateway workflow, usage lookup, dashboard management, and integration documentation.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://chinarouter.net/" rel="noopener noreferrer"&gt;https://chinarouter.net/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For developers building AI products: what part of API management becomes painful first?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj5jzwv99ct76v56w447w.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj5jzwv99ct76v56w447w.png" alt=" " width="457" height="483"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fml8khv8cj6iotn6xcw4p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fml8khv8cj6iotn6xcw4p.png" alt=" " width="451" height="552"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
    </item>
    <item>
      <title>Why AI API workflows become messy as projects grow</title>
      <dc:creator>หนึ่งฤทัย ธรรมศิริ</dc:creator>
      <pubDate>Fri, 07 Aug 2026 06:36:33 +0000</pubDate>
      <link>https://dev.to/__cb0eca/why-ai-api-workflows-become-messy-as-projects-grow-4235</link>
      <guid>https://dev.to/__cb0eca/why-ai-api-workflows-become-messy-as-projects-grow-4235</guid>
      <description>&lt;p&gt;When building a small AI demo, working with APIs usually feels simple.&lt;/p&gt;

&lt;p&gt;You choose a model, send a request, test the response, and move on.&lt;/p&gt;

&lt;p&gt;But once the project grows, the workflow becomes more complicated. The hard part is often not the model itself, but everything around it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where do you compare available models?&lt;/li&gt;
&lt;li&gt;How do you track usage across projects?&lt;/li&gt;
&lt;li&gt;Where do developers find integration docs?&lt;/li&gt;
&lt;li&gt;How do teams keep API access organized?&lt;/li&gt;
&lt;li&gt;How do you avoid switching between too many dashboards?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the operational layer of AI development, and it is easy to underestimate.&lt;/p&gt;

&lt;p&gt;A better AI API workflow usually needs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A clear place to explore models&lt;/li&gt;
&lt;li&gt;A simple way to manage API access&lt;/li&gt;
&lt;li&gt;Usage visibility&lt;/li&gt;
&lt;li&gt;Easy-to-find integration documentation&lt;/li&gt;
&lt;li&gt;A dashboard that connects these pieces together&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the reason I started working on ChinaRouter.&lt;/p&gt;

&lt;p&gt;ChinaRouter is a unified AI API gateway and admin dashboard. It focuses on model marketplace access, API gateway workflow, usage lookup, dashboard management, and integration documentation.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://chinarouter.net/" rel="noopener noreferrer"&gt;https://chinarouter.net/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For developers building AI products: what part of API management becomes painful first?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
    </item>
    <item>
      <title>Sharing ChinaRouter, a unified AI API gateway</title>
      <dc:creator>หนึ่งฤทัย ธรรมศิริ</dc:creator>
      <pubDate>Wed, 05 Aug 2026 04:32:15 +0000</pubDate>
      <link>https://dev.to/__cb0eca/sharing-chinarouter-a-unified-ai-api-gateway-3eae</link>
      <guid>https://dev.to/__cb0eca/sharing-chinarouter-a-unified-ai-api-gateway-3eae</guid>
      <description>&lt;p&gt;I wanted to share ChinaRouter with the DEV community.&lt;/p&gt;

&lt;p&gt;ChinaRouter is a unified AI API gateway and admin dashboard for developers, AI builders, and teams.&lt;/p&gt;

&lt;p&gt;It helps organize key AI API workflows such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Model marketplace access&lt;/li&gt;
&lt;li&gt;Usage lookup&lt;/li&gt;
&lt;li&gt;Dashboard management&lt;/li&gt;
&lt;li&gt;Integration documentation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are building AI applications or managing model-based workflows, it may be useful to explore.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://chinarouter.net/" rel="noopener noreferrer"&gt;https://chinarouter.net/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback is welcome.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/..." class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/..." alt="Uploading image" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>webdev</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
