<?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: ding</title>
    <description>The latest articles on DEV Community by ding (@_c5e884da318ceb903633f).</description>
    <link>https://dev.to/_c5e884da318ceb903633f</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%2F4017367%2F6069ffb9-bf3d-43a5-8a72-3d44bbf5fe6b.png</url>
      <title>DEV Community: ding</title>
      <link>https://dev.to/_c5e884da318ceb903633f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/_c5e884da318ceb903633f"/>
    <language>en</language>
    <item>
      <title>How I built a desktop console for managing LLM API keys, model discovery, and local routing</title>
      <dc:creator>ding</dc:creator>
      <pubDate>Mon, 06 Jul 2026 09:58:43 +0000</pubDate>
      <link>https://dev.to/_c5e884da318ceb903633f/how-i-built-a-desktop-console-for-managing-llm-api-keys-model-discovery-and-local-routing-37i7</link>
      <guid>https://dev.to/_c5e884da318ceb903633f/how-i-built-a-desktop-console-for-managing-llm-api-keys-model-discovery-and-local-routing-37i7</guid>
      <description>&lt;p&gt;Managing multiple LLM provider APIs sounds simple until the number of keys, relay sites, model names, and desktop clients starts to grow. I built AllApiDeck because I wanted one place to import records, organize them, test what actually works, and route requests through a local workflow that is easier to observe and debug.&lt;/p&gt;

&lt;p&gt;AllApiDeck is aimed at people who juggle many providers and client tools. It includes import and grouping, model discovery, quick checks, routing, and request tracing.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/jlwebs/AllApiDeck" rel="noopener noreferrer"&gt;https://github.com/jlwebs/AllApiDeck&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>llm</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I built a desktop console for managing LLM API key</title>
      <dc:creator>ding</dc:creator>
      <pubDate>Mon, 06 Jul 2026 09:28:44 +0000</pubDate>
      <link>https://dev.to/_c5e884da318ceb903633f/how-i-built-a-desktop-console-for-managing-llm-api-key-4d8i</link>
      <guid>https://dev.to/_c5e884da318ceb903633f/how-i-built-a-desktop-console-for-managing-llm-api-key-4d8i</guid>
      <description>&lt;p&gt;How I built a desktop console for managing LLM API keys, model discovery, and local routings, model discovery, and local routing&lt;br&gt;
Managing multiple LLM provider APIs gets messy fast. I built AllApiDeck because I wanted one place to import records, organize them, test what works, and route requests through a local workflow that is easier to observe and debug.&lt;/p&gt;

&lt;p&gt;Highlights:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;import from browser-extension backups&lt;/li&gt;
&lt;li&gt;batch model discovery and health checks&lt;/li&gt;
&lt;li&gt;grouping and filtering&lt;/li&gt;
&lt;li&gt;client handoff&lt;/li&gt;
&lt;li&gt;local proxy failover and request tracing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/jlwebs/AllApiDeck" rel="noopener noreferrer"&gt;https://github.com/jlwebs/AllApiDeck&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
