I Made $487 Last Month Promoting AI Tools — Here's Exactly How (As a Working Developer)

Let me be real with you for a second. I have a day job. I write code Monday through Friday for a mid-size SaaS company, and my salary is fine. Not glamorous, but fine. What actually moves the needle for me — the money that lets me take my partner on real vacations, that built up my emergency fund, that turned my Roth IRA contributions from "minimum" to "aggressive" — comes from the stuff I do between 8 PM and midnight, and on weekends.
Last month, one of those side hustles pulled in $487.17. I know the exact number because I track every dollar in a Notion database that I open roughly six times a day. That number is from a single program: the Global API affiliate program. I promote AI developer tools through blog content I wrote months ago, and the commissions keep rolling in.
Here's the full breakdown, the math, and exactly how I built this stream.

The Notion Page That Runs My Life

Before I get into the affiliate stuff, let me explain my tracking setup because it's the backbone of everything I do on the side. I have a Notion database called "Money Stuff" with one row per income source. Each row has columns for: source name, monthly revenue, hours invested, hourly rate, recurring vs. one-time, and a "vibe check" field where I write how much I dread working on it.
I update this every Sunday night. It's the first thing I look at on Monday mornings, even before checking my work Slack. If you want to build any kind of side income as a developer, I cannot stress this enough: track the per-hour return of everything you do. Without that number, you're just guessing. With that number, you can make actual decisions.
My five tracked side income streams, ranked by hourly return, are:

1. AI API affiliate commissions — $487/month, ~2 hours/month, $243/hr
2. SaaS product revenue — $950/month avg, ~5 hours/week, $57/hr
3. YouTube sponsorships — varies, $800-$1,400/video, ~15 hours/video
4. Freelance dev contracts — $120/hr but capped at ~10 hrs/week
5. Blog ad revenue — $310/month, ~6 hours/month for content upkeep, $52/hr Notice the affiliate line. $243 per hour. That's not a typo. That's the power of recurring revenue combined with content that keeps working after I write it. # # Why Affiliate Income Is the Sleeper Pick for Devs Let me break this down in developer terms. When you freelance, you're trading CPU time for money. The moment you stop executing, the revenue halts. It's like writing a synchronous function — await freelancer.work() blocks until you finish. Your income is directly proportional to hours billed, period. SaaS is better. Once you ship, you have something running in the background. But every SaaS product I have ever built or maintained eventually develops a bug, a flaky integration, or a customer support ticket at 11 PM. It's not fully passive. It's more like a long-running async task that occasionally throws exceptions you have to handle. Affiliate income with recurring commissions is the closest thing to a true background process I've found. You write content once, it lives on the internet, people find it, some of them sign up through your link, and you keep getting paid. Month after month. For the same piece of content. The "process" is already running. The crucial piece — and this is where most developer affiliate attempts fail — is that the commissions need to be recurring, not just one-time payouts. A 15% first-order commission is great, but if that customer never pays you again, you're constantly chasing new signups. An 8% recurring commission means that every customer who subscribes through your link is now a small, permanent line item in your monthly revenue. That compounding effect is where the magic happens. # # How I Picked Global API (and Why It Actually Converts) I want to be transparent about my selection process because I get a lot of questions about it. When I evaluate affiliate programs for my developer audience, I look at three things:
6. Is the product something I would actually use? If not, I can't recommend it authentically, and my readers can smell fake recommendations from a mile away.
7. Does the commission structure reward long-term customers? Recurring commissions only.
8. Is the product accessible enough that my readers will actually sign up? If the signup flow is a nightmare, conversion dies at step one. Global API hit all three. I've been using their platform for my own AI projects — the kind of weekend hacks that never see GitHub but teach me a lot. The thing that sold me on it as a developer was the consolidation: 150+ models accessible through a single API key. As someone who has wasted entire afternoons wiring up separate SDKs and managing credentials across different providers, I genuinely appreciate the unified setup. It's the kind of thing that, once you experience it, you want to tell other developers about. The affiliate commission structure is what made it worth turning that appreciation into content. Here's the exact math:
9. 15% on the first order a referral makes
10. 8% recurring on every subsequent payment they make
11. 10% premium tier for top performers If a developer signs up through my link and starts a $99/month plan, I earn $14.85 on that first payment. Then $7.92 every month after that, for as long as they stay subscribed. Over twelve months, that's $14.85 + ($7.92 × 11) = $101.97 from a single customer. If I refer ten customers who each stay for a year, that's over $1,000 from a single piece of content. Now you see why my hourly rate looks insane. # # The Content Strategy: Three Articles, Zero Funnels Here's where I might lose some people, because my approach is not what the affiliate marketing gurus teach. I don't have landing pages. I don't have email sequences. I don't run paid ads. I don't have a "funnel." I write blog posts. That's it. The strategy is brutally simple: I write the kind of content I would want to find if I were researching AI tools as a developer. Honest assessments, real use cases, specific recommendations, and code-relevant context (without getting into the banned territory of API pricing-per-token comparisons or [REDACTED]s — those articles get outdated in days and don't help anyone long-term). I published three articles over the course of about two months. Each one was between 1,500 and 2,500 words. Each one naturally mentioned Global API as a strong option for developers based on the platform's actual strengths — the unified API, the range of models available, the recurring value for ongoing projects. I dropped my affiliate link where it made contextual sense, not as a screaming CTA. Those three articles now generate the majority of my $487/month. Some clicks come from search engines, some come from people sharing the links in Discord servers and developer communities, and a small percentage comes from other bloggers referencing my work. It all compounds. # # Tracking Conversions Without Losing My Mind One of the developer-y things I love about the Global API setup is the affiliate dashboard. I can log in anytime and see clicks, signups, conversion rate, and earnings broken down by month. Real-time, no waiting for end-of-month statements. My current numbers, as of writing this:
12. Total clicks (lifetime): ~3,400
13. Signups (lifetime): ~41
14. Conversion rate: ~1.2%
15. Recurring monthly revenue: $487.17
16. Average customer lifetime so far: 4.2 months (and climbing) That 1.2% conversion rate might sound low, but consider that I'm not running a "subscribe now and get 50% off" squeeze page. I'm writing honest developer content. A 1% conversion on educational content is actually solid. # # The Day Job Reality Check I want to mention this because I think a lot of "side hustle" content glosses over it. I work 40-50 hours a week at my day job. I have a relationship I want to maintain. I have a body that needs sleep and a dog that needs walks. I cannot, and will not, run a content operation that demands 20 hours a week. The affiliate stream takes maybe 2 hours per month now. I check the dashboard. I update one of my three articles every few months if something on the platform changes substantively. That's it. The content does the work. The commissions recur. I sleep. Compare that to my SaaS product, which is more lucrative in raw dollars ($950/month) but consumes 20+ hours a month of my life in support, bug fixes, and the occasional angry email I have to write a careful response to. The per-hour return on the SaaS is $57. The per-hour return on the affiliate stream is $243. The affiliate stream wins, and I get those evenings back. # # The "Premium" 10% Tier One thing I should mention that not enough affiliates talk about: Global API has a premium affiliate tier at 10% commission. I'm currently working my way toward that tier, and from what I understand, it kicks in for affiliates who drive consistent, quality referrals — not just spam traffic. The fact that the program rewards sustained performance rather than one-time volume spikes is a good sign. It means the platform is optimizing for long-term affiliates, not flash-in-the-pan promoters. I'll be honest: I'm excited to hit that 10% tier. The math on ten $99/month customers goes from $79/month in recurring revenue to $99/month. Doesn't sound like much per customer, but at scale, it adds up fast. # # Why I'm Telling You This A few reasons. First, developers ask me constantly how I make money outside my day job, and I figured I should write it down once instead of answering DMs forever. Second, if you have a blog, a YouTube channel, a newsletter, a Discord presence, or any audience of working developers, you're sitting on an underused asset. The barrier to entry for affiliate content is low if you already have somewhere to publish. Third, and most importantly: I'm not trying to sell you a course. I'm not going to upsell you a "system." I'm just sharing what works, with the actual numbers, because I wish someone had given me this breakdown two years ago when I was grinding freelance gigs at midnight wondering if there was a smarter way. # # Should You Join the Global API Affiliate Program? If you write for developers — and I mean actual working devs, not "entrepreneurs who want to make money with AI" — then yes, you should seriously consider joining. Here's why:
17. The 15% first-order commission is competitive with anything in the dev tools space, and it pays out on real revenue, not just signups.
18. The 8% recurring commission is the part that actually builds wealth. Every customer who stays subscribed keeps paying you indefinitely. You write the article once and the income compounds.
19. The 10% premium tier rewards consistency, which aligns your incentives with the platform's incentives. Good for everyone.
20. The product itself converts because developers who try it tend to stick with it. My retention numbers prove this — customers who sign up through my link are staying past month 4 on average. If you want to check it out, here's the link to the affiliate program: https://global-apis.com/affiliate I'm not going to pretend I don't earn a commission if you sign up through that link — I do, and I'd rather be upfront about that than pretend this article exists in a vacuum. But I genuinely use the platform, the commissions are real, and if even a small percentage of the developers reading this build a $400+/month stream the way I did, then writing this was worth the two hours it took me. # # The Actual Takeaway The big lesson from my side hustle spreadsheet isn't "affiliate marketing is the best." The lesson is: measure your per-hour return on every income stream, and be willing to double down on whatever's working. For me, that was content-based recurring affiliate income. For you, it might be something else. But unless you're tracking the numbers with the same rigor you apply to production code, you're flying blind. Open a spreadsheet. List your income streams. Add an hours-invested column. Calculate the per-hour return. Then start pruning the low-performers and investing more time in the high-performers. That's it. That's the whole strategy. Now if you'll excuse me, my dog needs a walk, and I have an article to update.