<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TokenBridge]]></title><description><![CDATA[TokenBridge]]></description><link>https://tokenbridge.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 15:20:45 GMT</lastBuildDate><atom:link href="https://tokenbridge.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[I Sell DeepSeek API Credits to People Who Can't Pay for Them — Week 1, Honest Numbers]]></title><description><![CDATA[This is a build-in-public log for a very small, very specific business: TokenBridge. It sells prepaid DeepSeek API credit to developers outside China. Week…]]></description><link>https://tokenbridge.hashnode.dev/i-sell-deepseek-api-credits-to-people-who-can-t-pay-for-them-week-1-honest-numbers</link><guid isPermaLink="true">https://tokenbridge.hashnode.dev/i-sell-deepseek-api-credits-to-people-who-can-t-pay-for-them-week-1-honest-numbers</guid><category><![CDATA[AI]]></category><category><![CDATA[api]]></category><category><![CDATA[Deepseek]]></category><category><![CDATA[buildinpublic]]></category><category><![CDATA[Startups]]></category><dc:creator><![CDATA[TokenBridge]]></dc:creator><pubDate>Wed, 18 Nov 2026 13:35:19 GMT</pubDate><content:encoded><![CDATA[<p>This is a build-in-public log for a very small, very specific business: <strong>TokenBridge</strong>. It sells prepaid DeepSeek API credit to developers outside China. Week 1 numbers are at the bottom, and they're not flattering — that's the point of writing them down.</p>
<h2>The problem I kept seeing</h2>
<p>DeepSeek's API is cheap and capable, and its price list is public. But the official top-up page runs on Alipay/WeChat Pay. If you're a developer in Berlin, Lagos, São Paulo or Jakarta, there's a decent chance you simply have no working way to put money into the account. The API is not the product problem. The checkout is.</p>
<p>So the business is unglamorous on purpose:</p>
<ul>
<li>An OpenAI-compatible relay endpoint (model exposed as <code>deepseek-flash</code>), upstream is the official DeepSeek API</li>
<li>Prepaid packs instead of postpaid billing: <strong>$9 / 12M tokens, $19 / 30M, $49 / 100M, $149 / 400M</strong>, each valid 30 days</li>
<li>Payment in USDT (TRC20) — not because crypto is trendy, but because it's the rail that works in the most countries with the least setup</li>
<li>No prompt storage, no silent model swapping, official upstream only</li>
</ul>
<h2>What week 1 actually looked like</h2>
<ul>
<li>Built the gateway, the shop, and the payment chain; verified end-to-end with real calls and re-measured the token burn rate (my first quota estimate was ~6× too generous — better to find that before customers do)</li>
<li>Published two articles on Dev.to: one comparing every workaround for the payment problem, one breaking down the same 100M tokens at $360 on Claude Sonnet vs $49 in a quota plan</li>
<li>Opened accounts and listings across a pile of platforms and directories; several rejected automated signups outright, one directory wanted $49 for a "free" listing, another won't accept a bare-IP website at all</li>
<li><strong>Sales: 0. Article engagement so far: also basically 0.</strong></li>
</ul>
<h2>What I think week 1 taught me</h2>
<p>Distribution is the whole game. The product took days; getting a single qualified stranger to read a page is the hard part. Directories and profiles are cheap to create and mostly worthless on their own — they only matter once real content points at them. So week 2 is mostly: more useful content (setup tutorials people actually search for), answering questions where developers already ask them, and being honest in public about the numbers, including the zeros.</p>
<p>If you run something similar — a small API business, a reseller model, anything where payments are the moat — I'd genuinely like to compare notes in the comments. And if you're a developer who has hit the DeepSeek payment wall yourself, I'm curious which workaround you ended up with.</p>
<p><em>TokenBridge, for the record: <a href="http://173.254.217.33/">http://173.254.217.33/</a> — prepaid DeepSeek packs, USDT checkout, official upstream.</em></p>
]]></content:encoded></item></channel></rss>