Your agent pays you.
Kickbacks turns agent wait time into developer revenue. Short, clearly labeled sponsor messages appear while your agent thinks, and you keep half of every ad dollar.
npx kickbacks initexport async function charge(req) {
const client = await connect();
const invoice = await client.create({
amount: req.amount,
currency: "usd",
});
return invoice;
}> refactor the payment service to use the new client
Reading the files first, then updating each call site.
Updated payments/service.ts
the deal
Half of every ad dollar is yours.
Fixed split
The developer split is always 50%. No tiers, no hidden threshold, no fuzzy revenue math.
Seen only when useful
Sponsor lines show while the agent is busy, in the status area developers already monitor.
Prompt safe
Ads are labeled and isolated from prompts, code, context, shell history, and generated output.
how it works
Three steps, zero new habits.
Install
Wire Kickbacks into the status line of Codex, Claude Code, Cursor, or VS Code with one command.
Wait
When your agent is thinking, a short sponsored line appears in the place you already watch.
Cash out
Qualified impressions settle to your balance. Withdraw through Stripe once you reach $5.
What is your wait worth?
At the $5 sponsor floor, 1.5 hours of agent wait time per working day estimates around $6 per month. Higher bids and heavier usage raise the line.
Buy the line developers actually watch.
Sponsor a concise message in a public auction. Fund blocks of qualified impressions, pay for what is actually seen, and reach developers in the moment they are already waiting on AI.
faq
The fine print, kept readable.
Does Kickbacks read my prompts or code?
No. Sponsor messages ride the status line only. Kickbacks does not inject text into prompts, agent context, files, commits, or terminal output.
How do developers earn?
Sponsors buy qualified impressions in blocks. When an ad is shown while your agent is busy, 50% of that ad dollar accrues to your balance.
Will ads interrupt my workflow?
No. The placement is short, labeled, and passive. It appears during wait states, then gets out of the way when work resumes.
Why would sponsors use it?
They reach developers during an unusually focused moment: the exact line developers watch while agents think, test, refactor, or build.