Is Rebates legit? Yes — here’s how it works.
Getting paid to show a line in your terminal sounds too easy, so here is the whole thing with nothing hidden: how the money reaches you, how Rebates makes its cut, and how to sanity-check any tool like this.
Impression → ledger → wallet.
No clicks to chase, no referrals required. The line shows, it counts, it pays.
- 01The sponsored footer renders in Claude Code or Codex while you work.
- 02Each session it is visibly shown is counted as an impression.
- 03Impressions credit to your ledger within seconds — no clicks required.
- 04You claim your device, then cash out your balance from your wallet.
How Rebates makes money — and why it doesn’t need your code.
Rebates is a two-sided marketplace. Sponsors pay to reach developers; Rebates passes you a cut and keeps the margin. That model works without ever touching your work.
Because the revenue comes from sponsors — not from your data — Rebates has no reason to sell your raw files, prompts, or transcripts, and its Privacy Notice says it does not. The default footer isn’t even contextual: it doesn’t need to know what you’re building to pay you.
Five questions to ask any terminal-ad tool.
Use this on Rebates or anything like it. A trustworthy tool answers all five plainly.
- Does it read your code? Rebates does not, in the default flow.
- Does it disclose contextual sharing? Rebates makes it opt-in and redacts on-device.
- Can you preview changes? Run `rebate plan` before anything is applied.
- Can you fully undo it? `rebate off` restores your settings byte-for-byte.
- Are payouts real and live? Rebates credits in seconds and pays from your wallet.
Straight answers.
Is Rebates a scam?
No. Rebates pays you a share of what sponsors pay to reach developers. You earn a credit each time the sponsored footer is shown, the balance accrues in your wallet, and you cash it out. Nothing is required beyond letting the line render, and you can turn it off in one command.
Do you actually get paid?
Yes. Impressions credit within seconds and settle to your wallet; you claim your device to enable payouts. This is the ordinary two-sided-marketplace model: sponsors pay to reach developers, and Rebates passes a cut to you.
How does Rebates make money?
Sponsors pay to show a line to developers; Rebates keeps the difference between what a sponsor pays and what it credits you. That is the entire business — there is no need to sell your code, files, or transcripts, and Rebates does not.
Is it safe to run in my terminal?
Rebates backs up your Claude Code and Codex settings byte-for-byte before changing anything, lets you preview with `rebate plan`, and restores everything with `rebate off`. It adds a footer line and clickable-link setup; it does not run your code.
How do I know a terminal-ad tool is trustworthy?
Check five things: does it read your code, does it disclose any contextual sharing, can you preview changes, can you fully undo it, and are payouts actually live. A tool that answers all five plainly is one you can trust; Rebates publishes all five.
Legit, and off in one command.
Install, preview with rebate plan, and if it’s not for you, rebate off puts everything back.
curl -fsSL https://rebates.ai/install | bash