of open-source value to firms
Estimated cost to recreate the open-source software firms use. Replacement value, not market revenue.
FOR THE OPEN SOURCE BEHIND YOUR AI
Turn a Claude Code session into support for the open-source packages it used. Your budget. Their credit.
Voluntary contributions · Testnet USDC on Base Sepolia
Build a better checkout.
Usage recorded. Contributions recognized.
Validators. Test runners. The tiny utility that just works. Your agent uses their work. End Credits helps you recognize it.
Examples of open-source projects in the ecosystem, not customers or endorsements.
THE MISSING THANK-YOU
Developers pay for the agent. The packages underneath it are still maintained by people. End Credits connects the work your agent uses to a contribution you choose.
Estimated cost to recreate the open-source software firms use. Replacement value, not market revenue.
In our top-1,000 npm package snapshot, 416 had funding metadata. Just 21 listed a wallet across the sources we checked.
HOW END CREDITS WORKS
Follow the work from your AI agent to the people behind its packages. Every contribution has a budget, a decision, and a trail you can inspect.
ON YOUR MACHINE
Connect Claude Code with the CLI. Hooks quietly record package imports, reads, dependency additions, and documentation lookups. Your source code and repository paths stay local.
The MCP server also lets your agent inspect sessions and initiate settlement using your configured settings.
@endcredits-demo/schemadependency added
package imported
docs consulted
Watch the full loop, or jump to any chapter. Amounts and packages here are illustrative.
Explore the implementation ↗THE INTEGRATIONS BEHIND THE CREDITS
Each integration has a specific job in the contribution flow.
SCREENING
Counterparty, token, and impersonation screening informs each credit’s decision. Screening failures put contributions on hold.
ON-CHAIN VISIBILITY
Escrow and USDC event queries, plus webhooks, bring blockchain activity into the dashboard.
An open-source hackathon project on Base Sepolia.
GENEROSITY, WITH BOUNDARIES
Choose what a session can spend, a daily limit, and a maximum share per package. No surprise open tabs.
A screening error means hold, never pay. Escrowed holds need approval; denial or expiry makes them refundable.
A package’s share can wait in escrow. Maintainers prove GitHub ownership and publish a wallet to claim it.
Find your package, inspect its reserved credits, and connect a payout wallet.
A LITTLE MORE CONTEXT
What gets recorded, where the money goes, and what stays in your control.
No. End Credits is voluntary support, never a paywall. Package licenses and access stay exactly as they are. You choose whether to contribute and set the budget.
Package attribution signals, not your source code or repository paths. The local hook records package reads, imports, and installs, then the session’s package credits are uploaded.
Its share can be reserved in EndCreditsEscrow. The maintainer signs in with GitHub, proves repository ownership, and adds a payout wallet through a funding pull request.
A timeout or error from Intercepta means hold, never pay. No payment authorization is signed without the required stored decision and payment checks.
This version runs on Base Sepolia using testnet USDC. It is a working testnet project built for ETHGlobal Tokyo 2026.
READY FOR YOUR NEXT SESSION
Build the CLI from source, create a connection key, and install the hook in your project.
Create a connection keySource code ↗pnpm installpnpm --filter endcredits buildcd cli && npm link && cd ..endcredits initendcredits key <token> --api https://end-credits.up.railway.appClone the source first. Run init inside your project and replace <token> with your connection key.