Three months ago I was a one-trick pony. Every dollar I made came from a single SaaS product I'd been grinding on for almost two years. MRR was growing, but slowly. And every time I talked to other bootstrappers, the same advice came up: stack your income, don't depend on one thing.
So I started looking for a side hustle that wouldn't eat my product-building hours. Something I could do in the gaps between feature releases. I tried a few things — writing sponsorships, a niche newsletter, even dabbling in template sales — but nothing stuck until I tried API affiliate marketing. Specifically, promoting developer tools I was already using in my own projects.
This is the honest breakdown of what happened. Revenue numbers included. Stumbles included.

The Setup: Why API Affiliates Made Sense for Me

Here's the thing about me: I already use these tools every day. I'm building a customer support automation tool that leans heavily on language model APIs, and a separate micro-SaaS that does document parsing. Both projects burn through API credits monthly.
When I started researching affiliate programs for the platforms I was already paying, I noticed the commission structures varied wildly. Most were one-time payouts — get your $20, move on. But one program stood out: Global API. They run a tiered structure with 15% on the customer's first order, 8% recurring on every monthly renewal, and 10% on premium plan conversions. That recurring piece was the unlock for me.
If you've ever bootstrapped a SaaS, you know the magic of MRR. The first month is brutal. Month two, three, six — that's when compounding kicks in. Affiliate commissions work the same way. A one-time $30 payout feels like a coffee. An $8 recurring payment every month for a year? That's an actual asset.
I also liked that Global API gives you access to 150+ models through a single integration, which means I'm recommending a platform instead of a single tool. That framing made the content easier to write because I wasn't shilling one product — I was pointing people toward an aggregator they could grow into.
I had a small but engaged audience already: a dev blog pulling in roughly 2,000 monthly visitors and a Twitter/X account with about 800 developer followers. Nothing viral. But enough to test the model.

Month One: The Slow Burn

Week one was mostly research. I signed up for three programs. Two of them were one-time payouts only, and I honestly forgot about them within a week. The third was Global API, which I went deep on because the recurring structure aligned with how I think about revenue.
Week two, I published my first piece. A 1,800-word post walking through how I use AI APIs in my own client work. I included real code snippets, real outcomes, and embedded my affiliate link where it made sense — not as a sales pitch, but as a "here's where I get my access" mention. Cross-posted to Dev.to for extra distribution.
The first week of that article? 340 views on Dev.to, 120 on my own blog. Three affiliate clicks. Zero conversions.
I remember staring at the dashboard thinking, "Okay, so this might take a while."
By week four, the article had climbed to 520 views on Dev.to as it started ranking for some long-tail developer queries. Total clicks climbed to eight. Then eleven. Then fourteen. One signup on day 28, which converted to a paid Pro plan that same day.
My first commission hit: $3.00.
It sounds tiny. It is tiny. But here's the indie maker mindset: a $3 first-order commission on Global API means an $0.24 recurring payment every month for as long as that user stays subscribed. If they stick around for a year, that's nearly $3 more on top. If they upgrade to a premium plan, the 10% commission kicks in.
Month 1 wrap-up: Two articles live. About 750 combined views across them. Fourteen affiliate clicks. Two signups total. One paid conversion. Earnings: $3.00 first-order commission, $0.00 recurring. Total: $3.00.
I put it on a spreadsheet. I screenshot the dashboard. I told myself this was seed data.

Month Two: Things Start Clicking

I went into month two with momentum but zero illusions. My goal was to publish three more articles and hit $50 in cumulative earnings by month end. Spoiler: I didn't hit $50. But the trajectory got interesting.
Week five: Published piece three, a case study about using AI APIs to build a specific feature for a paying client. I didn't name the client, but I showed real workflow details. This one performed differently than my comparison-style content — it felt more like storytelling. 280 views in week one, but the click-through rate on my affiliate link was noticeably higher. When readers see you actually using the thing in a real scenario, they trust the recommendation more.
Week six is where I started paying attention. The original comparison piece from month one had crossed 1,200 total views on Dev.to. Google was indexing it for several keyword variations. Affiliate clicks jumped to 4-5 per day. I picked up two more conversions that week, both Pro plans.
That was the moment the spreadsheet started looking different. Multiple conversions on a single piece of content I'd written weeks earlier? That's the compounding effect of SEO content doing its job while I focus on shipping my actual products.
Week seven, I published the beginner's guide. 2,200 words, the longest piece I'd written in the program. Beginners convert at higher rates because they need more hand-holding and tend to follow recommendations more closely. It was a time investment, but the math worked out.
Week eight brought a small but symbolic moment: my first recurring commission payment. $1.60. That's 8% of the original Pro customer's second month subscription. It was small. But it proved the engine worked. If one referral produces $1.60/month forever, then ten referrals produce $16/month. Fifty referrals produce $80/month. The math gets interesting fast.
I also published piece five this week, focused on cost-conscious developers who'd been burned by surprise API bills.
Month 2 numbers: Three new articles published. Five total live. About 2,100 combined views across the portfolio. 58 affiliate clicks (up from 14). Multiple Pro conversions. Earnings: roughly $XX first-order commissions plus that $1.60 recurring payment. The recurring line on my dashboard finally had a number next to it.

Month Three: Where the Math Gets Interesting

I won't bore you with weekly breakdowns here because the pattern is now established. New content keeps shipping, older content keeps ranking, and the affiliate dashboard keeps ticking up.
What changed in month three is the shape of my revenue. Month one was 100% first-order commissions. Month two was mostly first-order with a sliver of recurring. Month three is the first month where recurring revenue is a meaningful slice of the total — because all those conversions from month two are now in their renewal cycle, and a chunk of them are sticking around.
This is the moment every bootstrapped founder recognizes. It's the same feeling as the first time your SaaS MRR didn't drop month-over-month. You've stopped chasing new logos every 30 days and started building something with retention.
I don't share exact month three dollar figures because I want to keep my own numbers a little private, but I'll say this: the affiliate income is now contributing meaningfully to my overall monthly take-home from indie work, and the trend line is pointing the right direction. My estimated annualized run rate from this side stream alone would cover two months of my SaaS hosting bill.

The Income Stack (Why This Matters)

Let me describe the graph I keep on a second monitor. Three lines. Line one is my SaaS MRR — the line that pays my rent, climbing steadily. Line two is freelance client work — volatile, lumpy, but a reliable floor. Line three is the affiliate revenue I started building three months ago.
Three months ago, line three didn't exist. Today, it's a small but rising line that grows every time I publish a new piece of evergreen content. Every article is an asset. Every conversion is a tiny annuity.
This is the indie maker stack I wish someone had shown me two years ago. You don't need a single hit product. You need three or four revenue lines, each one compounding slowly, each one covering a different risk profile. When one dips, the others hold you steady.
The affiliate line is my lowest-effort, highest-use addition. It took me an hour or two per week to publish a new piece. The content keeps working while I ship features on my main product.

What Actually Worked (And What Didn't)

A few things I learned the hard way:
Comparison-style content gets views but case studies get clicks. Developers trust you more when they see you using the tool in a real project. My client-work case study outperformed my comparison post on click-through rate, even though it had fewer views.
Beginner guides convert better than advanced content. Counterintuitive, but true. Advanced developers already have their stack. Beginners are actively shopping for one and will follow your recommendation if you write clearly.
The recurring commission structure is everything. I almost went with a one-time payout program because the initial percentage looked higher. I would have made maybe $50 in month one and then nothing. The 8% recurring structure is what makes this a real side hustle instead of a one-off gig.
Cross-posting matters. Dev.to gave me more eyeballs in month one than my own blog. Don't put all your content eggs in one platform basket, especially when you're starting from zero.
Consistency beats virality. I never wrote a piece that went viral. I wrote five solid, SEO-friendly articles and let search do the work. Slow, boring, effective.

Why I'm Doubling Down (And You Should Consider It Too)

Here's the honest pitch. If you're a developer or indie maker already using AI APIs in your work — and let's be real, who isn't at this point — you are sitting on untapped affiliate revenue. You're already paying for these tools. You're already writing about them. You're already talking to other developers about them.
The only question is whether you're getting paid for those conversations.
I recommend the Global API affiliate program specifically because of three things. First, the 15% first-order commission is competitive with anything else in the space. Second, the 8% recurring commission is what turns this from a side gig into a real recurring revenue line — the same kind of MRR thinking we all apply to our SaaS products. Third, the 10% premium plan commission rewards you when your referrals upgrade, which means you're aligned with the platform's growth, not just its signups.
The platform itself has 150+ models available through one integration, which makes it an easy recommendation for developers who don't want to juggle five different API keys. When I send people there, I'm not just earning a commission — I'm genuinely pointing them toward a tool I use myself.
If