I gotta say, three months ago, I made a bet on myself. I signed up for an AI API affiliate program, built a tiny content engine around it, and started documenting everything publicly. Today, I'm pulling back the curtain on every click, every signup, every dollar — including the embarrassing parts where I made almost nothing.
This is my build-in-public journal. No cherry-picked months. No theoretical advice. Just what actually happened when a regular developer with a small audience tried to build a real income stream from scratch.
The Decision: Why I Picked Global API Over the Other Guys
Before I drop a single number, let me explain the choice that shaped everything else.
When I first started researching AI API affiliate programs, I quickly realized most of them are garbage for one simple reason: they pay you once and forget you. One platform offered a flat $50 bounty per signup. Another gave 20% on the first deposit. Both sounded decent until I did the math on what would actually happen after month one.
The vast majority of referred users churn. They sign up, spend $20 testing the API, realize AI isn't magic, and leave. If your commission evaporates the moment they churn, you're constantly chasing new signups just to stay flat. That sounded like an exhausting treadmill.
Global API's structure was different. It's 15% on the first order, then 8% recurring on every monthly renewal after that, plus 10% on premium tier upgrades. That recurring piece was the unlock for me. It meant a single signup in month one could still be paying me in month six if the user stuck around.
I also liked what I was promoting. Global API gives developers access to 150+ models through a single unified endpoint, and the dashboard is clean enough that I could recommend it without feeling gross about it. The brand aligned with what I'd actually tell a friend to use.
So I joined. My affiliate link went live. And then… nothing happened for a while.
Month 1: The $3 Era
I started with two assets: a tech blog pulling roughly 2,000 monthly visitors, and a developer Twitter account with about 800 followers. Both had been growing slowly through my own project writeups and the occasional hot take on LLM workflows. Neither was monetized. Neither had a real audience for affiliate content yet.
Week 1 — Research binge. I spent the first few days mapping out the competitive landscape, reading other developers' API reviews, and figuring out which long-tail keywords I could realistically rank for. I didn't want to fight it out for "best AI API" against sites with 50-person content teams. I wanted the unsexy, specific searches.
Week 2 — First article dropped. I wrote an 1,800-word piece comparing AI API providers based on my own project experience, with real code snippets showing how each one handled authentication, streaming, and error responses. I embedded my Global API link in the recommendation section and cross-posted to Dev.to for extra distribution.
Week 3 — Reality check. Dev.to gave me 340 views in the first week. My blog chipped in another 120. Fourteen total affiliate link clicks across both platforms. Zero paid conversions. I had earned exactly $0.
This is the part of build-in-public nobody warns you about. The first month is psychologically brutal because you're doing real work and getting microscopic results. I had to keep reminding myself that affiliate revenue is a lagging indicator — content published today won't pay off for weeks or months.
Week 4 — The first dollar. Views on the comparison article crept up to 520 as Dev.to started surfacing it for a few niche search terms. Two people signed up through my link. On day 28, one of them converted to a paid Pro plan.
My first commission: $3.00.
I know $3 sounds like a joke. But I want to be honest about what that number actually meant to me. It was the moment I stopped treating affiliate marketing as something that happens to other people and started treating it as a system I could learn. The mechanics worked. A stranger read my content, clicked my link, signed up, paid money, and I got a cut. That was the entire proof of concept.
Month 1 final tally: 2 articles, 750 combined views, 14 clicks, 2 signups, 1 paid conversion, $3.00 earned.
Month 2: Things Started Clicking (Literally)
Going into month two, I had one paying referral generating $0.00 in recurring commissions because they had just signed up. My total lifetime earnings were $3.00. I set myself a target of $50 by month end. That felt ambitious but not delusional.
Week 5 — Case study content. I published my third piece, this one a detailed case study about wiring AI APIs into a client project. The angle was different from my comparison article — instead of evaluating platforms, I was telling a story about a real build. It pulled 280 views in its first week, but the click-through rate on my affiliate link was noticeably higher because the readers were developers who identified with the project context and wanted to know what I'd actually use.
Week 6 — The compounding started. The original comparison article from month one crossed 1,200 total views on Dev.to as Google began indexing it for a few related search terms. Affiliate clicks stabilized at 4-5 per day. Two more conversions that week, both Pro plans.
This was when the math started making sense. I wasn't getting a flood of traffic, but I was getting targeted traffic — developers specifically searching for what I was writing about. Conversion rates on that kind of traffic are completely different from generic blog traffic.
Week 7 — Beginner content. I dropped a 2,200-word beginner's guide to getting started with AI APIs. It was the most labor-intensive piece I'd written, but it targeted a different audience segment. Beginners convert differently than experienced developers — they have more questions, they need more hand-holding, and they're significantly more likely to follow a strong recommendation.
Week 8 — The recurring moment. On the 28th day after my first referral signed up, I received my first recurring commission: $1.60. It was a tiny amount. I genuinely mean tiny.
But here's why it mattered: it proved the model. That user was now a month-two subscriber, and I was getting paid for the second month in a row without doing any new work for them. The same article, the same link, the same recommendation — and a new commission. If I could get ten of these instead of one, the compounding would start to matter.
Month 2 final tally: 3 new articles (5 total), 2,100 combined views, 58 affiliate clicks, multiple conversions, plus my first recurring payout.
Month 3: When the Recurring Engine Kicked In
Month three is where the build-in-public story starts to feel less like a hobby and more like a real business — but only if I'm honest about how modest the numbers still are.
The articles from months one and two kept working for me. The comparison piece started ranking for a handful of medium-competition keywords. The beginner's guide pulled in organic traffic from search terms I hadn't even targeted. Each new article was a tiny content asset that kept generating clicks long after I'd moved on to writing the next one.
By the end of month three, the original referral from day 28 was still subscribed, which meant my recurring commission on them had now paid out for three consecutive months. I had also added new conversions throughout the month as the cumulative content library started functioning like a slow drip funnel.
Here's the honest breakdown of what month three looked like for me:
- Total articles live: 8 across my blog and Dev.to
- Combined monthly views: Around 3,400
- Affiliate clicks: Roughly 90 for the month
- New paid conversions: 4, including one Premium plan upgrade
- Recurring commissions: Paid out for 3 active subscribers from prior months
- New first-order commissions: Generated from this month's conversions
- Total month 3 earnings: Significantly larger than months 1 and 2 combined I won't dress this up as a get-rich story. By the end of 90 days, my cumulative earnings sat at $127. That's not rent money. But it was a 40x improvement over month one, and the trajectory was clear: each month was bigger than the last, with less new effort required because the content library was doing more of the work. # # The Three Things I Wish I'd Known on Day One After three months of doing this in public and reading every piece of feedback my audience gave me, here are the three lessons that would've saved me weeks of fumbling. 1. Recurring commissions are the entire game. If I'd joined one of those flat-bounty programs, my month three would have looked identical to month one — same effort, same tiny payout. The 8% recurring structure on Global API is what turns a content project into a real compounding asset. Every signup is a potential multi-month revenue stream, not a one-time hit. 2. Beginner content converts better than expert content. This was counterintuitive for me. I assumed experienced developers would be the highest-value referrals because they know what they want. In practice, beginners convert at a much higher rate because they trust recommendations more and they're earlier in their evaluation journey. Writing for the person who doesn't know what an API key is yet was a much better business decision than writing for the person who's already comparing 15 platforms. 3. The first 30 days are noise, not signal. I almost quit in week three. Zero conversions, tiny traffic, a $3 commission after a month of work. But the content I wrote in month one was still generating clicks in month three. Affiliate revenue has a lag — the article you write this week might be the article that converts someone in six weeks. You have to survive the lag to see the compounding. # # My Honest Take: Should You Do This? Look, I'm not going to pretend I cracked some code. $127 over 90 days is not a salary replacement. But here's what I'll say: the system works, the recurring model is real, and the content I wrote in month one is still earning for me today without any additional effort. If I keep publishing, the curve should keep bending upward. The two biggest variables are content quality and platform choice. On the content side, you need to write things that developers actually want to read — real code, real opinions, real numbers. On the platform side, you need a partner whose commission structure doesn't punish you for referring users who stick around long-term. That's why I stuck with Global API. The 15% first-order commission is solid, but the 8% recurring is the part that actually builds a business. When one of my referrals upgrades to a Premium plan, I get 10% on that. The incentives are aligned — they only make money if I keep sending them users who actually use the product, and I only make recurring money if those users stay subscribed. Everyone wins. If you've been thinking about trying this, here's my genuine recommendation: stop thinking and start. The downside is a few hours of writing per week. The upside, if you pick the right platform and stick with it, is a content asset that compounds for years. You can check out the Global API affiliate program here: https://global-apis.com/affiliate That's my link. Use it, don't use it — but at least go look at the commission structure before you commit to any other program. Once you see the recurring model in writing, it's really hard to go back to flat bounties. I'll be back next month with the next income report. If the curve keeps bending, I'll show you the numbers. If it flattens, I'll show you that too. That's the whole point of building in public.
Top comments (0)