i.
You run the collector
A tiny open-source CLI reads the usage logs your tools already write to your own disk (the same files ccusage reads). One daily cron tick, no resident daemon.
Every AI coding tool you run harvests your usage stats, ships them home, and monetizes them. You get nothing — you can't even see the aggregate. Backpay inverts it: the same metadata, collectively bargained. We publish the live index of who's actually winning the AI tooling war — the data every vendor, VC and fund is starving for — and 50% of every euro flows back to the members generating it.
A tiny open-source CLI reads the usage logs your tools already write to your own disk (the same files ccusage reads). One daily cron tick, no resident daemon.
The payload is a whitelist: token counts, model and tool names from a fixed vocabulary, day-level dates.
Prompts, paths, repo names — never read in the first place. preview shows every byte before it leaves.
Buyers pay for k-anonymous aggregates only. Half of all revenue accrues to members, pro-rata by days contributed. Default payout rail: Lightning — money nobody can freeze.
One command, once — the meter then runs itself (a ~1-second daily tick, no daemon). It shows you every byte and asks before sending anything. No email, no signup, no spam — ever. Member №1 is live on the feed; the first hundred carry permanent founding weight.
npx backpay
1 member(s) and counting · founding weight for the first 100