// open-source panel · works with claude code
Every session your agent runs
earns royalties.
Your agent picks packages, calls APIs, burns tokens. That’s market data companies pay for, and you take your cut. Metadata only. Never your code. Beer money, finally automated. 🍺
no account · uninstall in one command · read every byte that leaves in the open repo
a few cents a session · ≈ a few beers a month
illustrative · formula published before first payout
// 01 — what leaves your machine
The whitelist is the law. Read it like a diff.
[ collected ]
- +package names added
- +api domains — from a public list
- +model, agent & version
- +session stats — duration, turns, tokens
- +error category
- +country
[ never collected ]
- -your prompts
- -your code & diffs
- -file, repo & branch names
- -error messages
- -secrets & environment variables
- -your ip address
> don’t trust the table — npx royalties inspect prints the exact payload for your last session and sends nothing.
// 02 — how the money works
Three steps, then it runs itself.
install via official hooks
Plugs into Claude Code’s documented hook API — SessionStart, PostToolUse, Stop. No binary patching, no MITM proxy.
code as you always do
The collector reads only whitelisted metadata from your local session logs. Prompts and code never leave the machine.
your share, paid out
Panel revenue from aggregated reports is split by contribution. Cash out via Stripe once thresholds are met.
// 03 — why this exists
> They sell your attention. We think you should sell your metadata instead.
Every devtool company on earth is asking “do coding agents pick us or our competitor?” — and today they only have synthetic benchmarks. The real-world ground truth of what AI agents actually choose doesn’t exist anywhere. A voluntary, paid, auditable panel is the only legitimate way it can.
// 04 — for devtool builders
Building a devtool?
See share-of-agent-choice for your category — aggregated, anonymized, from a real panel. No synthetic benchmarks.
// 05 — faq
The questions you should be asking.
[+–]Is this spyware?
npx royalties inspect shows the exact payload before you trust anything. A leak of a non-whitelisted field is a critical bug, fixed in public.[+–]How much will I earn?
[+–]What about my client’s code confidentiality?
.royaltiesignore in that project.