How much can you earn from terminal ads?
Honestly: it’s modest, passive cash back — enough to chip away at your AI tooling bill, not a paycheck. You keep 90% of the ad revenue your own sessions in Claude Code and Codex generate, capped at $1 a day. Here’s exactly what moves the number.
Impressions, not clicks.
You get credited for the line being shown — nothing to click, nothing to chase.
- You earn on impressions — every session the sponsored footer is shown counts.
- No clicks required. Clicks pay nothing; the impression is what earns.
- You keep 90% of the ad revenue your own devices generate, settled daily.
- Capped at $1 per account per day, withdrawable after a 14-day review hold.
What an active developer sees.
This is an illustrative figure from the dashboard, not a guarantee — your number will differ with your sessions and the sponsors in rotation.
Three things decide your number.
No gaming, no clicking. Earnings track how much you actually code, whether a sponsor is there to fill the slot, and what that sponsor pays — up to $1 a day.
How often you code
More sessions in Claude Code and Codex means more impressions, up to the $1 a day cap. A daily driver earns more than an occasional user — this is still the biggest lever.
What the sponsors pay
You only earn when a real sponsor fills the slot, and you keep 90% of what that impression actually earned. Fill and rates both improve as more sponsors join.
Sessions, not screen time
Earnings track sessions where the line is shown, not hours idling. Short, frequent sessions can out-earn one long one.
It’s cash back, not a salary.
The most useful way to think about it: make your AI tooling pay for part of itself while you work exactly as you already do.
Rebates won’t replace your income, and we won’t pretend it will. What it does is turn sessions you were going to run anyway into a steady trickle of credit — quietly offsetting the cost of the tools you already pay for. No clicks, no referral grind, off in one command.
Straight answers about earnings.
How much can you really earn from Claude Code ads?
Modest, passive cash back. The honest comparison is an AI tooling bill partly offset, not a salary earned. Rebates pays each developer 90% of the ad revenue their own devices generate, capped at $1 per account per day, which puts a ceiling of roughly $30 on a month. The published Rebates dashboard example shows $23.80 of cash back in a month for an active developer, and that figure is illustrative rather than a guarantee. Earnings then depend on two variables: how often a developer runs sessions, because impressions are the unit, and sponsor fill, because a slot with no sponsor in rotation earns nothing. Neither variable rewards gaming, so the realistic range for most developers is tens of dollars per month rather than anything larger.
Are you paid per impression or per click?
Per impression. Every session the sponsored footer is shown pays 90% of the ad revenue that impression generated, and clicks pay nothing at all, so no reader has to be persuaded to click for a developer to be paid. The share is deliberately high. Kickbacks pays a 50% revenue share plus clicks, and IdleDev pays 65% plus clicks, according to each product site as of July 2026, which means both keep a larger cut of the same impression and make part of it back on click-through that no developer controls. Rebates keeps 10%, settles daily against the revenue the ad exchange reports, and caps each account at $1 per day during the beta.
When do earnings show up?
Impressions appear immediately; the money settles daily. The sequence is short. First, the sponsored footer renders during a normal Claude Code or Codex session, and that visible impression is counted straight away. Second, Rebates settles the day against the revenue the ad exchange reports and credits 90% of it, up to the $1 daily cap. Finally, a settled balance clears a 14-day review hold, after which it is withdrawable from the wallet. The hold exists so invalid traffic can be reversed before money leaves, not to delay honest earnings. Claiming the device is the only step that requires action beyond installing the Rebate CLI.
What makes my earnings go up?
Two things, and neither involves gaming the system. The first is coding more, because more Claude Code and Codex sessions mean more impressions, and impressions are what Rebates pays on — up to the $1 per account per day cap, which bounds how far that lever runs. The second is sponsor fill and what those sponsors pay, since Rebates hands back 90% of the revenue an impression actually earned and a slot with no sponsor available earns nothing at all. Advertiser demand is outside any individual developer control. No clicking, referral grinding, or session padding increases earnings, because clicks pay nothing and Rebates counts visible impressions during real work rather than rewarding activity for its own sake.
Can this cover my Claude or Codex subscription?
Partly, for many developers, and that is the honest framing. The $1 per account per day cap puts a hard ceiling of roughly $30 on a month, so fully covering a Claude or Codex subscription is not something Rebates will promise. The published dashboard example of $23.80 in a month is illustrative, and whether a given month lands above or below depends on session volume, sponsor fill, and what those sponsors pay, because the credit is 90% of realized ad revenue rather than a fixed rate. Treat Rebates as cash back that chips away at the bill rather than a guaranteed offset against it. A developer running Claude Code daily will see more than an occasional user, but no usage pattern turns a footer line into a subscription-sized number.
Start the trickle.
Install in one command and the footer starts earning on your next session — preview first with rebate plan.
curl -fsSL https://rebates.ai/install | bash