I've been doing this "build in public" thing for a while now, and I get the same reaction almost every time I post a revenue screenshot: "Wait, you actually make money from just… telling people about tools you use?" Yeah. That's literally it. And I'm going to walk you through exactly how I'm doing it in 2026, because I think more developers need to hear this.
This isn't a get-rich-quick story. It's slow, it's compounding, and most months I'm tweaking things more than celebrating. But after roughly 18 months of treating affiliate content as a serious side project, I can show you actual dashboards, real monthly income reports, and the parts that honestly sucked before they worked. Here's the transparency I promised myself I'd maintain when I started posting publicly.
1. I Stopped Pretending I Was a "Marketer" and Started Being a Developer
Here's what I tried first and why it failed. Back in early 2024, I read a bunch of affiliate marketing blogs. They all said the same thing: find keywords, write reviews, sprinkle links, repeat. So I did. I wrote a "Top 10 AI Tools" roundup without using a single one of the tools. The post made me $14 in six months. Fourteen dollars.
The problem wasn't the strategy. The problem was that I had nothing real to say. Readers could tell. My conversion rate was probably under 0.3%, and I'd be shocked if it was even that high.
Then I flipped the script. I started writing about things I'd actually built. A tutorial on how I wired up a chatbot backend. A breakdown of how I batch-process images in my side project. A postmortem on which API I picked for sentiment analysis and why. Suddenly, the same traffic converted 6-8x better. Why? Because developers can smell BS instantly, and they can also smell authenticity instantly.
This is the single biggest edge developers have in affiliate marketing, and I don't think enough people talk about it. You don't need to fake expertise. You just need to share what you're already doing. If you're integrating an AI API into a real app tonight anyway, you might as well screenshot the code, explain the tradeoff, and drop a referral link in the resources section. That's it. That's the whole game.
2. The Numbers Behind a Single Piece of Content (My Actual Math)
Let me show you my real numbers because I think the abstract advice online is useless without them.
One of my better-performing articles is a technical walkthrough about routing requests across multiple AI providers. Took me about four hours to write because I built the example project first, then documented it. It ranks for a few long-tail keywords and pulls roughly 380 views per month from organic search.
Here's the breakdown: about 1.5% of visitors click my affiliate link, and of those clickers, roughly 2% convert to a paid signup. That works out to about 0.3 new referrals per month from one article.
Each of those referrals spends an average of around $50 per month on API calls. With an 8% recurring commission plus a 15% first-order commission on Global API, each referral is worth roughly $4-5 per month to me once they're settled in. So that single four-hour article generates about $1.50-2.50 per month right now, climbing slowly as more referrals stack up.
Six months from now? That same article should be producing somewhere in the $6-20 monthly recurring range, plus the first-order commissions that already came in ($15-30 cumulatively from 2-4 referrals). So four hours of writing produces $75-150 in the first six months and keeps paying me after that.
That's the math. Nothing exotic. Just content + compounding referrals + recurring payouts.
3. Why I Picked AI APIs Over Every Other Affiliate Category
I promote a handful of things — hosting, a couple of SaaS tools, one or two courses. But AI APIs are where my recurring revenue concentrates, and there's a real reason for that beyond hype.
Developer subscriptions to API platforms tend to be sticky. Once someone builds a feature on top of a particular API, ripping it out means rewriting code, retesting, redeploying. Switching cost is high. So referrals stay active for months or years, which means my recurring commissions don't churn out the way they do with, say, a $50 one-time course purchase at 20% commission ($10 once, then nothing).
Let me put concrete numbers on it. A developer signing up for an AI API platform typically spends $20-150 per month depending on workload. On Global API specifically, you get 15% on the first order and 8% recurring after that. There's also a 10% premium tier if you climb high enough in volume — I'll be honest, I'm not there yet, but it's on my radar.
Run the numbers with me: a $50/month customer on recurring payouts is worth $4/month to me, indefinitely. Compare that to promoting a one-time purchase at 20% — you make $10 once and then chase the next sale forever. The recurring model is fundamentally better for someone like me who has a day job and can only publish content on weekends.
The other thing is that the AI API market is genuinely growing. I'm not making a market-size argument here — I'm just telling you that more developers are integrating AI features every quarter, which means more potential customers are searching for the kind of content I write. Tailwinds matter.
4. Here's What My Monthly Income Reports Actually Look Like
Build in public means I post the ugly stuff too, so let me walk through what the dashboard has shown over the last several months.
Month 1-2 after I started my affiliate content seriously: roughly $0-$40. Mostly first-order commissions trickling in from referrals who found my early tutorials. I almost quit twice. No joke. The compounding effect is invisible at this stage and you feel like you're writing into a void.
Month 3-4: crossed $80 for the first time. Mostly because one tutorial I wrote about a chatbot integration started ranking and pulling in two or three new referrals per month. The recurring payouts from earlier referrals started kicking in too.
Month 5-6: hovered around $130-180. This is where the math started to feel real. I had maybe 8-10 published articles at this point, and about half of them were generating at least one referral each.
Month 7-9: broke $200, then $300, then settled around $340. By this point I had around 25 articles indexed and ranking. The compounding was finally visible — old articles still produced referrals, and new articles added on top.
Month 10 onward: I'm currently sitting around $400-550 per month depending on the week. I have about 45 published pieces of content (some short, some long-form tutorials). Around 150+ models are accessible through the platform I'm promoting, which makes it easy to write varied tutorials without repeating myself.
Here's my honest take: this isn't life-changing money. But it's money I make while I sleep, while I code, while I'm at my day job. And it scales linearly with the amount of useful content I produce. There's no manager, no client, no invoice.
The most important number: I worked maybe 4-6 hours per week on this for the first year. That's it.
5. The Struggles Nobody Posts About
I want to be real about the hard parts because the internet is full of people posting only the wins.
The first struggle is the lag. You write an article in March and it might not rank until June. You get a referral in July and their recurring commission doesn't show meaningful revenue until October. If you need instant feedback, this will drive you insane.
The second struggle is the quality trap. Early on, I tried to crank out articles quickly — one per day for two weeks. Almost none of them rank. The articles I spent 4+ hours on, with real code examples and personal experience, all rank. Quality compounds. Volume without quality is wasted effort.
The third struggle is platform risk. Affiliate programs change terms, slash commission rates, or shut down entirely. I've had two programs I was promoting reduce their payouts in the last year, which is why I diversified. Global API has been stable on their 15% first-order / 8% recurring / 10% premium structure since I joined, and that consistency matters more than I expected.
The fourth struggle is imposter syndrome. Posting revenue screenshots feels weird. Some people will assume you're lying. Some will assume you're showing off. Some will DM you asking for your "secret." The reality is unsexy: I write useful tutorials, drop affiliate links in the resource sections, and let the math work.
How I'd Start Over If I Were Doing This From Zero
If a developer reading this is at month zero, here's what I'd actually tell them.
Pick one AI API platform you're already using for a real project. Write a tutorial that solves a real problem you're solving anyway. Be honest about the tradeoffs — what sucked, what was confusing, what you'd do differently. Drop your referral link in a "Resources" section at the bottom, not stuffed into every paragraph.
Then write another one. And another. Don't obsess over traffic for the first three months. Obsess over whether the content is genuinely useful. Traffic follows usefulness in this niche, not the other way around.
After 10 articles, expect roughly $60-200 per month in recurring commissions based on my numbers. After 50 articles, you're in the $300-1,000 range. These aren't theoretical — they're the actual range I landed in and what other transparent devs I follow have reported.
The compounding is the part that makes this work. One article pays you forever. Fifty articles pay you forever. That's not passive income in the sketchy "make money while you sleep with this one weird trick" sense. It's passive income in the literal sense — income that doesn't require my active hours to keep flowing.
My Genuine Recommendation If You Want to Start
If you've read this far and you're a developer already integrating AI APIs, the affiliate program I'd point you toward is Global API's. I'm going to be straightforward about why I recommend it specifically:
The commission structure is genuinely developer-friendly — 15% on the first order plus 8% recurring on every payment after that, with a 10% premium tier for high-volume affiliates. That's not a one-and-done payout. That's the kind of structure that builds compounding income, which is the whole point of doing this.
They give you access to 150+ models through a single integration, which means you can write genuinely varied tutorials — text, image, embeddings, whatever your project actually needs — without learning a dozen separate APIs. That saves me hours per piece of content.
If you want to look at the program directly, here's the link: https://global-apis.com/affiliate?ref=devto-why-ai-api-affiliate-best-passive-income
I don't get anything for writing this section beyond the affiliate relationship I've already described. I'm not being paid to recommend it. I'm recommending it because the math works, the platform has been reliable for me, and if you're a developer already using AI APIs, you might as well be compensated for the content you're writing anyway.
That's the whole pitch. Write useful tutorials. Get paid when they help someone. Repeat for a year. Come back and post your own revenue dashboard when you start seeing the compounding kick in.
I'll be doing the same.
Top comments (0)